Using appinfo annotations to store integrity constraints

• From: Vun Kannon, David <dvunkannon@kpmg.com>
• Date: Mon, 1 May 2000 16:28:00 -0400
• To: "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
• Message-Id: <1BFA1EA02439D21193A20008C7A4B20F04F65787@USMNYEXC04>

	I am considering, as the subject line says, using appinfo
annotations to store integrity constraints. Consider a document as the
transfer syntax for a database predicate. An integrity constraint might be
"no worker earns more than their supervisor" or "pay_rate > 0". These
integrity constraints could be expressed as CHECK constraints in SQL, for
instance.
	I was considering trying to achieve the same effect with XSL-T
templates in appinfo elements. Unfortunately, it appears that even in the
April 7 draft, annotation and appinfo are poorly documented. Annotation is
used but not defined in either the schema for schemas or DTD, and appinfo
(and documentation) similarly. What is the content model ()+ supposed to
mean, in sec 4.3.10?
	Your comments appreciated on the appropriateness of the idea, and my
understanding of appinfo.
Thanks,
David vun Kannon
Manager, Financial Services Consulting
KPMG Consulting LLP
*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 
If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         
*****************************************************************************

Received on Monday, 1 May 2000 16:28:34 UTC