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


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Are people really using Identity constraints specified in

[ Lists Home | Date Index | Thread Index ]


That functionality is really in the registry interface - and is a designer
support functionality - to return potential candidate content fields - as you
are creating the CAM template in the first place.

If I look at something like OAGi BODs and search in their data dictionary on
'date' 'billing' - I probably get about 10 or 15 hits, and then I need to
decide which one - by looking at the semantics around each - is best suited to
my purpose, etc.

Seems like we are straying now into design-time v run-time.

Ooops - it must be Friday afternoon again!

Thanks, DW.

Quoting "Hunsberger, Peter" <Peter.Hunsberger@STJUDE.ORG>:

> w3c@drrw.info writes:
> > 
> > Here's how VAM works in CAM right now.  We have a simple 
> > precedence sequence.
> > 
> > Again - in order to remain sane - and to allow implementers 
> > of CAM engines and writers of CAM templates - to do stuff 
> > that does not require Teraflops of processing power or 
> > excessive tearing of hair out!
> > 
> > Anyway - the VAM is this - base rules are those in-line rules 
> > embedded into structure members, (or included via an included 
> > structure).  These are overridden by any rules that match the 
> > same XPath target(s) that are declared in the the 
> > <BusinessContext> section of the template.  Third - the 
> > <ContentReference> section provides default rules (typically 
> > retrieved from the central registry, but can be in-lined too) 
> > - that provide rules if neither the structure or context 
> > section provides any.  Last but not least there is the 
> > <DataValidation> section - this is mostly for external calls 
> > to webservices - and so again - anything failing these checks 
> > will be rejected with an appropriate error - this section is 
> > optional though - an intended for backend internal 
> > integration needs against the actual data content - rather 
> > than structural checks.
> I don't really view that as VAM, more like a default fallback mechanism.
> <warning type="weak example"/> 
> The VAM I want would to something like understand that a researcher can
> query on birth date and disease and get back a randomized patient
> identifier, but the same query will fail if it contains a geographic
> identifier since the population of patients (for the given disease) is
> so small that including both restrictions will allow the researcher to
> uniquely identify the patient.
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS