OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: XRD <uri> vs. Link: anchor=


Hi Jonathan,

The <URI> element is the same as the link target in Link header (the <> enclosed value), or the 'href' attribute in HTML. XRD does not support the anchor functionality. It would be a bit odd to allow an XRD describing one resource to make statements about other resources' relations.

EHL

> -----Original Message-----
> From: Jonathan Rees [mailto:jar@creativecommons.org]
> Sent: Thursday, December 10, 2009 5:11 AM
> To: xri-comment@lists.oasis-open.org; Eran Hammer-Lahav
> Cc: Mark Nottingham; Ben Adida
> Subject: XRD <uri> vs. Link: anchor=
> 
> [ bcc: www-tag  for the TAG's information.  To broaden the discussion
> beyond XRD change the cc: list as appropriate. ]
> 
> XRD <uri> seems to do exactly what the Link: header's anchor= parameter
> does [1]. It would be nice if the two used the same token to communicate
> this function.  As <uri> is not descriptive of the role played by the URI, I
> recommend updating XRD to match Link:, by renaming the <uri> element (or
> attribute, should you go that route) to be <anchor>.
> 
> Jonathan
> 
> [1] http://www.mnot.net/drafts/draft-nottingham-http-link-header-07.txt
> 
> (p.s. I wonder if HTML5's <link> element should have an 'anchor'
> attribute, for symmetry ...)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]