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 5656 - Defining interoperability for user-defined reference schemes
Summary: Defining interoperability for user-defined reference schemes
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Interchange Format (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: CR
Assignee: Kumar Pandit
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-22 20:07 UTC by Kirk Wilson
Modified: 2008-08-14 01:33 UTC (History)
2 users (show)

See Also:


Attachments

Description Kirk Wilson 2008-04-22 20:07:56 UTC
SML defines three conditions for defining reference schemes (section 4.5).  These conditions constitute an extension mechanism for defining user-defined reference schemes.  SML itself uses these conditions to define the SML URI Reference Scheme. SML-IF adds substantially to the definition of the SMI URI Reference Scheme in section 5.3.4 regarding how SML URI reference scheme instance are processed in SML-IF documents.  However, it is never discussed how user-defined reference scheme are supported, or what needs to be done to support these schemes, in SML-IF.  The text merely states, "Resolution of URI references in category #3 is defined in their respective scheme definitions."  but nowhere is explicitly stated as a requirement of user-defined reference schemes.

In particular, SML-IF needs to recognize that to address the interoperability of user-defined references there needs to be discussions of:
1.  An algorithm for generating URI aliases from the instances of the reference scheme so that targeted documents can be identified within the SML-IF document.
2. The need to define the process by which a user-defined reference schema instance is resolved in terms of the target document in SML-IF (i.e., there needs to be explicit recognition of the fact that a user-defined reference scheme that aims for interoperability must spell out something like what section 5.3.4 does for the SML URI reference scheme.

(These issues have emerged with the writing of the "EPR Note"--I wish these issues would have been more explicitly spelled out in SML-IF.)
Comment 1 Kumar Pandit 2008-05-01 19:01:04 UTC
resolution in conf call (5/1/08): mark needsAgreement
Comment 2 John Arwe 2008-06-24 10:06:34 UTC
f2f consensus to add the following text

SMLIF 4.5 item 4

The SML-IF document may use references schemes that do not use target-complete identifiers.  In addition to the requirements imposed by SML on reference scheme definitions, SML-IF imposes additional requirements on references schemes that do not use target-complete identifiers in order to make them useful in the context of SML-IF [5.3.4 discussion of category 3].

SMLIF 5.3.4 end, after category 1 & 2 URI processing

To process a URI reference UR that is within category #3 above, a set of steps corresponding to those described above for categories #1 and #2 MUST be defined as part of the reference scheme definition.

...and to fix the following typo
SMLIF 5.3.4 2.b
from: Otherwise ( R is within category #2, 
to  : Otherwise (UR is within category #2, 
Comment 3 Kumar Pandit 2008-07-03 01:25:37 UTC
fixed per comment# 2
Comment 4 John Arwe 2008-07-03 15:44:43 UTC
comment 2 had 2 places where the English was mangled, and it made it into the draft.  we need to tweak them.

from: "references schemes" 
to  : "reference  schemes"
Comment 5 Kumar Pandit 2008-08-14 01:33:09 UTC
fixed per comment# 4.