[Osr-101] Misleading neutron specs example

[Thomas Comiotto]

Hi

> Whereas another question would be: how shall we treat documents with 
> multiple different schemas? Imagine e.g. a XHTML document with 
> embedded MathML.
>
> What we need is a) a way to specify multiple schemas and b) map the 
> namespaces used in that document to the schema in question.
>

What we could provide protocol wise is multiple documents support where 
every document has its schema attached and docs are glued together by a 
view templating mechanism. The templating approach I proposed some 
mails ago takes this into account.

Something like this (introducing file/fileset element within edit):

<edit>
   <fileset>
     <file url="foo.xml">
        <schema url="foo.xsd"/>
     </file>
     <file url="bar.xml">
        <schema url="bar.rng"/>
     </file>
   </fileset>
   <stye url="foobar.xsl">
     <template url="includesFooAndBar.xml"/>
   </style>
</edit>

Styles could also be attached to files within a fileset of course and 
merged by client:

<edit>
   <fileset>
     <file url="foo.xml">
       <schema url="foo.xsd"/>
       <style url="foo.xsl">
         <template url="includesFoo.xml"/>
       </style>
     </file>
     <file url="bar.xml">
       <schema url="bar.rng"/>
       <style url="bar.xsl">
         <template url="includesBar.xml"/>
       </style>
     </file>
   </fileset>
   <stye url="foobar.xsl">
     <template url="includesFooAndBarTemplates.xml"/><!-- if templates 
are provided, otherwise includesFooAndBar -->
   </style>
</edit>

Speaking off the client, source editing would have to be document 
specific (multiple source views + 1 WYSIWYG view) and there are some 
implications regarding file operations (checkin/out of filesets) that 
have to be considered.

All other usecases (including your example) can and should be covered 
by a single schema (mixing xhtml+mathML, xhtml+rdf, ...). I think 
that's what people might want to do most often. Luckily we don't have 
to deal with approaches to combining schemas, because there are som HOT 
debates on the relevant listservs about that for years now. If the 
client supports schema constraints properly it will also support 
namespaces mixing - whatever approach has been taken.

--
Bests
Thomas




> -- 
> Kind regards,
> Andi
>