On Feb 2, 2008 5:50 AM, Daniel Aleksandersen < [EMAIL PROTECTED]> wrote:
> > What part of the publication with urn:issn:1234-567 does "2008-01" > > apply to? The first letter of the 2008th word, perhaps? > > It is supposed to identify the date. This is no standard! But the #part > would solve my problem with keeping my ISSN in all feeds, but still have > the ID be unique. Just be aware that applications aware of ISSN URNs may reject this URN as invalid if it contains a fragment. RFC3044 doesn't specify what a fragment means in the context of an ISSN URN, and the URN spec explicitly cautions against its use in URNs generally: 2.3.2 The other reserved characters RFC 1630 [2] reserves the characters "/", "?", and "#" for particular purposes. The URN-WG has not yet debated the applicability and precise semantics of those purposes as applied to URNs. Therefore, these characters are RESERVED for future developments. Namespace developers SHOULD NOT use these characters in unencoded form, but rather use the appropriate %-encoding for each character. This means your Atom IDs (ISSN URNs) may only be readable to humans. Using a tag: URI as Aristotle suggested would let you use it however you wanted (still with no computers understanding its semantics). If your publication has a canonical online presence, perhaps the atom:id could just be the (permanent) URL to that issue online? And this is all assuming you still feel you need distinct atom:ids for the different versions of your feed. I agree with Antone that there's no reason they can't be the same, but do whatever makes the most sense for you. Good luck. David
