[Bug 5740] Inconsistent requirements for using PSVI after 5541 adopted

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


John Arwe <johnarwe@us.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |hasProposal




--- Comment #1 from John Arwe <johnarwe@us.ibm.com>  2008-06-18 17:04:00 ---
The editor's draft of SML 4.1.1, after
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5541 , reads as follows:

4.1.1 SML Reference

An element information item in an SML model instance document is as an SML
reference if and only if it has an attribute information item for which all of
the following is true:
   1.      Its [local name] is ref
   2.      Its [namespace name] is http://www.w3.org/@@@@/@@/sml
   3.      Its [normalized value], after whitespace normalization using
collapse following schema rules, is either "true" or "1".

Note:
   1.      This mechanism enables schema-less identification of SML references,
i.e., SML references can be identified without relying on the Post Schema
Validation Infoset (PSVI). [XML Schema Structures]
   2.      SML model validators must use PSVI to identify SML references. See
8. Conformance Criteria.

An SML reference is considered to be an instance of a specific SML reference
scheme, if it can be identified as such according to that SML reference
scheme's rules. See 4.3 SML Reference Schemes. An SML reference MAY be an
instance of multiple SML reference schemes.

Although its normative definition allows several syntaxes to be used to
identify an SML reference, for the sake of brevity and consistency, the rest of
this specification uses sml:ref="true" to denote an SML reference in examples
and text.

------------------ end of excerpt ----------------
Areas for improvement
- Note 2 is redundant with section 8 (which states the same condition
normatively)
- Note 2 has nothing to do with the rest of the definition of an SML reference.
- The original bug, namely the loss of the impl-defined reqt on (non-validator)
model processors.

============================================
Alternative Proposal 1: all of the following (1a-1b)
1a Just make notes 1 and 2 consistent (neither has to do w/ the def of sml ref,
and talk about both classes of processor), and forget about the "interruption"
in the def of an sml ref.

from: SML references can be identified
to  : model processors can identify SML references

Note:
   1.      This mechanism enables schema-less identification of SML references,
i.e., model processors can identify SML references without relying on the Post
Schema Validation Infoset (PSVI). [XML Schema Structures]
   2.      SML model validators must use PSVI to identify SML references. See
8. Conformance Criteria.

1b Update the conformance section to levy the impl-defined reqt.
Current text starts:
8. Conformance Criteria
A program is a conforming SML model validator if and only if it satisfies the
following conditions:

Update to read (#1 text taken from section 2's definition):
8. Conformance Criteria
A program is a conforming SML model processor if and only if it satisfies the
following conditions:
1. The processor MUST process a conforming SML model using, in whole or in
part, semantics defined by this specification.
2. If the processor identifies SML references as part of its processing, it is
implementation-defined whether to use the XML Infoset [XML Information 
Set] or the Post Schema Validation Infoset (PSVI) [XML Schema Structures] for 
SML reference identification.

A program is a conforming SML model validator if and only if it satisfies the
following conditions:


============================================
Alternative Proposal 2: all of the following (2a)
2a: Append to the current definition of 'model processor' a new sentence: 
It is implementation-defined whether to use the XML Infoset [XML Information 
Set] or the Post Schema Validation Infoset (PSVI) [XML Schema Structures] for 
SML reference identification.

Since the definition is normative, this could be deemed sufficient.

============================================
Alternative Proposal 3: all of the following (3a)
3a: proposal 2a (levy the impl-defined reqt in the definition)
3b: remove 4.1.1 note 2 (remove the redundant reqt on validators, and remove
the inconsistency of the note mentioning only one class of processor)


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 18 June 2008 17:04:35 UTC