[ah; my original post turned up, sorry for the double posting]
Luke Arno wrote:
> Ok, I am throwing this out there for the sake of argument...
>
> Could a server not issue a unique "stub" id with introspection? Then
> a client could just increment on the end of that. Ids could be globally
> unique and a server could change it or not when receiving a POST.
Luke,
probably because that's operationally the same as changing a real id*.
If people feel we need to go with invalid Atom, I would be +1 to
something like an empty tag or a marker URI.
Maybe we need a new template pace:
<atom:id>{id}</atom:id>
That has one advantage - if you get one of those downstream you'll know
what, and roughly where, something went wrong (anyone who's ever used
Ant or certain web templating libraries will know what I'm talking about).
The downside is by the time we're done working around invalidity, we
might have well specced a templating langauge.
cheers
Bill
* the whole notion of real and unreal ids makes me think we're well off
the happy path.
