Ignore:
Timestamp:
Sep 15, 2012, 11:06:23 PM (7 years ago)
Author:
fielding@…
Message:

(editorial) description of resource is now in p2, remove redundant xrefs to 3986

File:
1 edited

Legend:

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

    r1894 r1899  
    4646  <!ENTITY OPTIONS                "<xref target='Part2' x:rel='#OPTIONS' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4747  <!ENTITY qvalue                 "<xref target='Part2' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     48  <!ENTITY resource               "<xref target='Part2' x:rel='#resource' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4849  <!ENTITY status-codes           "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4950  <!ENTITY status-1xx             "<xref target='Part2' x:rel='#status.1xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    780781<t>
    781782   Uniform Resource Identifiers (URIs) <xref target="RFC3986"/> are used
    782    throughout HTTP as the means for identifying resources. URI references
    783    are used to target requests, indicate redirects, and define relationships.
    784    HTTP does not limit what a resource might be; it merely defines an interface
    785    that can be used to interact with a resource via HTTP. More information on
    786    the scope of URIs and resources can be found in <xref target="RFC3986"/>.
     783   throughout HTTP as the means for identifying resources (&resource;).
     784   URI references are used to target requests, indicate redirects, and define
     785   relationships.
    787786</t>
    788787  <x:anchor-alias value="URI-reference"/>
     
    800799   "absolute-URI", "relative-part", "port", "host",
    801800   "path-abempty", "path-absolute", "query", and "authority" from the
    802    URI generic syntax <xref target="RFC3986"/>.
     801   URI generic syntax.
    803802   In addition, we define a partial-URI rule for protocol elements
    804803   that allow a relative URI but not a fragment.
Note: See TracChangeset for help on using the changeset viewer.