Changeset 2604


Ignore:
Timestamp:
29/01/14 23:41:26 (6 years ago)
Author:
fielding@…
Message:

(editorial) disambiguate the it in explanation of absolute-path; see #531

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2603 r2604  
    448448  }
    449449  @bottom-center {
    450        content: "Expires August 1, 2014";
     450       content: "Expires August 2, 2014";
    451451  }
    452452  @bottom-right {
     
    490490      <meta name="dct.creator" content="Reschke, J. F.">
    491491      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    492       <meta name="dct.issued" scheme="ISO8601" content="2014-01-28">
     492      <meta name="dct.issued" scheme="ISO8601" content="2014-01-29">
    493493      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    519519            <tr>
    520520               <td class="left">Intended status: Standards Track</td>
    521                <td class="right">January 28, 2014</td>
     521               <td class="right">January 29, 2014</td>
    522522            </tr>
    523523            <tr>
    524                <td class="left">Expires: August 1, 2014</td>
     524               <td class="left">Expires: August 2, 2014</td>
    525525               <td class="right"></td>
    526526            </tr>
     
    551551            in progress”.
    552552         </p>
    553          <p>This Internet-Draft will expire on August 1, 2014.</p>
     553         <p>This Internet-Draft will expire on August 2, 2014.</p>
    554554      </div>
    555555      <div id="rfc.copyrightnotice">
     
    10741074            </p>
    10751075            <p id="rfc.section.2.7.p.2">The definitions of "URI-reference", "absolute-URI", "relative-part", "scheme", "authority", "port", "host", "path-abempty",
    1076                "segment", "query", and "fragment" are adopted from the URI generic syntax. An "absolute-path" rule is defined, differing
    1077                slightly from RFC 3986's "path-absolute" in that it allows a leading "//". A "partial-URI" rule is defined for protocol elements
    1078                that allow a relative URI but not a fragment.
     1076               "segment", "query", and "fragment" are adopted from the URI generic syntax. An "absolute-path" rule is defined for protocol
     1077               elements that can contain a non-empty path component. (This rule differs slightly from RFC 3986's path-abempty rule, which
     1078               allows for an empty path to be used in references, and path-absolute rule, which does not allow paths that begin with "//".)
     1079               A "partial-URI" rule is defined for protocol elements that can contain a relative URI but not a fragment component.
    10791080            </p>
    10801081            <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span>  <a href="#uri" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#RFC3986" id="rfc.xref.RFC3986.3"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.1">Section 4.1</a>&gt;
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2603 r2604  
    824824   "path-abempty", "segment", "query", and "fragment" are adopted from the
    825825   URI generic syntax.
    826    An "absolute-path" rule is defined, differing slightly from
    827    RFC 3986's "path-absolute" in that it allows a leading "//".
     826   An "absolute-path" rule is defined for protocol elements that can contain a
     827   non-empty path component. (This rule differs slightly from RFC 3986's
     828   path-abempty rule, which allows for an empty path to be used in references,
     829   and path-absolute rule, which does not allow paths that begin with "//".)
    828830   A "partial-URI" rule is defined for protocol elements
    829    that allow a relative URI but not a fragment.
     831   that can contain a relative URI but not a fragment component.
    830832</t>
    831833<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="URI-reference"><!--exported production--></iref><iref primary="true" item="Grammar" subitem="absolute-URI"/><iref primary="true" item="Grammar" subitem="scheme"/><iref primary="true" item="Grammar" subitem="authority"/><iref primary="true" item="Grammar" subitem="absolute-path"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="fragment"/><iref primary="true" item="Grammar" subitem="segment"/><iref primary="true" item="Grammar" subitem="uri-host"/><iref primary="true" item="Grammar" subitem="partial-URI"><!--exported production--></iref>
Note: See TracChangeset for help on using the changeset viewer.