(Difference between revisions)

Jump to: navigation, search
(added notes about should & must)
Line 53: Line 53:
* [[geo]]
* [[geo]]
* [[hcard|hCard]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]
* [[abbr-design-pattern]]

Revision as of 01:57, 26 April 2006


UID Brainstorming

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.



Goals Requirements


UIDs that are URLs

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>

Should rather than Must

A UID *should* rather than *must* be a URL. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

UID + URL -> permalink?

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

abbr pattern

Use the abbr-design-pattern to allow identifiers to be more fully described.

<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>


Just use UID from hCard


See Also

Related Discussion

uid-brainstorming was last modified: Wednesday, December 31st, 1969