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: [xri-comment] XRD <uri> vs. Link: anchor=

Regarding point #2, title is left as an element because there is a fundamental difference between XRD and ATOM/HTML. XRD does not have a language context since it is a machine readable format for machine-based information. ATOM and HTML almost always have a specific context language and almost always one. This means in XRD we need to allow multiple titles with different languages for each link. You can’t do that easily using attributes.




From: Santosh Rajan [mailto:santrajan@gmail.com]
Sent: Thursday, December 10, 2009 7:15 AM
To: Jonathan Rees
Cc: xri-comment@lists.oasis-open.org; Eran Hammer-Lahav; Mark Nottingham; Ben Adida; openid-general@lists.openid.net
Subject: Re: [xri-comment] XRD <uri> vs. Link: anchor=



Hi Jonathan,


This is only the least of the problems with XRD. As far as the "link" element is concerned. Here are a few points I have to make. Please have a look at this post first of all.



1) The XRD "Link" element today looks exactly like the Atom "link" element.

2) Except for one difference. The "Title" element. The XRD Title element is not an attribute in a Link element, its an element on its own right, with the value being the title value.

3) This is ridiculous. They have not given a good argument for having a title element inside the link, instead of an attribute.

4) And here is another very unscientific argument. The "link" element looks very beautiful with all values described as attributes. Putting any value, inside an element, inside a link element makes it look positively ugly.


Of cource my argument can always be brushed aside as coming from a "crazy" as was posted here in this link.




On Thu, Dec 10, 2009 at 6:40 PM, Jonathan Rees <jar@creativecommons.org> wrote:

[ 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>.


[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 ...)

This publicly archived list offers a means to provide input to the
OASIS Extensible Resource Identifier (XRI) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: xri-comment-subscribe@lists.oasis-open.org
Unsubscribe: xri-comment-unsubscribe@lists.oasis-open.org
List help: xri-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/xri-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xri


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