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 4637 - What should we do with EPR scheme?
Summary: What should we do with EPR scheme?
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: LC
Assignee: Kumar Pandit
QA Contact: SML Working Group discussion list
Depends on:
Blocks: 5106
  Show dependency treegraph
Reported: 2007-06-12 22:51 UTC by Philippe Le Hegaret
Modified: 2007-12-07 06:47 UTC (History)
0 users

See Also:


Description Philippe Le Hegaret 2007-06-12 22:51:56 UTC
At the minimum, the example needs to be modified since it is using reference parameters to identify resources, which is contrary to the Web Services Addressing 1.0 recommendation.

Should we be specific on how to dereference the EPR? How are we going to do interop testing on this part?
Comment 1 Kirk Wilson 2007-09-12 12:49:40 UTC
Valentina has submitted a use case for the "EPR scheme":

However, Kirk argued that the issue that the use case brings up is the transport of a reference to a service that maintains XML documents:  It was also argued that embedded a referent in the wsa:ReferenceParameters may not be the best approach to addressing this issue.

Whether we should address this issue in the specification and how we should address it requires agreement of the group.  I would support discussing the approach to transporting references in the spec as a way to define interoperability between model builders and the data center services that maintain model documents.
Comment 2 Kirk Wilson 2007-11-14 14:27:54 UTC
Initial draft of a proposal.  Basically, this version lays out the arguments for a new direction of a solution.
Comment 3 Kirk Wilson 2007-11-21 16:48:48 UTC
Final proposal dealing with both the definition of the epr scheme and resolution process (issue 5242).
Comment 4 Valentina Popescu 2007-11-27 19:59:29 UTC
+1 on Kirk's proposal attached under comment #3
Comment 5 Kumar Pandit 2007-11-28 06:40:38 UTC
I agree with the proposal.
Comment 6 Jordan Boucher 2007-11-28 22:15:15 UTC
+1, I agree with the proposal.
Comment 7 Sandy Gao 2007-11-28 23:28:30 UTC
I also agree with this proposal. A few minor changes are suggested in this email. Note that some of the suggested changes also apply to the SML URI scheme definition.
Comment 8 Kirk Wilson 2007-11-29 00:40:26 UTC
Revised version of section 4.2.2:
Comment 9 Kumar Pandit 2007-11-29 01:58:50 UTC
I agree with the revised proposal.
Comment 10 Kirk Wilson 2007-12-06 21:15:48 UTC
Decision on teleconference of 12/6/2007: move EPR scheme to a W3C Note.  This requires several changes to the current text of the SML and SML-IF specifications.  These places are:

SML spec:  Introductory paragraph of section 4.2 refers to the EPR scheme as one of "the two" schemes defined in the specification.

SML spec: content of section 4.2.2 needs to completely deleted.  Suggestion: this would be an appropriate place to discuss the SML "extension mechanism" for defining additional schemes.  For example, to identify the "categories" of schemes that are identified in SML-IF section 5.3.3 (ignoring the schemaLocation but including non-URI schemes).

SML spec: Appendix D.  There is example code that contains an example of an EPR scheme that should deleted, and there is text following that example that discusses having two scheme in one reference.  That text needs to be deleted.

SML-IF spec: The only place the EPR scheme is mentioned is in section 5.3.3, where it is given as an example of category 3 URI reference.  The text will have to be generalized or perhaps the the EPR scheme as a potential type of such a category.
Comment 11 Kumar Pandit 2007-12-07 06:47:00 UTC
EPR related text mentioned by Kirk removed from SML & SML-IF specs.