hello.
John Panzer wrote:
Ross Singer wrote:
... what argument are you making against using the http URI the
identifier? I understand if the tag URI is necessary for internal
reasons for the application, but if the http URI is, indeed, a viable
identifier for the resource... why not use that?
If the http URL is a permanent identifier that will never disappear
unless the resource itself does, and will never be reassigned to some
different resource, then sure. In practice it's very hard to guarantee
this.
it's not that hard to guarantee that it will never be re-assigned, and
that's all it takes ("disappearing" is not something that can happen to
the identifier, i guess you mean that it stops working because of some
server or domain reorganization issues). if you encode the date into it
as many publishing schemes do, for example, re-assignment becomes almost
a non-issue. and it's ok if it stops working from the identifier point
of view, all that's required is that it needs to provide identification
properties.
cheers,
dret.
