Re: RFC 8288 on Web Linking

Heather,

is there a pointer to the changes? I mean I presume such a spec already existed before, and this is just a new version. At first glance, I have not seen anything in the document that stroke me as absolutely new

(Maybe one: that it is possible to use a URI for a 'private' link relation type, ie, not necessarily use a registered one. But that may have been available before…)

In any case, I have added a reference to our reading list[1]

Thanks!

Ivan


[1] https://github.com/w3c/publ-wg/wiki/Reading-List <https://github.com/w3c/publ-wg/wiki/Reading-List>



> On 25 Oct 2017, at 16:33, Heather Flanagan (RFC Series Editor) <rse@rfc-editor.org <mailto:rse@rfc-editor.org>> wrote:
> 
> Hello all,
> 
> Thought this new RFC, on the standards track within the IETF, might be of interest.
> -Heather
> 
> -------- Forwarded Message --------
> Subject: RFC 8288 on Web Linking
> Date: Tue, 24 Oct 2017 16:25:35 -0700 (PDT)
> From: rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>
> To: ietf-announce@ietf.org <mailto:ietf-announce@ietf.org>, rfc-dist@rfc-editor.org <mailto:rfc-dist@rfc-editor.org>
> CC: rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>, drafts-update-ref@iana.org <mailto:drafts-update-ref@iana.org>
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 8288
> 
>         Title:      Web Linking
>         Author:     M. Nottingham
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       October 2017
>         Mailbox:    mnot@mnot.net <mailto:mnot@mnot.net>
>         Pages:      24
>         Characters: 50797
>         Obsoletes:  RFC 5988
> 
>         I-D Tag:    draft-nottingham-rfc5988bis-08.txt
> 
>         URL:        https://www.rfc-editor.org/info/rfc8288 <https://www.rfc-editor.org/info/rfc8288>
> 
>         DOI:        10.17487/RFC8288
> 
> This specification defines a model for the relationships between
> resources on the Web ("links") and the type of those relationships
> ("link relation types").
> 
> It also defines the serialisation of such links in HTTP headers with
> the Link header field.
> 
> This is now a Proposed Standard.
> 
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards <https://www.rfc-editor.org/standards>) for the
> standardization state and status of this protocol.  Distribution of this
> memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce <https://www.ietf.org/mailman/listinfo/ietf-announce>
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>
> 
> For searching the RFC series, see https://www.rfc-editor.org/search <https://www.rfc-editor.org/search>
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk <https://www.rfc-editor.org/retrieve/bulk>
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
> 


----
Ivan Herman, W3C
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>