Opened 10 years ago

Closed 6 years ago

#20 closed enhancement (fixed)

namespace URI is non-standard

Reported by: prjemian Owned by: prjemian
Priority: major Version:
Keywords: Cc:

Description

Daniel Franke writes:

... This is probably already known: 
reading the example files from the wiki, libxml2 keeps complaining

bimodal-test1.xml:4: namespace warning : xmlns: URI cansas1d/1.0 is not 
absolute
                xmlns="cansas1d/1.0"
                                    ^

The W3C Recommendation on Namespaces [1] has:
"2.2 Use of URIs as Namespace Names
[...]
 The use of relative URI references, including same-document references, in 
namespace declarations is deprecated."

Regards

	Daniel


[1] http://www.w3.org/TR/REC-xml-names/#iri-use

Change History (6)

comment:1 Changed 10 years ago by prjemian

  • Owner set to prjemian
  • Status changed from new to assigned

Now that the WWW site is established, it is possible to use a namespace with a URL such as http://www.smallangles.net/cansas1d/1.0. Since the "cansas1d/1.0" standard has been released this will remain unchanged for the v1.0 standard. For the v1.1 standard and beyond, a conforming URI will be chosen.

This should be one of the first steps in starting the v1.1 standard.

comment:2 Changed 10 years ago by prjemian

possible conforming choices for the v1.1 could be:

  • URN style: urn:cansas-1d:1.1
  • URL style: http://www.smallangles.net/cansas1d/1.1

The URL can be used to advise about a WWW site that either provides the schema or the documentation. But, it is not required for the URL to actually exist. This causes confusion for those that assume the URL must exist.

The URN conforms, is compact, and yet provides no other information about the location of the actual standard.

URL is probably better. Better still if it describes an existing and available WWW page.

comment:4 Changed 7 years ago by prjemian

  • Resolution set to wontfix
  • Status changed from assigned to closed

for consistency with the 1.0 standard and to avoid confusing those who implement either canSAS1d/1.0 or canSAS1d/1.1, change of the form of the namespace will not be made at this time

best to make this change with an XML implementation of the multi-dimensional standard

comment:5 Changed 6 years ago by prjemian

  • Resolution wontfix deleted
  • Status changed from closed to reopened
  • Type changed from defect to enhancement

proposition to change targetnamespace

from   cansas1d/1.1
to     urn:cansas1d:1.1

This means the XML file header would change from

<SASroot version="1.1"
		xmlns="cansas1d/1.1"
		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
		xsi:schemaLocation="cansas1d/1.1
				    http://www.cansas.org/svn/1dwg/trunk/cansas1d.xsd"
		>

to

<SASroot version="1.1"
		xmlns="urn:cansas1d:1.1"
		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
		xsi:schemaLocation="urn:cansas1d:1.1 
				    http://www.cansas.org/svn/1dwg/trunk/cansas1d.xsd"
		>

Note the change from smallangles.net to cansas.org!

Last edited 6 years ago by prjemian (previous) (diff)

comment:6 Changed 6 years ago by prjemian

  • Resolution set to fixed
  • Status changed from reopened to closed

fixed by [262]

Note: See TracTickets for help on using tickets.