W3C home > Mailing lists > Public > www-archive@w3.org > July 2009

diff: draft-nottingham-http-link-header-05 to 06

From: Sean B. Palmer <sean@miscoranda.com>
Date: Mon, 13 Jul 2009 20:38:31 +0100
Message-ID: <b6bb4d890907131238r17d7c9d7r2524c90e51d86986@mail.gmail.com>
To: www-archive <www-archive@w3.org>
5c5
< Internet-Draft                                            April 17, 2009
---
> Internet-Draft                                             July 12, 2009
8c8
< Expires: October 19, 2009
---
> Expires: January 13, 2010
12c12
<                   draft-nottingham-http-link-header-05
---
>                   draft-nottingham-http-link-header-06
45c45
<    This Internet-Draft will expire on October 19, 2009.
---
>    This Internet-Draft will expire on January 13, 2010.
55c55
< Nottingham              Expires October 19, 2009                [Page 1]
---
> Nottingham              Expires January 13, 2010                [Page 1]
57c57
< Internet-Draft                 Web Linking                    April 2009
---
> Internet-Draft                 Web Linking                     July 2009
85,87c85,87
<      6.2.  Link Relation Type Registry  . . . . . . . . . . . . . . .  8
<    7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
<    8.  Internationalisation Considerations  . . . . . . . . . . . . . 12
---
>      6.2.  Link Relation Type Registry  . . . . . . . . . . . . . . .  9
>    7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
>    8.  Internationalisation Considerations  . . . . . . . . . . . . . 13
91,96c91,96
<    Appendix A.  Notes on Using the Link Header with HTML4 . . . . . . 14
<    Appendix B.  Notes on Using the Link Header with Atom  . . . . . . 15
<    Appendix C.  Defining New Link Serialisations  . . . . . . . . . . 16
<    Appendix D.  Acknowledgements  . . . . . . . . . . . . . . . . . . 16
<    Appendix E.  Document history  . . . . . . . . . . . . . . . . . . 17
<    Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19
---
>    Appendix A.  Notes on Using the Link Header with HTML4 . . . . . . 15
>    Appendix B.  Notes on Using the Link Header with Atom  . . . . . . 16
>    Appendix C.  Defining New Link Serialisations  . . . . . . . . . . 17
>    Appendix D.  Acknowledgements  . . . . . . . . . . . . . . . . . . 17
>    Appendix E.  Document history  . . . . . . . . . . . . . . . . . . 18
>    Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20
111c111
< Nottingham              Expires October 19, 2009                [Page 2]
---
> Nottingham              Expires January 13, 2010                [Page 2]
113c113
< Internet-Draft                 Web Linking                    April 2009
---
> Internet-Draft                 Web Linking                     July 2009
160c160
<    [RFC4288]: type-name.
---
>    [RFC4288]: type-name and subtype-name.
167c167
< Nottingham              Expires October 19, 2009                [Page 3]
---
> Nottingham              Expires January 13, 2010                [Page 3]
169c169
< Internet-Draft                 Web Linking                    April 2009
---
> Internet-Draft                 Web Linking                     July 2009
186c186
<    [RFC3986], because common protocols (such as HTTP) do not support
---
>    [RFC3986], because many protocols (such as HTTP) do not support
223c223
< Nottingham              Expires October 19, 2009                [Page 4]
---
> Nottingham              Expires January 13, 2010                [Page 4]
225c225
< Internet-Draft                 Web Linking                    April 2009
---
> Internet-Draft                 Web Linking                     July 2009
246c246
<    There are two kinds of relation types; registered and extension.
---
>    There are two kinds of relation types: registered and extension.
255,256c255,256
<    This draft establishes an IANA registry of such relation types; see
<    Section 6.2.
---
>    This specification establishes an IANA registry of such relation
>    types; see Section 6.2.
266c266
<    compared in a case-insensitive fashion.
---
>    compared character-by-character in a case-insensitive fashion.
279c279
< Nottingham              Expires October 19, 2009                [Page 5]
---
> Nottingham              Expires January 13, 2010                [Page 5]
281c281
< Internet-Draft                 Web Linking                    April 2009
---
> Internet-Draft                 Web Linking                     July 2009
290,291c290,291
<    type, clients SHOULD NOT access that resource to avoid overburdening
<    its server.
---
>    type, clients SHOULD NOT automatically access that resource to avoid
>    overburdening its server.
296,298c296,298
<    Note that while extension relation types are required to be URIs, but
<    a serialisation of links MAY specify that they are expressed in
<    another form, as long as they can be converted to URIs.
---
>    Note that while extension relation types are required to be URIs, a
>    serialisation of links MAY specify that they are expressed in another
>    form, as long as they can be converted to URIs.
312c312
<                        | ( "type" "=" type-name )
---
>                        | ( "type" "=" type-name "/" subtype-name )
326,329c326,329
<    conversion to one, if necessary) inside angle brackets ("<>").  If
<    the URI-Reference is relative, it MUST be resolved as per [RFC3986],
<    Section 5.  Note that any base IRI from the body's content is not
<    applied.
---
>    conversion to one, if necessary; see [RFC3987], Section 3.1) inside
>    angle brackets ("<>").  If the URI-Reference is relative, it MUST be
>    resolved as per [RFC3986], Section 5.  Note that any base IRI from
>    the body's content is not applied.
335c335
< Nottingham              Expires October 19, 2009                [Page 6]
---
> Nottingham              Expires January 13, 2010                [Page 6]
337c337
< Internet-Draft                 Web Linking                    April 2009
---
> Internet-Draft                 Web Linking                     July 2009
357c357
<    The "title", "title*" and any link-extension link-params are
---
>    The "title", "title*", "type" and any link-extension link-params are
367a368,373
>    The "type" parameter, when present, is a hint indicating what the
>    media type of the result of dereferencing the link should be.  Note
>    that this is only a hint; for example, it does not override the
>    Content-Type header of a HTTP response obtained by following the
>    link.
>
382,384d387
<    The example below shows an instance of the Link header encoding
<    multiple links, and also the use of RFC 2231 encoding to encode both
<    non-ASCII characters and language information.
387a391,394
> Nottingham              Expires January 13, 2010                [Page 7]
>

