URI scheme for TC subcommittees

[Eric Sirois <esirois@ca.ibm.com>]

Hello, Fellow TC members;

During the latter part of DITA 1.1 the TC approved the use of URIs and a
URI scheme to uniquely identify DITA XML Schema and its components.  As the
TC subcommittees are getting closer to delivering new industry
specializations they should create URIs for their schemas.  The URIs are
used to uniquely identify their schemas so as to make easier to validate
the content to be processed by XML applications.  This is similar to how
DTDs use unique a PUBLIC identifier to identify DTDs.

The design pattern for the current base schemas are:

urn:oasis:names:tc:dita:xsd:<filename.xsd>:<version>

I propose that the TC subcommittees use the following design pattern to
uniquely identify their schemas and its components.

urn:oasis:names:tc:dita:sc:<subcommittee-name>:xsd:<filename.xsd>:<version>


Here are some samples of how URI would be used in the schema documents and
XML instance documents.  For instance,
urn:oasis:names:tc:dita:sc:learning:xsd:learningOverview.xsd:1.0

The URIs would replace the any instance where are relative or absolute path
URL would have normally been used.

<?xml version="1.0" encoding="utf-8"?>
<learningSummary xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:noNamespaceSchemaLocation="../schemas/learningSummary.xsd"
 id="learningsummary">

would be

<?xml version="1.0" encoding="utf-8"?>
<learningSummary xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:noNamespaceSchemaLocation=
"urn:oasis:names:tc:dita:sc:learning:xsd:learningSummary.xsd:1.0"
 id="learningsummary">

The same would apply to include/redefine/import in the schemas documents

<!--  ================ INFO TYPES =====================  -->
  <xs:include schemaLocation=
"urn:oasis:names:tc:dita:sc:learning:xsd:learningAssessmentGrp.xsd:1.0"/>

Kind regards,
Eric
Eric A. Sirois
Staff Software Developer
DB2 Universal Database - Information Development
DITA Migration and Tools Development
IBM Canada Ltd. - Toronto Software Lab
Email: esirois@ca.ibm.com
Blue Pages (Internal)

"Transparency and accessibility requirements dictate that public
information and government
transactions avoid depending on technologies that imply or impose a
specific product or
platform on businesses or citizens" - EU on XML-based office document
formats.