James,
This is not about easier parsing, but about unambiguous interpretation of what the atom metadata elements pertain to:
(*) <content src="" /> is widely used, but there is no spec out there that tells us to make the following interpretation:
if <content src="" /> is used then the atom metadata elements pertain to xxx instead of to the Atom Entry (entry/id).
As a matter of fact, when looking at existing Atom use of src="" there are cases in which the atom metadata pertains to xxx and there are cases in which it pertains to the Atom Entry (/entry/id).
(*) <link rel="about" href="" /> would allow for unambiguous interpretation through the introduction of a link to explicitly states what the atom metadata is about.
I hope this helps clarifying our perspective.
Cheers
Herbert
On Fri, Sep 12, 2008 at 1:03 PM, James Holderness
<j4_james@xxxxxxxxxxx> wrote:
Erling Wegger Linde wrote:
It would be extremely useful
for a client to know that the summary of the Atom entry is actuall the
summary property of an issue e.g. <link rel="about"
href="" href="http://issuetracker/project1/issue1" target="_blank">http://issuetracker/project1/issue1">. You could not embed the
represenation found at http://issuetracker/project1/issue1 in the
entry using <content src="" href="http://issuetracker/project1/issue1" target="_blank">http://issuetracker/project1/issue1"> as
this probably would be hard for a non-human client to parse.
Can you explain how a non-human client would find this:
<content src="" />
harder to parse than this:
<link rel="about" href="" />
I don't get it.
Regards
James
--
Herbert Van de Sompel
Digital Library Research & Prototyping
Los Alamos National Laboratory, Research Library
http://public.lanl.gov/herbertv/