- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 20 Jan 2010 12:01:17 +0100
- To: Apps Discuss <discuss@apps.ietf.org>
- CC: "public-html@w3.org" <public-html@w3.org>, HTTP Working Group <ietf-http-wg@w3.org>
Thanks, Mark. I'd like to make sure that everybody is aware that these are past-LC changes, and they *are* significant; see <http://tools.ietf.org/html/draft-nottingham-http-link-header-07#appendix-E>: o Allowed multiple spaces between relation types. o Relaxed requirements for registered relations. o Removed Defining New Link Serialisations appendix. o Added Field registry. o Added registry XML format. o Changed registration procedure to use mailing list(s), giving the Designated Experts more responsibility for the smooth running of the registry. o Loosened prohibition against media-specific relation types to SHOULD NOT. o Disallowed registration of media-specific relation types (can still be used as extension types). o Clarified that parsers are responsible for resolving relative URIs. o Fixed ABNF for extended-initial-value. o Fixed title* parameter quoting in example. o Added notes for registered relations that lack a reference. o Added hreflang parameter. o Clarified status of 'rev'. o Removed advice to use @profile in HTML4. o Clarified what multiple *title and hreflang attributes mean. o Disallowed multiple type, rel and title attributes. o Removed text about absolute URI form of registered relations. o Required registered relations to conform to sgml-name (now just rel-relation-type). o Required registered relations to be lowercase. o Made comparison of extension relations case insensitive. o Clarified requirements on registered relation types regarding media types, etc. o Allowed applications to ignore links with anchor parameters if they're concerned. o Made 'rev' text a bit less confusing. o Extension relation URIs SHOULD be all-lowercase. o Added media parameter. o Required applications to specifically call out use of anchor parameter. Thus everybody who's interested in this specification should review these changes as soon as possible. Best regards, Julian Mark Nottingham wrote: > > Begin forwarded message: > >> From: Internet-Draft@ietf.org >> Date: 19 January 2010 4:30:02 PM AEDT >> To: mnot@pobox.com, draft-nottingham-http-link-header@tools.ietf.org,lisa.dusseault@gmail.com >> Subject: New Version Notification - draft-nottingham-http-link-header-07.txt >> >> New version (-07) has been submitted for draft-nottingham-http-link-header-07.txt. >> http://www.ietf.org/internet-drafts/draft-nottingham-http-link-header-07.txt >> Sub state has been changed to AD Follow up from New Id Needed >> >> Diff from previous version: >> http://tools.ietf.org/rfcdiff?url2=draft-nottingham-http-link-header-07 >> >> IETF Secretariat. > > > -- > Mark Nottingham http://www.mnot.net/ > > _______________________________________________ > Apps-Discuss mailing list > Apps-Discuss@ietf.org > https://www.ietf.org/mailman/listinfo/apps-discuss >
Received on Wednesday, 20 January 2010 11:01:56 UTC