I have another use case which I personally think justifies registering
On Fri, Sep 12, 2008 at 4:45 AM, Antone Roundy <electriceel@xxxxxxxxx> wrote:
>
> Herbert van de Sompel wrote:
>>
>> The Atom use cases we refer to use Entries as containers to provide
>> "metadata" about some web resource other than the Entry itself. For example,
>> the GData Entry <http://gdata.youtube.com/feeds/api/videos/S_bcAOlK0io > is
>> about the YouTube video by the Cribs
>> <http://www.youtube.com/watch?v=S_bcAOlK0io>
>
> My impression upon looking at the entry is that you could do this instead
> (and add an atom:summary element with textual content):
>
> <content src="" href="http://www.youtube.com/watch?v=S_bcAOlK0io" target="_blank">http://www.youtube.com/watch?v=S_bcAOlK0io" />
the rel="about" for Atom Entries, please correct me if I'm wrong about
this.
What if you use Atom entries as wrappers for other resources?
Let's say you have an issuetracker (Jira, Trac, Bugzilla etc.) which
you create/manage issues in, through a user interface. Such
issuetrackers may provide SOAP, REST etc. endpoints, but probably
nothing that outputs Atom and/or RDF (using the baetle ontology). You
want to create an AtomPub service that provides collections of
issues/bugs for instance all issues belonging to a project.
An issue has a summary, a creator (author), and other properties that
would match some of the elements of an Atom entry. (other details
could be put in the <content> element..). 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.
Furthermore, even if it were possible to embed some sort of XML
representation of the issue, what if you would like to express it in
RDF/XML or N3? Well you could of course create a new
resource/representation e.g http://issuetrackerwrapper/projec1/issue1
and link this into your Atom entry, but I think that would be a waste
of energy and resources, compared to just use <content
type="application/rdf+xml">RDF content here..</content>. I think
rel="about" would be a powerful add-on to AtomPub and would make it
more compatible with the Semantic web.
Best regards,
- Erling
>
> What that would do is incorporate the YouTube video as part of the entry.
> That would seem the appropriate method if you want the entry metadata to
> talk about the external resource.
>
> If the content of the entry is commentary about an external resource, then I
> could see having an "about" link relation to indicate that, but then the
> entry metadata would be talking about the entry, not the external resource.
>
>> We understand that an RFC that specifies the proposed rel="about"
>> relationship would have to express which child elements of atom:entry
>> pertain to the resource described by the Entry, and which to the Entry
>> itself, whenever a rel="about" is present in an Entry.
>
> The idea of a link relation changing the meaning of a core Atom element
> doesn't sound right to me.
>
> Antone
>
>