This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Proposal in 4/1/08 f2f: 1- update definition of SML reference in 2.2 Terminology to make it clearer that not all SML references resolve 2- change description of unresolved SML references in 4.1.3 to make it clearer that references must resolve to elements in the same model. 3- make clear that the method of determining what documents are in the model is implementation-defined (or implementation-dependent): you can have an a priori list, you can take the transitive closure of documents referred to by SML references starting from documents known to be in the model, or you can do anything in between. Editors to make this needsReview when completed.
Changes were made in sections 2, 4.1.3, and 4.1.4. See the diff at: http://www.w3.org/2007/10/htmldiff?doc1=http%3A%2F%2Fdev.w3.org%2Fcvsweb%2F%7Echeckout%7E%2F2007%2Fxml%2Fsml%2Fbuild%2Fsml.html%3Frev%3D1.202%26content-type%3Dtext%2Fhtml%3B%2520charset%3Diso-8859-1&doc2=http%3A%2F%2Fdev.w3.org%2Fcvsweb%2F%7Echeckout%7E%2F2007%2Fxml%2Fsml%2Fbuild%2Fsml.html%3Frev%3D1.203%26content-type%3Dtext%2Fhtml%3B%2520charset%3Diso-8859-1
Proposal to change definition of SML Reference as discussed in 4/17 meeting: SML Reference An SML Reference is an element with sml:ref="true". Note: Conceptually, SML references are used to signal a link from one element in an SML model to another element in the same model. ============= Also, edited section 4.1.4 to change 'must' to 'MUST' and move the statement about determining the documents in the model out of the note. It now reads: 4.1.4 SML Reference Target The node set that a non-null SML reference resolves to is its target. The target of an SML reference MUST be part of the same SML model as the SML reference. Null SML references have no target. The method of determining which documents are part of an SML model is implementation-defined. Note: For example, an SML model may consist of documents listed in a configuration file or an SML model could be construed as the transitive closure of documents referred to by any SML references starting from a set of documents known to be in the model.
+1 for the proposal in comment# 2 and for the change diff in comment# 1 (except the def. of a reference).
I'm unsure what "(except the def. of a reference)." means in comment #3. Are you saying further changes are needed, or something else?
Explanation about my comment in comment# 3: The diff in comment# 1 shows the definition of a reference to be: An SML Reference is a link from one element in an SML model to another element in the same model. If the target of the reference cannot be located in the model, the SML reference is considered to be unresolved. This definition does not match the proposed definition in comment# 2. However, the rest of the changes in the diff look good.
Resolution on 5/22 call - fix as per Comment #2
Fixed per comment #2 but with very small editorial changes: New definition of SML Reference: SML Reference An SML Reference is an element with an sml:ref attribute whose value is "true". Note: Conceptually, an SML reference is used to signal a link from one element in an SML model to another element in the same model.