editorial LC comments on draft-nottingham-http-link-header-07.txt

Hi,

below are some comments of editorial nature:

Section 1., paragraph 3:
OLD:

    Furthermore, an HTTP header-field for conveying typed links was
    defined in [RFC2068], but removed from [RFC2616], due to a lack of
    implementation experience.  Since then, it has been implemented in
    some User-Agents (e.g., for stylesheets), and several additional use
    cases have surfaced.

NEW:

    Furthermore, an HTTP header-field for conveying typed links was
    defined in Section 19.6.2.4 of [RFC2068], but removed from [RFC2616],
    due to a lack of implementation experience.  Since then, it has been
    implemented in some User-Agents (e.g., for stylesheets), and several
    additional use cases have surfaced.

(be nice to the reader and a bit more specific in the RFC 2068 reference)

Section 2., paragraph 0:
OLD:

    [[ Feedback is welcome on the ietf-http-wg@w3.org mailing list,
    although this is NOT a work item of the HTTPBIS WG. ]]

Please either move into a front page note, or clearly mark this as
something to be removed before publication.

Section 2., paragraph 3:
OLD:

    Additionally, the following rules are included from [RFC3986]: URI
    and URI-Reference; from [RFC4288]: type-name and subtype-name; from
    [W3C.REC-html401-19991224]: MediaDesc, and from [RFC4646]: Language-
    Tag.

NEW:

    Additionally, the following rules are included from [RFC3986]: URI
    and URI-Reference; from [RFC4288]: type-name and subtype-name; from
    [W3C.REC-html401-19991224]: MediaDesc, and from [RFC5646]: Language-
    Tag.

RFC 4646 was updated by RFC 5646.

Section 4.1., paragraph 3:
OLD:

    Registered relation types MUST NOT constrain the media type of the
    context IRI, and MUST NOT constrain the available representation
    media types of the target IRI.  However, they MAY specify the
    behaviours and properties of the target resource (e.g., allowable
    methods, request and response media types which must be supported).

Does "methods" refer to HTTP here? maybe clarify this.


Section 4.1., paragraph 4:
OLD:

    Additionally, specific applications of linking may have additional
    per-relation type attributes which are advantageous to register.  For
    example, some link relations might not be appropriate to use in
    particular contexts, or might have common behaviour such as whether
    their content should be archived with the page.  To accommodate this,
    new per-entry fields MAY be added to the registry, by registering
    them in the Link Relation Field Registry Section 6.3.

NEW:

    Additionally, specific applications of linking may have additional
    per-relation type attributes which are advantageous to register.  For
    example, some link relations might not be appropriate to use in
    particular contexts, or might have common behaviour such as whether
    their content should be archived with the page.  To accommodate this,
    new per-entry fields MAY be added to the registry, by registering
    them in the Link Relation Field Registry (Section 6.3).

(Missing brackets at the paragraph end)

Section 5.4., paragraph 3:
OLD:

    The "media" parameter, when present, is used to indicate intended
    destination medium or media for style information (see
    [W3C.REC-html401-19991224], Section 6.13.  Note that this may be
    updated by [W3C.CR-css3-mediaqueries-20090915]).  Its value MUST be
    quoted if it contains a semicolon (";") or comma (","), and there
    MUST NOT be more than one media parameter in a link-value.

NEW:

    The "media" parameter, when present, is used to indicate intended
    destination medium or media for style information (see
    [W3C.REC-html401-19991224], Section 6.13).  Note that this may be
    updated by [W3C.CR-css3-mediaqueries-20090915]).  Its value MUST be
    quoted if it contains a semicolon (";") or comma (","), and there
    MUST NOT be more than one media parameter in a link-value.

Missing closing bracket in HTML4 reference.

Section 5.4., paragraph 5:
OLD:

    The "title*" parameter MAY be used encode this label in a different
    character set, and/or contain language information as per [RFC2231].
    When using the enc2231-string syntax, producers MUST NOT use a
    charset value other than 'ISO-8859-1' or 'UTF-8'.  The "title*"
    parameter MAY appear more than once in a given link-value, but each
    occurrence MUST indicate a different language; occurrences after the
    first for a given language MUST be ignored by parsers.

NEW:

    The "title*" parameter MAY be used to encode this label in a
    different character set, and/or contain language information as per
    [RFC2231].  When using the enc2231-string syntax, producers MUST NOT
    use a charset value other than 'ISO-8859-1' or 'UTF-8'.  The "title*"
    parameter MAY appear more than once in a given link-value, but each
    occurrence MUST indicate a different language; occurrences after the
    first for a given language MUST be ignored by parsers.

...may be used *to* encode...


Section 9.1., paragraph 9:
OLD:

    [RFC4646]  Phillips, A. and M. Davis, "Tags for Identifying
               Languages", RFC 4646, September 2006.

NEW:

    [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
               IANA Considerations Section in RFCs", BCP 26, RFC 5226,
               May 2008.

Section 9.2., paragraph 7:
OLD:

    [W3C.CR-css3-mediaqueries-20090915]
               Glazman, D., Celik, T., Lie, H., and A. Kesteren, "Media
               Queries", World Wide Web Consortium CR CR-css3-
               mediaqueries-20090915, September 2009,
               <http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915>.

    [W3C.REC-html401-19991224]
               Jacobs, I., Raggett, D., and A. Hors, "HTML 4.01
               Specification", World Wide Web Consortium
               Recommendation REC-html401-19991224, December 1999,
               <http://www.w3.org/TR/1999/REC-html401-19991224>.

    [W3C.REC-rdfa-syntax-20081014]
               Adida, B., Pemberton, S., McCarron, S., and M. Birbeck,
               "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]
               Wugofski, T., Matsui, S., Baker, M., Yamakami, T.,
               Ishikawa, M., and P. Stark, "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>.

NEW:

    [W3C.CR-css3-mediaqueries-20090915]
               Glazman, D., Celik, T., Lie, H., and A. Kesteren, "Media
               Queries", W3C Candidate Recommendation CR-css3-
               mediaqueries-20090915, September 2009,
               <http://www.w3.org/TR/2009/
               CR-css3-mediaqueries-20090915/>.

    [W3C.REC-html401-19991224]
               Jacobs, I., Raggett, D., and A. Hors, "HTML 4.01
               Specification", W3C Recommendation REC-html401-19991224,
               December 1999,
               <http://www.w3.org/TR/1999/REC-html401-19991224/>.

    [W3C.REC-rdfa-syntax-20081014]
               Adida, B., Pemberton, S., McCarron, S., and M. Birbeck,
               "RDFa in XHTML: Syntax and Processing", W3C
               Recommendation REC-rdfa-syntax-20081014, October 2008,
               <http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014/>.

    [W3C.REC-xhtml-basic-20080729]
               Wugofski, T., Matsui, S., Baker, M., Yamakami, T.,
               Ishikawa, M., and P. Stark, "XHTML Basic 1.1", W3C
               Recommendation REC-xhtml-basic-20080729, July 2008,
               <http://www.w3.org/TR/2008/REC-xhtml-basic-20080729/>.

Please make the W3C references consistent: W3C instead of "Word Wide Web
Consortium", and make sure the URIs use the current format (trailing slash).

Optimally, also reduce the length of the anchor names (I'll be happy to
supply diffs).

Best regards, Julian

Received on Thursday, 21 January 2010 14:05:29 UTC