updating draft-soilandreyes-app title/abstract

concepts/uri-scheme.md

@@ -12,7 +12,7 @@ URI Scheme | Specification
 -------: | :-------
 [`about`](/concepts/uri-scheme/about "The resource that is referenced by a particular "about" URI is denoted by the <about-token> part of the URI.") | [**RFC 6694**: The "about" URI Scheme](/specs/IETF/RFC/6694 "This document describes the "about" URI scheme, which is widely used by Web browsers and some other applications to designate access to their internal resources, such as settings, application information, hidden built-in functionality, and so on.")
 [`acct`](/concepts/uri-scheme/acct "Although 'acct' URIs take the form "user@host", the scheme is designed for the purpose of identification instead of interaction. The "Internet resource" identified by an 'acct' URI is a user's account hosted at a service provider, where the service provider is typically associated with a DNS domain name.") | [**RFC 7565**: The 'acct' URI Scheme](/specs/IETF/RFC/7565 "This document defines the 'acct' Uniform Resource Identifier (URI) scheme as a way to identify a user's account at a service provider, irrespective of the particular protocols that can be used to interact with the account.")
-[`app`](/concepts/uri-scheme/app "The "app" URI scheme follows the RFC 3986 syntax for hierarchical URIs. The "app-authority" component provides a unique identifier for the opened archive. The "path-absolute" component provides the absolute path of a resource (e.g. a file or directory) within the archive.") | [**Internet Draft soilandreyes-app**: The Archive and Packaging Pointer system](/specs/IETF/I-D/soilandreyes-app "This Internet-Draft proposes the "app" URI scheme for the Archive and Packaging Protocol. app URIs can be used to consume or reference hypermedia resources bundled inside a file archive or a mobile application package, as well as to resolve URIs for archive resources within a programmatic framework. This URI scheme provides mechanisms to generate a unique base URI to represent the root of the archive, so that relative URI references in a bundled resource can be resolved within the archive without having to extract the archive content on the local file system. An app URI can be used for purposes of isolation (e.g. when consuming multiple archives), security constraints (avoiding "climb out" from the archive), or for externally identifying sub-resources in other hypermedia formats.")
+[`app`](/concepts/uri-scheme/app "The "app" URI scheme follows the RFC 3986 syntax for hierarchical URIs. The "app-authority" component provides a unique identifier for the opened archive. The "path-absolute" component provides the absolute path of a resource (e.g. a file or directory) within the archive.") | [**Internet Draft soilandreyes-app**: The Archive and Packaging Pointer (app) URI scheme](/specs/IETF/I-D/soilandreyes-app "This Internet-Draft proposes the Archive and Packaging Pointer URI scheme app. app URIs can be used to consume or reference hypermedia resources bundled inside a file archive or an application package, as well as to resolve URIs for archive resources within a programmatic framework. This URI scheme provides mechanisms to generate a unique base URI to represent the root of the archive, so that relative URI references in a bundled resource can be resolved within the archive without having to extract the archive content on the local file system. An app URI can be used for purposes of isolation (e.g. when consuming multiple archives), security constraints (avoiding “climb out” from the archive), or for externally identifying sub-resources referenced by hypermedia formats.")
 [`cap`](/concepts/uri-scheme/cap "The CAP URL scheme is used to designate both calendar stores and calendars accessible using the CAP protocol.") | [**RFC 4324**: Calendar Access Protocol (CAP)](/specs/IETF/RFC/4324 "The Calendar Access Protocol (CAP) described in this memo permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an iCAL-based Calendar Store (CS). At the time of this writing, three vendors are implementing CAP, but it has already been determined that some changes are needed. In order to get implementation experience, the participants felt that a CAP specification is needed to preserve many years of work. Many properties in CAP which have had many years of debate, can be used by other iCalendar protocols.")
 [`cid`](/concepts/uri-scheme/cid "The "mid" (Message-ID) and "cid" (Content-ID) URL schemes provide identifiers for messages and their body parts. The "cid" scheme refers to a specific body part of a message; its use is generally limited to references to other body parts in the same message as the referring body part.") | [**RFC 2392**: Content-ID and Message-ID Uniform Resource Locators](/specs/IETF/RFC/2392 "The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message.")
 [`coap+tcp`](/concepts/uri-scheme/coap+tcp "The "coap+tcp" URI scheme identifies CoAP resources that are intended to be accessible using CoAP over TCP.") | [**Internet Draft ietf-core-coap-tcp-tls**: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets](/specs/IETF/I-D/ietf-core-coap-tcp-tls "The Constrained Application Protocol (CoAP), although inspired by HTTP, was designed to use UDP instead of TCP. The message layer of the CoAP over UDP protocol includes support for reliable delivery, simple congestion control, and flow control. Some environments benefit from the availability of CoAP carried over reliable transports such as TCP or TLS. This document outlines the changes required to use CoAP over TCP, TLS, and WebSockets transports. It also formally updates RFC 7641 for use with these transports.")

