search

w3c / wpub

W3C Web Publications
https://w3c.github.io/wpub/
Other
78 stars 19 forks source link

Change rel URLs to tokens #431

Closed mattgarrish closed 5 years ago

mattgarrish commented 5 years ago

As noted in the tag feedback, the use of URLs for relations is an uncommon choice. It also means that if we don't standardize these with IANA before publishing, existing content will either have to be changed or user agents will forever be stuck supporting the URLs.

In the interests of clarity, can we just change:

and deal with IANA registration separately?

iherman commented 5 years ago

I do not have a problem with that; the arguments are compelling.

HadrienGardeur commented 5 years ago

[...] the use of URLs for relations is an uncommon choice

Actually it isn't. URLs are usually recommended as an extensibility mechanism for rel values:

https://tools.ietf.org/html/rfc5988#section-4.2

Applications that don't wish to register a relation type can use an extension relation type, which is a URI [RFC3986] that uniquely identifies the relation type.

If the proposed tokens get registered at IANA, it's fine though because there's no reason to use an URL in this case.

mattgarrish commented 5 years ago

If the proposed tokens get registered at IANA, it's fine though because there's no reason to use an URL in this case.

This is what makes them an odd choice. We're planning to register them, as we say in the notes for each, and URLs are only for relations you don't intend to register.

If for some reason they get rejected, then we should look at how else they might be expressed.