RE: [ubl-dev] SBS and Restricted Data Types

["David RR Webber \(XML\)" <david@drrw.info>]

Chin, 

CAM takes the declarative way out of this empasse.   

Whereas an XSD is describing (as you infer) all possible structural
permutations that you may possibly ever receive - the CAM template
allows you to exactly declare the permutation that matches your
business requirements and specify what the context drivers are. 

One nifty thing about this is - if I have a catalogue of existing CAM
templates for UBL transactions - I can actual search just based on
context parameters in the CAM template headers - to determine if there
is an available template for my needs. 

E.g. assume country_type is a key context factor in an UBL
export_manifest along with shipment_type - and allowed values are
'Perishable, Hazardous, Consumer-Recycle, Goods'.  I could search and
find a match if I'm looking to ship hazardous chemicals to a particular
country, and so on. 

Actually bringing together the work on context that the original CCTS
envisioned was possible... 

DW 

  


  


 -------- Original Message --------
Subject: RE: [ubl-dev] SBS and Restricted Data Types
From: Chin Chee-Kai <cheekai@softml.net>
Date: Wed, May 03, 2006 12:01 pm
To: stephen.green@systml.co.uk
Cc: UBL-Dev <ubl-dev@lists.oasis-open.org>

>>2. a way to say (and maybe
>>validate/verify) that a schema is a strict subset of another schema
>>of which it therefore uses the same namespace. Too late for XSD 1.1?

Stephen,

That's an interesting question to ask, or re-phrasing it,
"is there a way to determine if the entire set of all possible
instances that are validated as acceptable by a given schema (A)
are also validated as acceptable by another given schema (B)" ?

Call this "sub-of" operator operating on 2 parameters (A) & (B)
each of type schema.

But I suspect as long as a schema can metamorph into another
form during runtime through redefine, phrasing the question
itself might need to involve the notion of *when*.  In other words,
it may be necessary to cope with the idea of (A) being "sometimes"
sub-of (B) and "sometimes" not...

This "sub-of" operator, taking inputs which are schema themselves,
would likely be outside of the realm in which XSD specifies.
But of course, whatever XSD does (or doesn't) specify would 
affect the realisability of this "sub-of" operator that you suggested.




Chin Chee-Kai
SoftML
Tel: +65-6820-2979
Fax: +65-6820-2979
Email: cheekai@SoftML.Net
http://SoftML.Net/




---------------------------------------------------------------------
This publicly archived list supports open discussion on implementing the
UBL OASIS Standard. To minimize spam in the
archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Alternately, using email: list-[un]subscribe@lists.oasis-open.org
List archives: http://lists.oasis-open.org/archives/ubl-dev/
Committee homepage: http://www.oasis-open.org/committees/ubl/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Join OASIS: http://www.oasis-open.org/join/