[dsdl-discuss] Re: FW: [office-comment] Ambiguity problems caused bya:defaultValue

I think that a simple (probably streamable) integrity constraint
language would work. Part 6 is supposed to do this.

I think that we only need a very tiny language for identity constraints.

1) It should be simple. Something similar to key/keyref would be good
   enough.
2) It should be streamable.
3) Checking of identity constraints shall be separated from RELAX NG
   validation.
4) Given descriptions in this language, it should be easy for
    application programmers to create programs for maintaining
    hashtables.
5) It would be nice if descriptions in this language can be embedded
    within RELAX NG schemas.

We can spend a lot of time if we forget 1). Researchers do that, but
DSDLers shouldn't.

Can Part 6 meet these goals?

Cheers,

-- 
MURATA Makoto <murata@hokkaido.email.ne.jp>
--
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)