Namespace ID: urn- Registration Information: Registration version number: 1 Registration date: 2001-@@-@@ Declared registrant of the namespace: Name: Sean B. Palmer email address: Declaration of syntactic structure: urn := "urn:" nid ":" nss nid := "urn-" n n := number-assigned-by-IANA nss := note note := ( western | ratio ) western := hertz ":" westernnote ratio := hertz ":" rationote westernnote := "A" | "Bb" | "B" | "C" | "Cs" | "D" | "Eb" | "E" | "F" "Fs" | "G" | "Gs" rationote := number "/" number number := digitxo *digit digitxo := "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" digit := "0" | digitxo hertz := number [ "." number ] ( "Hz" | "KHz" ) Examples of valid URNs under this scheme include: urn:urn-:A urn:urn-:1/72 urn:urn-:440Hz:A Relevant ancillary documentation: All URNs defined herein conform to:- Moats, R. "URN Syntax", RFC 2141, May 1997. Identifier uniqueness considerations: These URNs may map many to one, but not one to many. Identifier persistence considerations: URNs have the requirement that they be persistently bound to one resource, and not reassigned. Process of identifier assignment: The assignment of URNs is closed by the syntactic rules. Process for identifier resolution: These URNs resolve to a note. That is, they resolve to the concept of a certain amount (frequency) of vibrations on an archetypal string. Perhaps by activiating a link to such a URN, a musical note could be played. In that way, crude HyperText instruments could be formed. Conformance with URN Syntax: Processors SHOULD follow the lexical equivalence considerations of the URN specification, although postal services tend to be flexible. Validation mechanism: None specified. Scope: Global; music is music.