Re: Proposal to register rel="about"

["Peter Keane" <pkeane@xxxxxxxxxxxxxxx>]

What about the case of a Media Link Enty?

This from AtomPub spec 9.6:

"The Media Link Entry contains the metadata and IRI of the (perhaps
non-textual) Media Resource. The Media Link Entry thus makes the
metadata about the Media Resource separately available for retrieval
and alteration."

Isn't this a specified case in which the atom elements are describing
the media resource and not the entry?

I've struggled a bit in my own implementation with this exact issue,
and wishing there was a switch that could be flipped to say "this is
an MLE".  I am not sure that in practice it matters all that much,
since a specific use case will clearly suggest which you are talking
about.  I believe the challenge that Herbert is pointing to is that we
need to be more precise is we are going to be deriving RDF from the
Atom entry.

--peter keane

On Thu, Sep 18, 2008 at 11:28 AM, Brian Smith <brian@xxxxxxxxxxxxxx> wrote:
>
> Herbert van de Sompel wrote:
>> if <content src="xxx" /> 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="xxx" 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).
>
> In Atom the metadata always pertains to the entry it is contained in and not
> anything else. Atom:title always is the title of the entry that contains it.
> The difference between inline and out-of-line content is purely syntactic;
> except for XML documents that have a DOCTYPE, you can encode the same entry
> with inline or out-of-line content and the meaning doesn't change.
>
> I do agree that there are some counter-intuitive situations. For example, if
> the content/@src links to a PDF document, then the PDF document will often
> have its own metadata (especially the title, authorship, and modification
> time) encoded in it. Most applications want to think of the atom:title  as
> being the title of the PDF document. But, that isn't the case; the
> atom:title is always the title of the entry whose content is the PDF file.
> There is no fixed relationship between the metadata for the entry and the
> metadata for the entry's content.
>
> Here is an example where we avoid using out-of-line content; notice that the
> entry and its content have different titles, because atom:entry/atom:title
> describes the entry's title, not the entry's content's title:
>
>   <entry ...>
>   <title>Title of the Entry</title>
>   <content type='application/xhtml+xml'>
>      <html:html ...>
>         <html:head><html:title>Title of the HTML
> document</html:title></html:head>
>         ...
>      </html>
>   </content>
>   </entry>
>
> - Brian
>
>