concepts/uri-scheme/app.md

@@ -7,7 +7,7 @@ concept-value: app
 description: "The \"app\" URI scheme follows the RFC 3986 syntax for hierarchical URIs. The \"app-authority\" component provides a unique identifier for the opened archive. The \"path-absolute\" component provides the absolute path of a resource (e.g. a file or directory) within the archive."
 ---
 
-[The "app" URI scheme follows the RFC 3986 syntax for hierarchical URIs. The "app-authority" component provides a unique identifier for the opened archive. The "path-absolute" component provides the absolute path of a resource (e.g. a file or directory) within the archive.](http://tools.ietf.org/html/draft-soilandreyes-app#section-2 "Read documentation for URI Scheme "app"") (**[Internet Draft soilandreyes-app: The Archive and Packaging Pointer system](/specs/IETF/I-D/soilandreyes-app "This Internet-Draft proposes the "app" URI scheme for the Archive and Packaging Protocol. app URIs can be used to consume or reference hypermedia resources bundled inside a file archive or a mobile application package, as well as to resolve URIs for archive resources within a programmatic framework. This URI scheme provides mechanisms to generate a unique base URI to represent the root of the archive, so that relative URI references in a bundled resource can be resolved within the archive without having to extract the archive content on the local file system. An app URI can be used for purposes of isolation (e.g. when consuming multiple archives), security constraints (avoiding "climb out" from the archive), or for externally identifying sub-resources in other hypermedia formats.")**)
+[The "app" URI scheme follows the RFC 3986 syntax for hierarchical URIs. The "app-authority" component provides a unique identifier for the opened archive. The "path-absolute" component provides the absolute path of a resource (e.g. a file or directory) within the archive.](http://tools.ietf.org/html/draft-soilandreyes-app#section-2 "Read documentation for URI Scheme "app"") (**[Internet Draft soilandreyes-app: The Archive and Packaging Pointer (app) URI scheme](/specs/IETF/I-D/soilandreyes-app "This Internet-Draft proposes the Archive and Packaging Pointer URI scheme app. app URIs can be used to consume or reference hypermedia resources bundled inside a file archive or an application package, as well as to resolve URIs for archive resources within a programmatic framework. This URI scheme provides mechanisms to generate a unique base URI to represent the root of the archive, so that relative URI references in a bundled resource can be resolved within the archive without having to extract the archive content on the local file system. An app URI can be used for purposes of isolation (e.g. when consuming multiple archives), security constraints (avoiding “climb out” from the archive), or for externally identifying sub-resources referenced by hypermedia formats.")**)
 
 <br/>
 <hr/>

specs.json

@@ -356,11 +356,11 @@
        "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/to" }]}},{
      "soilandreyes-app": {
       "id": "http://webconcepts.info/specs/IETF/I-D/soilandreyes-app",
-      "title": "The Archive and Packaging Pointer system",
+      "title": "The Archive and Packaging Pointer (app) URI scheme",
       "name": "Internet Draft soilandreyes-app",
       "URI": "urn:ietf:id:soilandreyes-app",
       "URL": "http://tools.ietf.org/html/draft-soilandreyes-app",
-      "abstract": "This Internet-Draft proposes the \"app\" URI scheme for the Archive and Packaging Protocol. app URIs can be used to consume or reference hypermedia resources bundled inside a file archive or a mobile application package, as well as to resolve URIs for archive resources within a programmatic framework. This URI scheme provides mechanisms to generate a unique base URI to represent the root of the archive, so that relative URI references in a bundled resource can be resolved within the archive without having to extract the archive content on the local file system. An app URI can be used for purposes of isolation (e.g. when consuming multiple archives), security constraints (avoiding \"climb out\" from the archive), or for externally identifying sub-resources in other hypermedia formats.",
+      "abstract": "This Internet-Draft proposes the Archive and Packaging Pointer URI scheme app. app URIs can be used to consume or reference hypermedia resources bundled inside a file archive or an application package, as well as to resolve URIs for archive resources within a programmatic framework. This URI scheme provides mechanisms to generate a unique base URI to represent the root of the archive, so that relative URI references in a bundled resource can be resolved within the archive without having to extract the archive content on the local file system. An app URI can be used for purposes of isolation (e.g. when consuming multiple archives), security constraints (avoiding “climb out” from the archive), or for externally identifying sub-resources referenced by hypermedia formats.",
       "concepts": [{
        "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/app" }]}},{
      "thomson-http-content-signature": {

specs/IETF/I-D/index.md

@@ -41,7 +41,7 @@ There are currently 44 listed specifications in the [Internet Engineering Task F
   * [Signing HTTP Messages (Internet Draft cavage-http-signatures)](cavage-http-signatures)
   * [The 'XML2RFC' version 3 Vocabulary (Internet Draft hoffman-xml2rfc)](hoffman-xml2rfc)
   * [The +exi Media Type Suffix (Internet Draft shelby-exi-registration)](shelby-exi-registration)
-  * [The Archive and Packaging Pointer system (Internet Draft soilandreyes-app)](soilandreyes-app)
+  * [The Archive and Packaging Pointer (app) URI scheme (Internet Draft soilandreyes-app)](soilandreyes-app)
   * [The JavaScript Object Notation (JSON) Data Interchange Format (Internet Draft ietf-jsonbis-rfc7159bis)](ietf-jsonbis-rfc7159bis)
   * [The Key HTTP Response Header Field (Internet Draft ietf-httpbis-key)](ietf-httpbis-key)
   * [The Link-Template HTTP Header Field (Internet Draft nottingham-link-template)](nottingham-link-template)

specs/IETF/I-D/soilandreyes-app.html

@@ -1,16 +1,16 @@
 ---
 layout:      page
-title:       "The Archive and Packaging Pointer system"
-description: "This Internet-Draft proposes the \"app\" URI scheme for the Archive and Packaging
-Protocol. app URIs can be used to consume or reference hypermedia resources bundled
-inside a file archive or a mobile application package, as well as to resolve URIs
-for archive resources within a programmatic framework. This URI scheme provides mechanisms
-to generate a unique base URI to represent the root of the archive, so that relative
-URI references in a bundled resource can be resolved within the archive without having
-to extract the archive content on the local file system. An app URI can be used for
-purposes of isolation (e.g. when consuming multiple archives), security constraints
-(avoiding \"climb out\" from the archive), or for externally identifying sub-resources
-in other hypermedia formats."
+title:       "The Archive and Packaging Pointer (app) URI scheme"
+description: "This Internet-Draft proposes the Archive and Packaging Pointer URI scheme app. app
+URIs can be used to consume or reference hypermedia resources bundled inside a file
+archive or an application package, as well as to resolve URIs for archive resources
+within a programmatic framework. This URI scheme provides mechanisms to generate a
+unique base URI to represent the root of the archive, so that relative URI references
+in a bundled resource can be resolved within the archive without having to extract
+the archive content on the local file system. An app URI can be used for purposes
+of isolation (e.g. when consuming multiple archives), security constraints (avoiding
+“climb out” from the archive), or for externally identifying sub-resources referenced
+by hypermedia formats."
 ---
 
 <table cellpadding="5">
@@ -58,16 +58,16 @@
       <th valign="top" align="right">
          <em>Abstract:</em>
       </th>
-      <td>This Internet-Draft proposes the "app" URI scheme for the Archive and Packaging Protocol.
-         app URIs can be used to consume or reference hypermedia resources bundled inside a
-         file archive or a mobile application package, as well as to resolve URIs for archive
-         resources within a programmatic framework. This URI scheme provides mechanisms to
-         generate a unique base URI to represent the root of the archive, so that relative
-         URI references in a bundled resource can be resolved within the archive without having
-         to extract the archive content on the local file system. An app URI can be used for
-         purposes of isolation (e.g. when consuming multiple archives), security constraints
-         (avoiding "climb out" from the archive), or for externally identifying sub-resources
-         in other hypermedia formats.
+      <td>This Internet-Draft proposes the Archive and Packaging Pointer URI scheme app. app
+         URIs can be used to consume or reference hypermedia resources bundled inside a file
+         archive or an application package, as well as to resolve URIs for archive resources
+         within a programmatic framework. This URI scheme provides mechanisms to generate a
+         unique base URI to represent the root of the archive, so that relative URI references
+         in a bundled resource can be resolved within the archive without having to extract
+         the archive content on the local file system. An app URI can be used for purposes
+         of isolation (e.g. when consuming multiple archives), security constraints (avoiding
+         “climb out” from the archive), or for externally identifying sub-resources referenced
+         by hypermedia formats.
       </td>
    </tr>
 </table>

src/specs/draft-soilandreyes-app.xml

@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" ?>
 <service primary="IETF" secondary="I-D" id="soilandreyes-app">
-    <title>The Archive and Packaging Pointer system</title>
-    <documentation source="http://tools.ietf.org/html/draft-soilandreyes-app">This Internet-Draft proposes the "app" URI scheme for the Archive and Packaging Protocol. app URIs can be used to consume or reference hypermedia resources bundled inside a file archive or a mobile application package, as well as to resolve URIs for archive resources within a programmatic framework. This URI scheme provides mechanisms to generate a unique base URI to represent the root of the archive, so that relative URI references in a bundled resource can be resolved within the archive without having to extract the archive content on the local file system. An app URI can be used for purposes of isolation (e.g. when consuming multiple archives), security constraints (avoiding "climb out" from the archive), or for externally identifying sub-resources in other hypermedia formats.</documentation>
+    <title>The Archive and Packaging Pointer (app) URI scheme</title>
+    <documentation source="http://tools.ietf.org/html/draft-soilandreyes-app">This Internet-Draft proposes the Archive and Packaging Pointer URI scheme app. app URIs can be used to consume or reference hypermedia resources bundled inside a file archive or an application package, as well as to resolve URIs for archive resources within a programmatic framework. This URI scheme provides mechanisms to generate a unique base URI to represent the root of the archive, so that relative URI references in a bundled resource can be resolved within the archive without having to extract the archive content on the local file system. An app URI can be used for purposes of isolation (e.g. when consuming multiple archives), security constraints (avoiding “climb out” from the archive), or for externally identifying sub-resources referenced by hypermedia formats.</documentation>
     <uri-scheme def="app">
         <documentation source="http://tools.ietf.org/html/draft-soilandreyes-app#section-2">The "app" URI scheme follows the RFC 3986 syntax for hierarchical URIs. The "app-authority" component provides a unique identifier for the opened archive. The "path-absolute" component provides the absolute path of a resource (e.g. a file or directory) within the archive.</documentation>
     </uri-scheme>