uid-brainstorming: Difference between revisions
Jump to navigation
Jump to search
Ed Summers (talk | contribs) |
Ed Summers (talk | contribs) |
||
Line 18: | Line 18: | ||
== See Also == | == See Also == | ||
* [http://www.ietf.org/rfc/rfc2396.txt RFC 2396] Uniform Resource Identifiers | |||
* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces. | * [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces. | ||
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span. | * [http://ocoins.info COinS] for putting attaching openurl context objexts to a span. |
Revision as of 04:39, 22 April 2006
UID Brainstorming
This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.
Authors
- Ed Summers
Experience
- a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers (RFC 2396)
Goals Requirements
- can we reuse uid from hCard
See Also
- RFC 2396 Uniform Resource Identifiers
- RFC 4452 the "info" URI scheme for information assets with identifiers in public namespaces.
- COinS for putting attaching openurl context objexts to a span.
- unAPI has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
- Tag URI an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.