[dsdl-discuss] Re: Potential use cases for complex value validation from ebXML

 
From: "Martin Bryan" <mtbryan@sgml.u-net.com>

> What about if we do it another way: what if we make it necessary for
> permitted datatype values to be declared locally but provide a mechanism
> that allows the values themselves to be validated at some separate point in
> the lifecycle, e.g.
>
> <validEntries>
> <permittedValue source="http...." date="...." value="KOR KO">KO</value>
> ....
> </validEntries>

Can you explain more? Do you mean that we have two classses:
  1) the (subset of interest of) the controlled vocabulary at the time of
    document created or schema creation and
  2) the current value of the controlled vocabulary.

So these validate
  1) Is this document consistent with the world of the schema creator?
  2) Is this document still consistent?

That is an interesting approach.

> Haven't had any feedback yet on the idea of using a really minimalist string
> matching approach rather than formally defining sets of datatypes. Is this a
> total non-starter?

We certainly need string matching using regex somewhere. I see RELAX NG
has had discussion on adding REGEX into it, and that might be best.

So now we are thinking about:
 1) matching token against regex
 2) matching token against local list of permitted values and
       (probably at some other time) against an external list
 3) doing some kind of integrity check, treating the enumeration as a link or
    key

Is that right?

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)