* Simon Brown <[EMAIL PROTECTED]> [2005-08-13 11:00]:
> If Tim *moves* his blog to www.timbray.com/ongoing, would you
> expect his Atom IDs to remain the same?
Yes. That’s what the spec says and that’s what IDs are for: they
*NEVER change*. Period. Regardless of what else you do with your
content
* Tim Bray <[EMAIL PROTECTED]> [2005-08-13 16:50]:
> The fact that I use HTTP URIs for identifiers reflects my
> belief that good Web citizenship requires that once something
> is published and its URI widely disseminated, it should never
> ever be moved; so in my case this scenario is unlikely to
--On August 13, 2005 8:34:49 AM + Simon Brown <[EMAIL PROTECTED]> wrote:
> If Tim *moves* his blog to www.timbray.com/ongoing, would you expect his Atom
> IDs to remain the same? Spec aside, this has some implications for storing
> Atom
> IDs next to content they identify, which I imagine do
On Aug 13, 2005, at 1:34 AM, Simon Brown wrote:
Just to quote an example, Tim is currently using URL based Atom
IDs, such as :
http://www.tbray.org/ongoing/
http://www.tbray.org/ongoing/When/200x/2005/08/09/Web-2.0
If Tim *moves* his blog to www.timbray.com/ongoing, would you
expect his A
Simon brown raises a valid point on the "Spec explanations for
Pebble?" thread:
That same paragraph starts, "When an Atom Document is relocated,
migrated,
syndicated, republished, exported or imported, the content of its
atom:id
element MUST NOT change.". For me, this paragraph talk
Graham Parks <[EMAIL PROTECTED]> writes:
> On 12 Aug 2005, at 9:16 am, Carey Evans wrote:
>
> > First, where does the spec actually say that the atom:id shouldn't
> > change if the blog moves to a different domain? I think that if the
> > URL of the blog changes, it means that the Atom Feed Do