> Internet-Draft                 Web Linking                     July 2009
>
388a396
>    Similarly,
389a398
>    Link: </>; rel="http://example.net/foo"
391,393c400,401
< Nottingham              Expires October 19, 2009                [Page 7]
<

< Internet-Draft                 Web Linking                    April 2009
---
>    indicates that the root resource ("/") has the extension relation
>    "http://example.net/foo".
394a403,405
>    The example below shows an instance of the Link header encoding
>    multiple links, and also the use of RFC 2231 encoding to encode both
>    non-ASCII characters and language information.
402c413
<    language ("de"), and contains the Unicode code point \u'00E4' ("LATIN
---
>    language ("de"), and contains the Unicode code point U+00E4 ("LATIN
432d442
< 6.2.  Link Relation Type Registry
434,437d443
<    This specification establishes the Link Relation Type Registry,
<    located at <http://www.iana.org/assignments/relation/>, and updates
<    Atom [RFC4287] to refer to it in place of the "Registry of Link
<    Relations".
439,440d444
<    The requirements for registered relation types are described in
<    Section 4.1.
442,443c446,449
<    Relation types may be registered on the advice of a Designated Expert
<    (appointed by the IESG or their delegate), with a Specification
---
>
> Nottingham              Expires January 13, 2010                [Page 8]
>

> Internet-Draft                 Web Linking                     July 2009
445a452
> 6.2.  Link Relation Type Registry
447,449c454,456
< Nottingham              Expires October 19, 2009                [Page 8]
<

< Internet-Draft                 Web Linking                    April 2009
---
>    This specification establishes the Link Relation Type Registry, and
>    updates Atom [RFC4287] to refer to it in place of the "Registry of
>    Link Relations".
450a458,459
>    The requirements for registered relation types are described in
>    Section 4.1.
451a461,462
>    Relation types are registered on the advice of a Designated Expert
>    (appointed by the IESG or their delegate), with a Specification
465a477
>    o  Notes: [optional]
485a498,507
>
>
>
>
>
> Nottingham              Expires January 13, 2010                [Page 9]
>

> Internet-Draft                 Web Linking                     July 2009
>
>
498,507d519
<
<
<
<
<
< Nottingham              Expires October 19, 2009                [Page 9]
<

< Internet-Draft                 Web Linking                    April 2009
<
<
542a555,563
>
>
>
>
> Nottingham              Expires January 13, 2010               [Page 10]
>

> Internet-Draft                 Web Linking                     July 2009
>
>
554,563d574
<
<
<
<
<
< Nottingham              Expires October 19, 2009               [Page 10]
<

< Internet-Draft                 Web Linking                    April 2009
<
<
598a610,619
>
>
>
>
>
> Nottingham              Expires January 13, 2010               [Page 11]
>

> Internet-Draft                 Web Linking                     July 2009
>
>
610,619d630
<
<
<
<
<
< Nottingham              Expires October 19, 2009               [Page 11]
<

< Internet-Draft                 Web Linking                    April 2009
<
<
629a641,647
>    o  Relation Name: service
>    o  Description: Indicates a URI that can be used to retrieve a
>       service document.
>    o  Reference: [RFC5023]
>    o  Notes: When used in an Atom document, this relation specifies Atom
>       Publishing Protocol service documents by default.
>
643a662,675
>    o  Relation Name: up
>    o  Description: Refers to a parent document in a hierarchy of
>       documents.
>    o  Reference: [this document]
>
>
>
>
>
> Nottingham              Expires January 13, 2010               [Page 12]
>

> Internet-Draft                 Web Linking                     July 2009
>
>
669,675d700
<
<
< Nottingham              Expires October 19, 2009               [Page 12]
<

< Internet-Draft                 Web Linking                    April 2009
<
<
698a724,731
>
>
>
> Nottingham              Expires January 13, 2010               [Page 13]
>

> Internet-Draft                 Web Linking                     July 2009
>
>
721,731d753
<
<
<
<
<
<
< Nottingham              Expires October 19, 2009               [Page 13]
<

< Internet-Draft                 Web Linking                    April 2009
<
<
757a780,787
>
>
>
> Nottingham              Expires January 13, 2010               [Page 14]
>

> Internet-Draft                 Web Linking                     July 2009
>
>
759a790,803
>    [W3C.REC-rdfa-syntax-20081014]
>               Pemberton, S., Birbeck, M., Adida, B., and S. McCarron,
>               "RDFa in XHTML: Syntax and Processing", World Wide Web
>               Consortium Recommendation REC-rdfa-syntax-20081014,
>               October 2008,
>               <http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014>.
>
>    [W3C.REC-xhtml-basic-20080729]
>               Baker, M., Wugofski, T., Ishikawa, M., Stark, P., Matsui,
>               S., and T. Yamakami, "XHTML[TM] Basic 1.1", World Wide Web
>               Consortium Recommendation REC-xhtml-basic-20080729,
>               July 2008,
>               <http://www.w3.org/TR/2008/REC-xhtml-basic-20080729>.
>
780,787d823
<
<
<
< Nottingham              Expires October 19, 2009               [Page 14]
<

< Internet-Draft                 Web Linking                    April 2009
<
<
797a834,843
>
>
>
>
>
> Nottingham              Expires January 13, 2010               [Page 15]
>

> Internet-Draft                 Web Linking                     July 2009
>
>
812a859,863
>    Note that RDFa [W3C.REC-rdfa-syntax-20081014] defines a different way
>    to map link relations to URIs in XHTML
>    [W3C.REC-xhtml-basic-20080729].  Although this convention is not
>    defined for HTML4, some authors may still use it there.
>
835a887,889
>    feed IRI or an entry ID, depending on where it appears; generally,
>    feed-level links are obvious candidates for transmission as a Link
>    header.
836a891
>    When serialising an atom:link into a Link header, it is necessary to
839,841d893
< Nottingham              Expires October 19, 2009               [Page 15]
<

< Internet-Draft                 Web Linking                    April 2009
842a895,897
> Nottingham              Expires January 13, 2010               [Page 16]
>

> Internet-Draft                 Web Linking                     July 2009
844,845d898
<    feed IRI or an entry ID, depending on where it appears; generally,
<    feed-level links are candidates for transmission as a Link header.
847d899
<    When serialising an atom:link into a Link header, it is necessary to
851c903,904
<    specification defines them as URIs, to aid in their comparison.
---
>    specification re-defines them as URIs, to simplify and reduce errors
>    in their comparison.
854,862c907,915
<    absolute URIs, because a base URI is defined for the registry.  Such
<    relation types SHOULD be converted to the appropriate registered form
<    (e.g., "http://www.iana.org/assignments/relation/self" to "self") so
<    that they are not mistaken for extension relation types.
<
<    Furthermore, Atom link relations are compared in a case-sensitive
<    fashion; therefore, registered link relations SHOULD be converted to
<    their registered form (usually, lower case) when serialised in an
<    Atom document.
---
>    absolute URIs.  Such relation types SHOULD be converted to the
>    appropriate registered form (e.g.,
>    "http://www.iana.org/assignments/relation/self" to "self") so that
>    they are not mistaken for extension relation types.
>
>    Furthermore, Atom link relations are always compared in a case-
>    sensitive fashion; therefore, registered link relations SHOULD be
>    converted to their registered form (usually, lower case) when
>    serialised in an Atom document.
865c918
<    associated with a single link, atom:link does not.  In this case, a
---
>    serialised in a single link, atom:link does not.  In this case, a
870c923
<    used as link-extensions.
---
>    used as link-extensions to maintain fidelity.
891a945,946
>    themselves are sourced from several documents; see the applicable
>    references.
895c950,951
< Nottingham              Expires October 19, 2009               [Page 16]
---
>
> Nottingham              Expires January 13, 2010               [Page 17]
897c953
< Internet-Draft                 Web Linking                    April 2009
---
> Internet-Draft                 Web Linking                     July 2009
900,902d955
<    themselves are sourced from several documents; see the applicable
<    references.
<
904,905c957,958
<    encouraged and gave feedback to this draft, especially including
<    Frank Ellermann, Roy Fielding and Julian Reschke.
---
>    encouraged and gave feedback to this specification, especially
>    including Frank Ellermann, Roy Fielding and Julian Reschke.
911a965,972
>    -06
>
>    o  Added "up" and "service" relation types.
>    o  Fixed "type" attribute syntax and added prose.
>    o  Added note about RDFa and XHTML to HTML4 notes.
>    o  Removed specific location for the registry, since IANA seems to
>       have its own ideas about that.
>
942,946d1002
<    o  Relation types split into registered (non-URI) and extension
<       (URI).
<    o  Changed wording around finding URIs for registered relation types.
<    o  Changed target and context URIs to IRIs (but not extension
<       relation types).
951c1007
< Nottingham              Expires October 19, 2009               [Page 17]
---
> Nottingham              Expires January 13, 2010               [Page 18]
953c1009
< Internet-Draft                 Web Linking                    April 2009
---
> Internet-Draft                 Web Linking                     July 2009
955a1012,1016
>    o  Relation types split into registered (non-URI) and extension
>       (URI).
>    o  Changed wording around finding URIs for registered relation types.
>    o  Changed target and context URIs to IRIs (but not extension
>       relation types).
999,1002d1059
<    -01
<
<    o  Changed syntax of link-relation to one or more URI; dropped
<       Profile.
1006,1007c1063
<
< Nottingham              Expires October 19, 2009               [Page 18]
---
> Nottingham              Expires January 13, 2010               [Page 19]
1009c1065,1066
< Internet-Draft                 Web Linking                    April 2009
---
> Internet-Draft                 Web Linking                     July 2009
>
1010a1068
>    -01
1011a1070,1071
>    o  Changed syntax of link-relation to one or more URI; dropped
>       Profile.
1059,1063c1119
<
<
<
<
< Nottingham              Expires October 19, 2009               [Page 19]
---
> Nottingham              Expires January 13, 2010               [Page 20]

-- 
Sean B. Palmer, http://inamidst.com/sbp/
Received on Monday, 13 July 2009 19:39:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:18:25 GMT