Namespace ID: urn- Registration Information: Registration version number: 1 Registration date: 2001-09-08 Declared registrant of the namespace: Name: Sean B. Palmer email address: Declaration of syntactic structure: urn := 'urn:' nid ':' name nid := 'urn-' n n := number-assigned-by-IANA name := [A-Za-z][A-Za-z0-9]* Examples of valid URNs under this scheme include: urn:urn-n:someName urn:urn-n:anon05178 Relevant ancillary documentation: The name component is identical to the one found in the W3C's N-Triples specification:- http://www.w3.org/2001/sw/RDFCore/ntriples/#name - N-Triples, revision 1.9, W3C RDF Core WG Internal Working Draft All URNs defined herein conform to:- http://www.ietf.org/rfc/rfc2141.txt - "URN Syntax", RFC 2141, May 1997, Moats, R. Identifier uniqueness considerations: These identifiers need to be unique for the context of their use, which is the scope of the quantification for each particular anonymous none. Processors should ensure that the anonymous nodes are indeed unique within their contexts. Identifier persistence considerations: URNs have the requirement that they be persistently bound to one resource, and not reassigned. Since the scope of these identifiers is a single document, that is easy to ensure. Process of identifier assignment: Assignment of this URN scheme is fully open, as long as the syntax rules are obeyed. The author of the document gets to choose the identifiers used for the anonymous nodes (indeed, these may be automatically generated, and often are). Process for identifier resolution: None specified. Conformance with URN Syntax: Processors MUST follow the lexical equivalence considerations of the URN specification. Validation mechanism: None specified. Scope: Global.