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 5790 - reduce the "all bets are off" consequence of unreachable documents
Summary: reduce the "all bets are off" consequence of unreachable documents
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Kumar Pandit
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-24 11:09 UTC by John Arwe
Modified: 2008-07-03 16:02 UTC (History)
2 users (show)

See Also:


Attachments

Description John Arwe 2008-06-24 11:09:57 UTC
f2f consensus:

Need to narrow the license given in the sentence 2 below so that it's not "all bets are off" once a single document is unreachable.

Conformance and validity of a model can be assessed if and only if all documents in the model are available to the model validator. If any model document is not reachable, then the model validator's behavior is implementation-defined.
Comment 1 John Arwe 2008-06-24 17:25:27 UTC
This paragraph occurs in SML section 8 Conformance Criteria

--- Existing text, editor's draft
Conformance and validity of a model can be assessed if and only if all
documents in the model are available to the model validator. If any model
document is not reachable, then the model validator's behavior is
implementation-defined.
----

Proposed replacement text: 

The conformance of a model and the validity of a model can be assessed if and only if all documents in the model are available to the model validator.  A model validator MUST document its behavior (i.e. it is implementation-defined) when a model document is found to be unavailable.  It MAY respond to this condition in ways that include but are not limited to: assessing the model as invalid, or treating this as a warning.  The intent of the latitude granted to model validators in this case is to provide some implementation flexibility by not prescribing a limited set of choices, however it should be read narrowly rather than as a broad license to take unrelated actions like failing to enforce SML constraints on unrelated documents.
Comment 2 John Arwe 2008-06-25 08:32:06 UTC
f2f consensus to fix as in comment #1.

Some editorial suggestions:
- tweak comma placement
- move (impl-defined) parenthetical to end of sentence
- change "should be read" to "to be read" or similar... want the sense of must, without using rfc2219 keywords like must or should.
Comment 3 Kumar Pandit 2008-07-03 02:11:42 UTC
fixed per comment# 1 and comment# 2.
Comment 4 Kirk Wilson 2008-07-03 16:02:08 UTC
One further tweak to the final text, in addition to those in Comment #2:

Final sentences:

From: actions like    failing to enforce
TO:   actions such as failing to enfore

Despite some common (ubiquitous) uses of "like", I still hold to the old grammar rules: "like" should refer to a single object, "as" is used with complex clauses.