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 5390 - How to handle non-embedded documents referenced by EPRs in SML-IF
Summary: How to handle non-embedded documents referenced by EPRs in SML-IF
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: EPR Reference Scheme (show other bugs)
Version: PR
Hardware: PC Windows XP
: P2 normal
Target Milestone: CR
Assignee: Kirk Wilson
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2008-01-17 21:48 UTC by Kirk Wilson
Modified: 2009-01-08 20:01 UTC (History)
1 user (show)

See Also:


Attachments

Description Kirk Wilson 2008-01-17 21:48:19 UTC
Documents referenced through EPR reference schemes may not be embedded in SML-IF documents because of their potential dynamic character.  The issue is how to handle documents that are not embedded in the SML-IF document.  Specifically, should a value of a <locator> element be used and how?  The issues need to be discussed in the EPR Note.
Comment 1 John Arwe 2008-01-18 15:54:20 UTC
see also http://www.w3.org/Bugs/Public/show_bug.cgi?id=5383, which this bug was split off from, for some discussion that may be relevant.
Comment 2 Pratul Dublish 2008-04-02 18:38:56 UTC
Decided in F2F on 4/2 

RESOLUTION: Change conformance criteria from
"A set of XML documents is a conforming SML model if ..."

to read "A model is a conforming SML model ..."
Comment 3 Pratul Dublish 2008-04-02 18:40:22 UTC
Ignore Comment #2 - it was for a different bug
Comment 4 Kumar Pandit 2008-05-01 19:16:24 UTC
resolution in conf call (5/1/08): mark needsAgreement
Comment 5 C. M. Sperberg-McQueen 2009-01-08 20:01:24 UTC
We discussed this issue during the call of 8 January 2009.

Kirk Wilson suggested that the EPR Note should simply say that if
EPR references are used in locators for non-embedded documents in an
SML-IF package, then the same issues arise as when EPRs are used as a
reference scheme -- that is to say, it's complicated and error prone,
and those who do it need to make sure they know what they're doing.

KW noted that the draft text of the EPR Note already says this.

Those on the call agreed that this proposal suffices as a resolution
of the issue, and that the bug should be marked as FIXED.