This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5395 - Normative discussion of schemaComplete
Summary: Normative discussion of schemaComplete
Alias: None
Product: SML
Classification: Unclassified
Component: Interchange Format (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: LC
Assignee: Valentina Popescu
QA Contact: SML Working Group discussion list
Keywords: resolved
Depends on: 5406
  Show dependency treegraph
Reported: 2008-01-18 16:50 UTC by Kirk Wilson
Modified: 2008-02-14 20:26 UTC (History)
0 users

See Also:

diff document, doc format (165.50 KB, application/octet-stream)
2008-01-29 04:29 UTC, Valentina Popescu
diff doc, htm format (139.42 KB, text/html)
2008-01-29 04:30 UTC, Valentina Popescu

Description Kirk Wilson 2008-01-18 16:50:14 UTC
The decision regarding schemaComplete stipulated that it is to be a required attribute of <definitions>: see  However, the current discussion of schemaComplete occurs only in section 4 of the specification, which is a non-normative section.  A statement to the effect that "it is necessary" for SML-IF document to distinguish between schema completeness and incompleteness is therefore confusing, since it should not be interpreted as a normative statement.  The current text does not adequately implement the decision in 4774.

Suggestion: Include a normative discussion of schemaComplete as a subsection of 5.1. (See also issue 5306.)
Comment 1 Kirk Wilson 2008-01-21 13:31:16 UTC
Additional comment:  The schema for SML-IF does not show schemaComplete as a required attribute.  Given the decision, it probably should be required.
Comment 2 Virginia Smith 2008-01-21 22:25:18 UTC
Resolution: add a new section (in 5.2) that provides a normative definition of schema complete and normative statement about the schemaComplete attribute (see text in 4.4 for sample).

Use new definition for schemaComplete:  When schemaComplete is 'true' - a conforming consumer performing SML-IF model validation of the interchange set MUST NOT retrieve any schema components from outside the interchange set.

Introduce a new term, e.g. SML-IF model validation, for the operation "a consumer performing model validation of the interchange set"
Comment 3 C. M. Sperberg-McQueen 2008-01-22 13:27:15 UTC
Some sample wording illustrating some of the points I was trying to make in
yesterday's meeting is at

The covering email is at
Comment 4 Pratul Dublish 2008-01-23 14:44:11 UTC
The term "SML-IF model validation" is misleading and confusing. SML model validatio is already defined in the SML spec, and there is no such thing as an SML-IF model. An SML-IF document is just an XML doc that contains an SML model. We need a term that covers the additional requirements on an SML-IF consumer who wants to validate the SML model contained in an SML-IF document.  
Comment 5 Virginia Smith 2008-01-23 15:35:28 UTC
Resolution on Jan 23 f2f:

Proposal B with Alternative 1 plus careful editorial attention to remove behavioral statements (see Bug #5406). 
Comment 6 Valentina Popescu 2008-01-29 04:28:44 UTC
fixed as described in the attached documents
Comment 7 Valentina Popescu 2008-01-29 04:29:30 UTC
Created attachment 510 [details]
diff document, doc format
Comment 8 Valentina Popescu 2008-01-29 04:30:04 UTC
Created attachment 511 [details]
diff doc, htm format
Comment 9 Virginia Smith 2008-01-29 21:50:58 UTC
I suggest the following changes:

In section 2.2, change definition to:

Interchange set validation is the process of assessing the validity of the SML model [SML 1.1] represented by the interchange set while maintaining all assertions and interrelationships among the documents in the interchange set as defined by this specification.

In section 4, change last paragraph to: 

Getting consistent model validation results: The process of SML model validation defined in [SML 1.1] contains points of variability that, left unconstrained, would make it difficult for SML-IF to ensure interoperability of independent implementations in any practical way.  Many of these sources of variability are inherited from other specifications that SML uses, e.g. URI comparison [RFC 3986] and the source of Schema components [XML Schema 1.0] used to validate model instance documents.  SML-IF constrains these points of variability with the goal of ensuring interoperability when specific conditions are met and increasing the likelihood of interoperability in other cases. 

In section 4.1, change inserted paragraph to:

The schemaComplete attribute is defined on the definitions element and is used to indicate that the schemas constructed from the definition documents in the interchange set are complete, in the sense that the validity of the SML model represented by the interchange set is fully determined by these schemas. Formally, however, the schemaComplete attribute does not express any assertion that the schemas so constructed are, in fact, complete, or that validation using these schemas will not result in any errors. The only formal effect of schemaComplete attribute with a value of true or 1 is to specify precisely the schemas with which interchange set validation is to be performed.

In section 5.1, remove sentence "A conforming SML-IF Validator..." I don't think this is necessary and should be covered by the conforming consumer criteria (and the SML spec).

In section 5.1, move sentence "In particular..." to the end of the previous paragraph.

In section 5.2, change 4th paragraph to one sentence (note that 'definition' and 'instance' are now singular):
The definition and instance documents packaged by an SML-IF document MAY form a valid SML model but it is not required to do so. 

In section 5.2.3, replace section text with the following and *also insert link to the definition of interchange set validation:

The smlif:schemaComplete attribute is defined on the definitions element. The attribute indicates whether or not all the definition documents required for interchange set validation are included in the interchange set. If schemaComplete has the value true or 1, then schemas used for interchange set validation MUST contain only schema components declared in definition documents (and built-in components) within the interchange set. If schemaComplete has the value false or 0, then this specification does not constrain whether or not definition documents required for interchange set validation are retrieved from outside the interchange set.
Comment 10 Valentina Popescu 2008-02-01 21:45:22 UTC
re comment #9

Most of the comments are editorial updates and I addressed them with some changes:

Section 4, last paragraph still contains as a last sentence:
The enforcement of these additional constraints on SML model validation occurs during the process of interchange set validation.

Section 5.2.3 reads
If schemaComplete has the value true or 1, then schemas used for interchange set validation of the interchange set MUST contain only schema components declared in built-in components or in model definition documents within the interchange set.
Comment 11 Kumar Pandit 2008-02-13 07:31:43 UTC
+1 for the changes.