W3C home > Mailing lists > Public > public-sml@w3.org > February 2008

[Bug 5406] Use "model validator" term consistently; drop "conforming"

From: <bugzilla@wiggum.w3.org>
Date: Thu, 21 Feb 2008 20:12:05 +0000
CC:
To: public-sml@w3.org
Message-Id: <E1JSHm1-00040L-9L@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5406





------- Comment #15 from kumarp@microsoft.com  2008-02-21 20:12 -------
sandy's proposal:
-----------------

4.2.6 deref() XPath Extension Function 
Model validators MUST provide an implementation of the deref() XPath extension
function. This function takes a node set of elements and returns a node set
consisting of element nodes  
 
Note: 
This note is non-normative. This section The above describes the behavior
required for a general XPath 1.0 deref() library function,  
Model validators MUST provide an implementation of the deref() XPath extension
function. In addition to the above requirements for general deref() function
implementations, for each SML reference with recognized schemes, deref() in
model validators MUST attempt to resolve at least one of the recognized
schemes. 
So basically: 
1. Do not talk about model validators or SML processors. As the note suggests,
the first half of this section is about a general XPath extension function,
instead of an SML processor/validator.
2. Add a paragraph about deref() used by model validators. 
3. Additionally require that at least 1 recognized scheme needs to be checked,
to ensure consistent result within the validator. (Without this constraint, one
part of the validator, e.g. targetRequired, would think a reference is
resolved, while other parts, e.g. identity constraints, would treat the
reference as unresolved, if no scheme is attempted by the deref() function.) 

I hope the meaning of the #3 should be clear, but can be improved English-wise. 

Does this sound like the right direction? 


Kumar's small addition:
-----------------------
Add the following as a sub-section to section 4.2 SML Reference Semantics:
---
4.2.x Deterministic evaluation of SML constraints
Each non-null SML reference MUST satisfy all of the following conditions in
order to be able to deterministically evaluate SML constraints and rules
associated with it.
1.      At most one target
2.      Consistent references
---

Appropriate parts of text above will be links to the relevant sections.
Received on Thursday, 21 February 2008 20:12:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:56:09 UTC