OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Treasury Tag Pattern: to 'glue' two instances having different schemas

Regarding the issue of how to bring together a document and data from 
another schema (thanks to Duane for the suggestion along the lines below):

I guess what we need is the XML equivalent of a 'treasury tag'.
This treasury tag is then a 'pattern' (in the software design sense) 
rather than a specific schema.

It goes something like this:

Treasury Tag Pattern 

Requirement: a way to clip together two or more XML documents
so that these can be treated as a single file. 

A schema is created with a document top level element. The top level 
element can have any name but a suggestion is 'StandardDocument'.
This acts as a container element to one or more elements which 
are the document top level elements of the XML files to be contained.
The schema imports the schemas of the contained XML files.

There is no need to use xsd:any and all data may be associated
with namespaces
This has the following benefits and liabilities -
benefits - data is more easily recognised as being appropriate
liabilities - a schema has to be created for each set of documents
There is also the benefit that the set of documents may be validated
as one.
For storage it may be preferable to remove the containing element
so that each document is stored separately with its own namespace
and types.

All the best

Stephen Green

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]