RE : [docbook] Schema and MS Office beta

[Frédéric Glorieux <frederic.glorieux@ajlsm.com>]

	Hi,

	I took some experience in W3C.Schema by using or writing,
especially on mixed namespace models (W3C:..., Library of Congress:...,
Dublin Core...). 
	I ask Norm about the authority of the docbook.xsd, and if a
subset of docbook in w3c.schema need to be expressed as a redefinition
(like on some other public schemas). 
	For example, you are using a general dc.xsd (Dublin Core
metadatas), and for some local usages, you can constraints identifiers
to some pattern as a redefinition. It's better than to edit the
original, which could be distant. Then you can check big lots of
documents by validation.
	Redefinition was only for the official release, because there
are not a lot of tools able to fully understand the syntax. XMetal3
refused mixed namespaces. XML.Spy loose himself on mixed contents
(example:docbook.xsd, problem with hierarchies based on <xs:group/>,
could be fixed with abstract elements).
	For docbook, I began a working schema (on xMetal, XML.Spy, XXE,
msxml4). I'm implementing the generic elements (don't need too
software-specific stuff). It's day to day fixed on the documents we are
authoring, sometimes adding constraints, sometimes suppressing rules. 
	It's not the best example. I thought a lot but finally, I
haven't chosen to strictly follow the entities of the docbook.dtd
(probably because I'm not able to keep the full tree in my head). Also,
the dtd/entities style conducts to the <xs:group/> logic, but W3C.Schema
could allow other constructions, which have some understanding abilities
(because I first learned schema before DTD).

> I made a customization layer using the DTD and would like to "port"
> that work to W3C Schema.

Have you tried automatic converters?

> I have seen posts about namespaces

	docbook.xsd doesn't seem to advice an official namespace-uri()
(prefix could be a problem for DTDs, not for schemas or xsl). 
	For myself, first thing was to allow other namespaces in some
docbook elements (example: in <bibliocoverage/>, allow GML for
geographic location). Problems could arrive if an organisation is using
more than one noNameSpace schema. But biggest one is to rewrite your
docbook-xsl pack. 
	In fact, we need to play a lot with ns. For example, the free
version of XXE (used by some of our clients) is restricted, no support
for @xsi:noNamespaceSchemaLocation, but you have to use namespace-uri
beginning by  http://www.xmlmind.com/xmleditor/schema/... (a kind of
light signature).

	Welcome in schemas. Have you tested the new Office (I'm ordering
it from Europe)?

	Fred.