MURATA Makoto said:
>> But does it really mean that if I have three schemas in different
>> namespaces, A B and C, and schema A includes both schema B and C, and
>> schema B and C happen to have patterns with the same name, that it is an
>> error?
>
> Is <externalRef> good enough for your example?
I may have to organize things to use it, but that requires adding
knowledge about whether the XML schema is called by others or not, which
is back to front.
> Or, you might want to introduce two <grammar> elements within the
> top-level <grammar>. The first sub-<grammar> includes B, while
> the second sub-<grammar> includes C.
But I thought Eric said there is a flat namespace with no scoping in RELAX
NG. What difference does the grammar element make? My question still
stands: is it an error to have patterns with the same name in the case
above?
Unfortunately, I am getting more confused about this, not less. Especially
when I see material on parentRef, I cannot figure out what it all means. I
feel like the material on RELAX NG has been written making some key
assumption about something that I am not privy to...
Is there any other good summary around?
> You mentioned the combine attribute. I have always thought that
> the combine attribute is useful only when different define elements
> having the same name belong to different schema files. So, I am
> very surprised at the ODF RELAX NG schema (a single-file schema
> which heavily uses the combine attribute) and your suggestion
> about the combine attribute. How do others feel?
I am open for any suggestion. I guess I currently have three issues that I
cannot find satisfactory answers for in the material online:
1) When dealing with multi-namespace documents with multiple schema
documents, what should I use NVRL for and what should I use RELAX NG for?
I am asking both about absolute capabilities and best practise.
2) What is the scoping and visibility of pattern names in RELAX NG? What
does ExternalRef do? When do name duplications cause errors?
3) In the particular case of converting an XSD element that joins a
substitution group whose head and type is in another namespace (and there
for in another schema), what is the equivalent RELAX NG constructs? Does
the presence of these mean I cannot use NVRL to validate the branches
separately? (Also, I am working on the constraint that the RELAX NG
schema must follow as closely as possible the order and structure of the
XML Schemas: so even though I do have to copy or move sections out to
allow them to be defined and named, I need to keep this to a minimum.)
Cheers
Rick
-- DSDL members discussion list To unsubscribe, please send a message with the command "unsubscribe" to dsdl-discuss-request@dsdl.org (mailto:dsdl-discuss-request@dsdl.org?Subject=unsubscribe)Received on Thu Aug 17 16:34:14 2006
This archive was generated by hypermail 2.1.8 : Thu Aug 17 2006 - 22:33:02 UTC