Lists Home |
Date Index |
Both Michael and Len are stating that in a system there should be numerous
schemas. This is a big mindshift for me. I admit being trapped into
thinking that there should be a single schema.
It would be very useful if we could have a simple example that shows how
several schemas might be employed, rather than a single schema. Could
someone provide an example?
Quoting "Roger L. Costello" <email@example.com>:
I can happily point you at several examples. In the CAM tutorial there is the
Soccer Catalogue order example - where the schema has three derivatives -
depending on your addressing locale.
That's a trivial case however - and CAM actually supports iteration of
<structure> so you can have one or more structures.
An example of this is for BT itself. They use XML for trouble ticket reporting
from switch devices in the field. These devices produce 'flavours' of the base
XML. Therefore the CAM template for this consists of a master template - that
uses <as:include> to haul in the actual schema structure based on a context
switch statement of the actual equipment involved.
There are more examples too. Thinking of purchase order processing - I may have
two setups - where two different companies are using different versions and
configurations of schema - this happens alot - especially with things like OAGi
BODs - so one comapny may be on version 7 the other on version 8. Mostly the
tagnames are the same - but the structures are very different. The one CAM
template would have both structures in - and then select accordingly.
We're using the feature of CAM in ebXML BPSS particularly - where the BPSS step
points to a logical document "Send Purchase Order" and then the CAM template
resolves that to the actual physical PO format - depending on the receipient.
Hope that sets the right scenes here for you.