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 4755 - SMLIF section 3.3.6 some fragment URI cases not covered
Summary: SMLIF section 3.3.6 some fragment URI cases not covered
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: 2007-06-24 17:46 UTC by John Arwe
Modified: 2007-11-18 07:16 UTC (History)
0 users

See Also:


Attachments

Description John Arwe 2007-06-24 17:46:23 UTC
context: If the URI representing a resolved inter-document reference has a fragment, the reference is to the element obtained by applying the fragment to the referred-to document starting with its root element.

Since SMLIF does not require that the model being exchanged is a valid SML model, a fragment may resolve to any of the following:
0 elements
1 element
>1 element

Existing text assumes only 1 element is possible.  Need to cover other cases.  Other cases cannot occur if the SMLIF document is also a valid SML model, but 3.2 explicitly says SMLIF does not require the interchange set to form a valid SML model.
Comment 1 Virginia Smith 2007-10-17 17:42:10 UTC
Section is now 3.4.6.
Comment 2 Kumar Pandit 2007-11-13 18:51:08 UTC
Proposal:
Change the text,

from: ...has a fragment, the reference is to the element obtained by ...
to  : ...has a fragment, the reference is to the set of elements obtained by ...
Comment 3 John Arwe 2007-11-15 17:07:57 UTC
fine with me
Comment 4 Virginia Smith 2007-11-15 19:18:09 UTC
Resolution: Removing dependency and accepting proposal as in comment #2.
Comment 5 Kumar Pandit 2007-11-18 07:16:14 UTC
fixed as proposed.