Profiled Hypertext Application Language
draft-montoya-phtal-00

Document Type Active Internet-Draft (individual)
Last updated 2019-02-26
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         J. Montoya
Internet-Draft                         Mountain State Software Solutions
Intended status: Informational                         February 26, 2019
Expires: August 30, 2019

                Profiled Hypertext Application Language
                         draft-montoya-phtal-00

Abstract

   This document defines PHTAL, a generic representation format for
   hypertext applications guided by REST constraints.  PHTAL could be
   compared to HTML without graphical requirements.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 30, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Montoya                  Expires August 30, 2019                [Page 1]
Internet-Draft                    phtal                    February 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Definitions and Terminology . . . . . . . . . . . . . . .   2
       1.1.1.  Terminology and Conformance Language  . . . . . . . .   3
       1.1.2.  General . . . . . . . . . . . . . . . . . . . . . . .   3
       1.1.3.  Documents description . . . . . . . . . . . . . . . .   3
     1.2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  PHTAL Representations . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Hypermedia as the engine of application state . . . . . .   4
       2.1.1.  Document Root . . . . . . . . . . . . . . . . . . . .   4
       2.1.2.  Link  . . . . . . . . . . . . . . . . . . . . . . . .   7
       2.1.3.  Operation . . . . . . . . . . . . . . . . . . . . . .   9
       2.1.4.  HTTP Operation  . . . . . . . . . . . . . . . . . . .  11
       2.1.5.  SecurityRequirement . . . . . . . . . . . . . . . . .  12
       2.1.6.  Partial . . . . . . . . . . . . . . . . . . . . . . .  13
     2.2.  Self-descriptive messages . . . . . . . . . . . . . . . .  14
       2.2.1.  Linking to a profile  . . . . . . . . . . . . . . . .  15
     2.3.  Code-On-Demand  . . . . . . . . . . . . . . . . . . . . .  16
       2.3.1.  Script  . . . . . . . . . . . . . . . . . . . . . . .  16
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     3.1.  application/phtal+xml . . . . . . . . . . . . . . . . . .  18
     3.2.  application/phtal+json  . . . . . . . . . . . . . . . . .  19
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .  21
     4.2.  Informative References  . . . . . . . . . . . . . . . . .  22
     4.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  22
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  23
   Appendix B.  Frequently Asked Questions . . . . . . . . . . . . .  23
     B.1.  How can I submit comments or feedback to the editors? . .  23
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  23

1.  Introduction

   This document defines PHTAL, a generic representation format for
   hypertext applications guided by REST constraints.  PHTAL could be
   compared to HTML without graphical requirements.

   This document registers two media-type identifiers with the IANA:
   "application/phtal+json" and "application/phtal+xml".  This
   registration is for community review and will be submitted to the
   IESG for review, approval, and registration with IANA.

1.1.  Definitions and Terminology

Montoya                  Expires August 30, 2019                [Page 2]
Internet-Draft                    phtal                    February 2019

1.1.1.  Terminology and Conformance Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text