Open Bug 227321 Opened 21 years ago Updated 19 years ago

URN used in RDF data in Mozilla are not compliant with RFC 2141

Categories

(SeaMonkey :: UI Design, defect)

defect
Not set
minor

Tracking

(Not tracked)

People

(Reporter: pierre.thierry, Assigned: jag+mozilla)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031024 Debian/1.5-2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031024 Debian/1.5-2

RFC 2141 clearly states that a formal URN must begin with 'X-' (or 'x-', because
this aprt of the URN is case-insensitive) when it has not been registered to the
IANA. BCP 66 (RFC 3406) explains how to fill a application for a registered
namespace.

Future versions of Mozilla should either use urn:x-mozilla:... or register a
namesapce.

Reproducible: Always

Steps to Reproduce:
is this a dupe of bug 48545?
AFAICC they are different (conflicting) fixes for the same bug: use of an
invalid URN scheme.

This one proposes MF either use an experimental `x-mozilla' URN scheme or
register their own with IANA.  The other one proposes that we use the INET
scheme. AFAICC from googling around the INET scheme is no longer around (and has
not been registered as a URN scheme with IANA) although one of the other
existing registered schemes <http://www.iana.org/assignments/urn-namespaces> may
be appropriate.

Seems to make most sense to keep this one and WONTFIX the other one (which
doesn't make much sense esp. summary to me anyway).  Also, summary on this one
should probably be "URNs in RDF data use invalid URN scheme".
Product: Core → Mozilla Application Suite
*** Bug 48545 has been marked as a duplicate of this bug. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
Filed that would might need to change in order to fix this bug:
 <http://lxr.mozilla.org/seamonkey/find?string=.rdf>
OS: Linux → All
Hardware: PC → All
This is somewhat related to the huge bug 12161 (vocabulary cleanup).

At least urn:root is hooked up all over the place (including extensions), so this
is a scary bug.
You need to log in before you can comment on or make changes to this bug.