Discussion of edit-URIs versus public-URIs has tended to focus on
Media Collections but what about the case of wiki formats for blog
entries (or wiki entries for that matter)?
Leonardo, the non-APP software that currently runs my blog,
effectively has 3 representations for a given blog entry (ignoring
title-only feeds, etc)
1. the atom entry in my full-content feed with embedded HTML
2. the HTML page (the value of [EMAIL PROTECTED]"alternate"]/href in the
above entry)
3. the raw wiki-format that is edited and PUT
In an APP implementation (like Demokritos), I might expect to have:
1. the atom entry in my public full-content feed with embedded HTML
2. the HTML page (the value of [EMAIL PROTECTED]"alternate"]/href in the
above entry)
3. the atom entry with embedded wiki format that is edited and PUT
This is different from something like an image where the entities
involved might be:
1. the raw image, both publicly retrievable by a browser and what
would be PUT by an APP client
2. then atom entry in a public feed with a content/@src pointing to
the raw image
3. an HTML page about the image which might be the link
[EMAIL PROTECTED]"alternate"]/href in the atom entry above
Both of these are different from what one might expect in the case of
a blog entry that is edited in HTML:
1. the atom entry in a feed with embedded HTML content - also the
same as what is retrieved and PUT by an APP client
2. the HTML page for the blog entry
It's not clear to me that the examples we are talking about (whether
in support of an entry/media distinction or not) really cover all
three cases.
And note I haven't even raised the question of entries in a
collection feed.
My apologies if I've missed some previous conclusive discussion of
this matter.
James
--
James Tauber http://jtauber.com/
journeyman of some http://jtauber.com/blog/
