To explain it with an analogy: Modularization is like a program library,  
which a program then links to. Trying to compile a program library without  
a main program will cause several things to be reported as missing, in  
particular the main program.

With Modularization it is the same: it is a markup library, the driver is  
analogous to the program, and is just as essential when trying to use it  
for validation.

Best wishes,

Steven Pemberton

On Mon, 01 May 2006 03:07:42 +0200, Shane McCarron <shane@aptest.com>  
wrote:

>
> M12N schema require a driver module - in which those things are to be  
> defined.  XHTML 1.1 and XHTML Basic 1.0 schema implementations will have  
> examples of these driver modules when they are released.
>
> Christoph Schneegans wrote:
>> Hi!
>>
>> I was trying to incorporate the XML Schemas from
>> <http://www.w3.org/TR/2006/PR-xhtml-modularization-20060213/ > into my
>> validation service <http://schneegans.de/sv/ >. However, I wasn't
>> successful. It seems to me that there are many references to types
>> which are not defined anywhere, namely
>>
>>   xhtml.BlkNoForm.mix
>>   xhtml.Block.mix
>>   xhtml.Common.extra
>>   xhtml.Core.extra.attrib
>>   xhtml.Flow.mix
>>   xhtml.FlowNoTable.mix
>>   xhtml.Global.Common.extra
>>   xhtml.Global.core.extra.attrib
>>   xhtml.Global.I18n.extra.attrib
>>   xhtml.head.content
>>   xhtml.I18n.class
>>   xhtml.I18n.extra.attrib
>>   xhtml.Inline.extra
>>   xhtml.Inline.mix
>>   xhtml.InlinePre.mix
>>   xhtml.InlNoAnchor.mix
>>   xhtml.InlNoRuby.mix
>>   xhtml.InlPhras.class
>>   xhtml.InlPres.class
>>   xhtml.InlSpecial.class
>>   xhtml.InlStruct.class
>>   xhtml.Misc.class
>>
>> I've tested with .NET 2.0 and MSXML 5.0. Did anyone manage to compile
>> these schemas?
>>
>>
>