RE: [Bug 4638] Conformance section needed

I agree with Sandy's suggestion. I'll make the change.

________________________________

From: public-sml-request@w3.org [mailto:public-sml-request@w3.org] On Behalf Of Pratul Dublish
Sent: Thursday, September 06, 2007 8:29 AM
To: Sandy Gao; public-sml@w3.org
Subject: RE: [Bug 4638] Conformance section needed



Agree with Sandy and Kirk 

 

From: public-sml-request@w3.org [mailto:public-sml-request@w3.org] On Behalf Of Sandy Gao
Sent: Thursday, September 06, 2007 7:03 AM
To: public-sml@w3.org
Subject: RE: [Bug 4638] Conformance section needed

 


+1 to Kirk's comment. 

Maybe it'll be even better to treat acyclic in the same way as target*. e.g. 

    *      Each document in the model MUST satisfy all applicable Schematron constraints
   *      Each document in the model MUST satisfy all applicable sml:acyclic and sml:target* constraints

We don't have to repeat "no cycle" here. That rule is already specified elsewhere in the spec. 

Thanks,
Sandy Gao
XML Technologies, IBM Canada
Editor, W3C XML Schema WG <http://www.w3.org/XML/Schema/> 
Member, W3C SML WG <http://www.w3.org/XML/SML/> 
(1-905) 413-3255 T/L 969-3255




"Wilson, Kirk D" <Kirk.Wilson@ca.com> 
Sent by: public-sml-request@w3.org 

2007-09-06 06:27 AM 

To

<bugzilla@wiggum.w3.org>, <public-sml@w3.org> 

cc

	
Subject

RE: [Bug 4638] Conformance section needed

 

		





Now that we have dropped sml:refType, is "reference type" (see last bullet, last phrase) a well-defined term in the spec?  I would think we need to give an explicit definition of what we intend to cover with this term or, simpler, just drop the word "type" from the phrase.

Kirk Wilson, Ph.D.
Research Staff Member
CA Labs
603 823-7146

-----Original Message-----
From: public-sml-request@w3.org [mailto:public-sml-request@w3.org] On Behalf Of bugzilla@wiggum.w3.org
Sent: Thursday, September 06, 2007 5:56 AM
To: public-sml@w3.org
Subject: [Bug 4638] Conformance section needed


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


virginia.smith@hp.com changed:

          What    |Removed                     |Added
----------------------------------------------------------------------------
        AssignedTo|cmsmcq@w3.org               |virginia.smith@hp.com
          Keywords|editorial                   |needsReview




------- Comment #3 from virginia.smith@hp.com  2007-09-06 09:55 -------
In the SML spec, changed the "Model Validation" section to "Conformance
Criteria" as follows:

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

   *      The validator MUST perform model validation as defined in this
specification. Model validation is the process of examining each document in a
model and verifying that this document is valid with respect to the model
definition documents, i.e., each model instance document satisfies the schemas
and rules defined in the applicable model definition documents.
   *      The validator MUST support XML Schema 1.0 and XPath 1.0 but MAY also
support any future versions of these specifications.
   *      The validator MUST perform Schematron rule evaluation on the #ALL
phase, implying that every rule in every pattern is evaluated.

A set of XML documents is a conforming SML model if it satisfies the following
conditions:

   *      Each document in the model MUST be a well-formed XML document [XML
1.0]
   *      Each XML Schema document in the model's definition documents MUST
satisfy the conditions expressed in Errors in Schema Construction and Structure
(§5.1). [XML Schema Structures]
   *      Each Schematron document in the model's definition documents MUST be
a valid Schematron document [ISO/IEC 19757-3]
   *      In each instance document in the model, the [validity] property of
the root element and all of its attributes and descendants MUST NOT be
"invalid" when schema validity is assessed by a conforming schema-aware
processor with respect to the referenced XML Schema documents in the model's
definition documents. [XML Schema Structures]
   *      Each document in the model MUST satisfy all applicable sml:target*
and Schematron constraints
   *      The model MUST NOT contain a cycle whose edges are references of
type R if R is an acyclic reference type