[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (SRAMP-15) Type Encoding
[ http://tools.oasis-open.org/issues/browse/SRAMP-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26468#action_26468 ]
Randall Hauch commented on SRAMP-15:
------------------------------------
The following sections in the (original) Atom Binding document would need to be addressed:
Section 2.3.3 "Service Document" - This section does not point out that the URL for the Service Document (e.g., "/s-ramp/serviceDocument") is the only fixed/pre-defined URL, and that all other URLs should be determined by accessing the Service Document. It should also probably point out that although the "/s-ramp/{artifactModel}/{artifactType}" form used in the rest of the document's examples are merely possible URL forms and not mandated by the specification. Suggested wording here would be appreciated. This may need to be made as visible as possible using a Note.
Section 2.3.5 and subsections - Describe how artifacts are published and often refer to collections (e.g., "/s-ramp/xsd") and other URLs. However, many of these are examples, so they may be acceptable as is, although those that don't mention the Service Document URLs should probably do that.
Section 3.3.1 appears to require that all stored queries are accessible at "/s-ramp/queries". I assume this should be changed to say that they are accessible at a collection defined in the Service Document, which may be "/s-ramp/queries". Other opinions?
Appendix B "S-RAMP URI Space" - This appendix describes the URI space that appears to be expected, but per this issue it needs to be changed to say the presented URI space is one example of a URI space used by an implementation.
Section 2.3.5.2.2 "Publishing Using POST of ZIP files" - This section mandates that ZIP files should be posted to the "/s-ramp" URI space. Should this be specified in the Service Document, or should the spec maintain this requirement?
> Type Encoding
> -------------
>
> Key: SRAMP-15
> URL: http://tools.oasis-open.org/issues/browse/SRAMP-15
> Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
> Issue Type: Improvement
> Components: Foundation
> Affects Versions: 1.0
> Environment: N/A
> Reporter: Vincent Brunssen
> Assignee: Randall Hauch
> Fix For: 1.0
>
>
> Issue-015 from the contributed issues document
> Artifact URLs have the type encoded in them. Having /s-ramp/{artifactModel}/{artifactType} should not
> be required. Instead this should be inferred from the ServiceDocument and would allow for implementers
> to define their own URL's.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]