On Nov 23, 2006, at 22:42, Henry Story wrote:
This is very nice, in that it opens up the possibility of placing good RDF descriptions of these links at the http://www.iana.org/ assignments/relation/,
How could new link relations be described in RDF to such a degree that the description would actually be useful for software processing but simple enough to actually be implemented? Is it realistic to have UAs whacking IANA server effectively performing a DDoS on it?
as well as making the link relation very extensible (people who want to try out new link relations, can just use their own, unambiguous url).
How are full URIs distinguished from strings that need to be appended to "http://www.iana.org/assignments/relation/"; to obtain the full URI? Are UAs supposed to look for a colon as with XForms input methods? Where is this specified?
In practice people seem to want to use one-word link relations even when they are coming up with their own.
I would recommend you adopt that too. Perhaps you can even adopt the iana name space. If we could get them to put the appropriate rdf document at that location, people who created/coined new link relations could describe these relations as being superproperties or subroperties of relations the browser already knows, which would allow the browser to partially interpret those.
Well, RDF is not viewed that favorably by the WHATWG. Also, the barrier for entry for the IANA registration process is likely too high. (It certainly is for MIME types.) As for using the same namespace, the HTML5 definitions for the link types don't necessarily match the Atom definitions.
Recently, a WHATWG-managed registry for HTML5 rel values has been discussed informally. The idea was that conformance checkers could consult an online registry instead of only allowing a fixed list of values or allowing everything. RDF is an overkill for this. Even XMDP isn't the simplest thing that could possibly work. The simplest thing that could possibly work is a GETtable text/plain; charset=utf-8 resource at a well-known URI with one rel value per LF-separated line.
-- Henri Sivonen [EMAIL PROTECTED] http://hsivonen.iki.fi/
