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 5382 - Clarifying intention of section 4.4
Summary: Clarifying intention of section 4.4
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Interchange Format (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: LC
Assignee: Kumar Pandit
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-16 18:25 UTC by Kirk Wilson
Modified: 2008-06-05 19:08 UTC (History)
1 user (show)

See Also:


Attachments

Description Kirk Wilson 2008-01-16 18:25:49 UTC
In section 4.4, the statement is made (after the first set of numbered items) about "This proposal...".  THIS (specification) is no longer a proposal.  (I suspect that this some left-over text from this section was a proposal.)

Also, this statement states that the "proposal" pertains SML model validation, not SML-IF validation.  This statement is confusing to the reader.  If the "proposal" pertains to SML model validation, why is it in the Interchange specification.

This statement needs to be clarified.
Comment 1 Sandy Gao 2008-01-16 20:25:14 UTC
Agree that "this proposal" needs to be fixed.

For an SML-IF document, there are 2 kinds of validation that can be performed. One is to check whether it is a valid IF document, by validating it against the IF schema. This only checks the structure of the document (e.g. <instances> contains <document>s).

The other kind of validation is to check whether the model being packaged in this IF document is valid, by performing "SML model validation" (e.g. check SML references, Schematron rules).

To ensure inter-op, the IF spec needs to provide enough constraints to ensure that the second kind of (model) validation always produces the same result for the same IF document.

This explains why "schema binding", though an IF mechanism, is specifically for SML model validation.

That said, if the quoted sentence (after fixing "this proposal") confused one WG member, then it may confuse other readers too. Some word-smithing may be required. Not my expertise (and it was me who produced this confusing sentence).
Comment 2 Kumar Pandit 2008-01-18 09:29:42 UTC
The sentence "This proposal..." was odd given the surrounding context. The following change was made to fix this.

From:
So it is clear that SML-IF cannot guarantee general case interoperability based only on XML Schema given the constraints above and, therefore, needs to specify how to determine such associations. This proposal concerns only SML model validation and not SML-IF validation (against the IF schema). Unless otherwise indicated, "validation" or "validity" in the following sections refers to SML model validation. 

To:
So it is clear that SML-IF cannot guarantee general case interoperability 
based only on XML Schema given the constraints above and, therefore, needs to 
specify how to determine such associations. This section describes a method to achieve this goal.