I would suggest that the point of the identifier is that it represents some resource, and merely marking up a string as being an identifier doesn't accomplish much without being able to dereference it and obtain the resource it identifies. Saying "urn:isbn:<whatever>" is an identifier doesn't do much good; the point is that given that identifier, I can tell that it's talking about a book and I can go obtain information about that book. In which case, a href="" comes to mind. I think there's room for some debate here.
- David
On 11/23/05, Tantek Çelik <[EMAIL PROTECTED]> wrote:
Hello C. Hudley, welcome to the list!
On 11/23/05 9:54 AM, "C. Hudley" <[EMAIL PROTECTED]> wrote:
> Has any work been done on a format for identifiers? By "identifier" I
> mean "some kind of arbitrary string that identifies the object at hand
> in some system". Examples of the kinds of identifiers that might be
> in scope would be ISBNs for books, PMIDs for pubmed, node ids for
> weblog entries, DOIs for journal articles, flickr ids for flickr
> images, etc.
Yes, this is a solved problem.
See http://www.ietf.org/rfc/rfc3986.txt
AKA Uniform Resource Identifier (URI).
Thanks,
Tantek
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
_______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
