Re #1: not if we want it to express multiple titles, each with a different language.
I could not figure out what you were trying to say with the rest of your points.
From: Santosh Rajan [mailto:email@example.com]
Sent: Saturday, December 12, 2009 7:06 AM
Subject: Re: [xri-comment] XRD <uri> vs. Link: anchor=
Right. In that case it would be better for XRD to specify a new separate field for language instead of multiple titles. And titles are generally considered as cardinality 0 or 1.
1) Can't the XRD specify a language field and avoid multiple titles?
2) Since when, machine readable formats, and machine based information, cannot figure out a language, if it weren't clearly specified?
3) So you are saying XRD speaks "machine language"?, XRD can't understand any other machine language other than your own? Are we going back to the stone age here?
On Fri, Dec 11, 2009 at 2:02 AM, Eran Hammer-Lahav <firstname.lastname@example.org> wrote:
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.
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.