Groups - Draft of the DITA 1.2 XSDs (xsd1.2-20100925.zip) uploaded

Hi,

I have a fix for the ditabase.xsd issue.
I still get an error when validating the XSD itself. When I validate the
instance doc against the XSD I don't get any errors.  To resolve the
issue I had to create a ditabaseMod.xsd so that I pushed the reference
to xml:lang into another file.

I also removed all extraneous imports
of xml.xsd.  I only included them if the file actually referenced
an attribute from the xml namespace.  It fixes the issue, but it also
means that we would need to update the spec as well so that we can document
the new file.

We have a couple of options:
   1) Start the next review
cycle with the current uploaded package and fix it later.
   2) Fix the issue one Monday.
 That would mean regenerating the XSD package. As well as updating
the appropriate topics in the spec and regenerate it for Tuesdays meeting.

At least one topic would have to be
updated, possibly two.  I can figure out what topics needs to be updated
later.  

Kind regards,
Eric

ditabaseMod.xsd
<?xml version="1.0" encoding="UTF-8"?>

<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/">


<xs:import
namespace="http://www.w3.org/XML/1998/namespace"
 schemaLocation="../../base/xsd/xml.xsd"/>

 <xs:import
namespace="http://dita.oasis-open.org/architecture/2005/"
schemaLocation="../../base/xsd/ditaarch.xsd"/>

  

  <xs:annotation>

                <xs:documentation>The
&lt;<keyword>dita</keyword>&gt;
element provides a top-level container

      for multiple topics when you create documents using
the ditabase XSD. The

      &lt;<keyword>dita</keyword>&gt;
element lets you create any sequence of concept,

      task, and reference topics, and the ditabase XSD lets
you further nest these

      topic types inside each other. The &lt;<keyword>dita</keyword>&gt;
element has

      no particular output implications; it simply allows
you to create multiple

      topics of different types at the same level in a single
document.</xs:documentation>

        </xs:annotation>

        <xs:element
name="dita"
type="dita.class"/>

        <xs:complexType
name="dita.class">

                <xs:choice
maxOccurs="unbounded">

                
       <xs:group
ref="ditabase-info-types"/>

                </xs:choice>

                <xs:attribute
ref="ditaarch:DITAArchVersion"/>

                <xs:attribute
ref="xml:lang"/>

                <xs:attributeGroup
ref="global-atts"/>

        </xs:complexType>

  

  </xs:schema>




Eric A. Sirois

Staff Software Developer

DB2 Universal Database - Information Development

DITA XML Schema Architect and DITA Open Toolkit Developer

IBM Canada Ltd. - Toronto Software Lab

Email: 

Phone:(905) 413-2841

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. 





From:
Eric Sirois/Toronto/IBM@IBMCA

To:


Date:
09/25/2010 01:17 AM

Subject:
[dita] Groups - Draft of the DITA 1.2
XSDs (xsd1.2-20100925.zip) uploaded




Contains all changes from the first DITA 1.2 Public
Review:

* Add @copy-to to topichead

* Add <ph> into <linktext> within maps

* Add base domains (highlight, utilities, hazard statement) to the

following doctypes: base map, classification map, subject scheme,

learning

bookmap, learning map

* Add base domains and technical content domains (abbreviated form,

programming, software, UI) do bookmap and technical content map

* Fix validation errors in L&T XSDs for duplicate inclusion of

commonElementsGrp.xsd

* Fix for learningContent so that is does not allow no-topic-nesting.

* Fixes for MSXML4 parser (xml:lang and extension of mixed content model)


Note: There is still an issue with ditabase.xsd when validating against

MSXML4.  I get an odd error:


Description: /schema[1]/import[2] The value of the 'namespace' attribute
on

an import element was 'http://dita.oasis-open.org/architecture/2005/',

matching the value of the enclosing schema's 'targetNamespace' attribute.


If someone has some suggestions for a fix, it would be greatly appreciated.

I'm scouring the Net for a fix, but I haven't found a fix for it yet. It

validates fine with other XML parsers.


Kind regards,

Eric




 -- Mr Eric Sirois


The document revision named Draft of the DITA 1.2 XSDs

(xsd1.2-20100925.zip) has been submitted by Mr Eric Sirois to the OASIS

Darwin Information Typing Architecture (DITA) TC document repository.  This

document is revision #20 of xsd1.2-20080506.zip.


Document Description:

Draft implementation of the DITA 1.2 XML Schemas.


The package includes a URN based (requiring XML catalogs), TR9401 or SGML

Open catalogs and  URL based (for development purposes) schemaLocation

values.


The file _Updates.txt within the package contains a list of included

features. This file will be included with each draft until the changes
are

complete.


View Document Details:

http://www.oasis-open.org/committees/document.php?document_id=39550


Download Document:  

http://www.oasis-open.org/committees/download.php/39550/xsd1.2-20100925.zip


Revision:

This document is revision #20 of xsd1.2-20080506.zip.  The document
details

page referenced above will show the complete revision history.



PLEASE NOTE:  If the above links do not work for you, your email application

may be breaking the link into two pieces.  You may be able to copy
and paste

the entire link address into the address field of your web browser.


-OASIS Open Administration