RE: [xml-dev] 2 questions about Relax NG: ID/IDREF datatype and whitesp

[Len Bullard <len.bullard@uai.com>]

Dave also sent me that.  To do otherwise would have been to give DTDs a
longer lifespan.  It confirms comments made on this list along the way about
the necessity of creating minimal standards and really, minimal systems.

KISSGodzRule:  Any feature acquires a use case somewhere and becomes almost
impossible to remove post hoc.

As I sit here planning a 'features complete' release of a CAP-conforming
health alerting system, I marvel at the truth of that.

Here's something for you to ponder:  what percentage of a database entity
design (and consequently, supporting forms, business classes etc) should
support domain-lookups (eg, metadata) vs operational data (ie, business
data)?  It's not a trick question but the answer affects product planning
and standards planning.

len


From: Costello, Roger L. [mailto:costello@mitre.org] 

So I conclude that, unless otherwise specified, a Relax NG validator
will treat ID and IDREF values the same way that XML treats them, i.e.
an IDREF value must reference an ID value.

/Roger

[1] http://www.thaiopensource.com/relaxng/jing.html

-----Original Message-----
From: Len Bullard [mailto:len.bullard@uai.com] 

The technical clarification will be interesting to read, but
marketwise, given that ID/IDREF checking has been provided since ISO 8879
SGML, not validating that in a *validator* would be surprising even if not
in the lexical parse.  

Assert:  a tool can only be abstracted so far before it loses cohesion
With the original application and user base.  Don't shock the monkey.

len


From: Costello, Roger L. [mailto:costello@mitre.org] 
 
Hi Folks,

I am reading the "Guidelines for using W3C XML Schema Datatypes with
RELAX NG"[1], and am confused about a couple of things.

QUESTION #1

This paragraph in the Guidelines discusses the ID, IDREF datatypes:

The semantics defined by [W3C XML Schema Datatypes] for the ID, IDREF
and IDREFS datatypes are purely lexical and do not include the
cross-reference semantics of the corresponding [XML 1.0] datatypes. The
cross-reference semantics of these datatypes in XML Schema comes from
XML Schema Part 1. Furthermore, the [XML 1.0] cross-reference semantics
of these datatypes do not fit into the RELAX NG model of what a
datatype is. Therefore, RELAX NG validation will only validate the
lexical aspects of these datatypes as defined in [W3C XML Schema
Datatypes].

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender. This message contains confidential information and is
intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail.

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.