[OASIS Issue Tracker] Commented: (SRAMP-15) Type Encoding

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/SRAMP-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28230#action_28230 ] 

Randall Hauch commented on SRAMP-15:
------------------------------------

My proposal for the changes to the Foundation document have been uploaded to the S-RAMP document space, and is available at http://www.oasis-open.org/apps/org/workgroup/s-ramp/document.php?document_id=44002

This change, however, will make it more difficult to define the query language, because the query grammar now depends on the structure of the URIs. So I think there are several possible approaches to take in resolving this issue, and I plan on discussing these options and coming to an agreement on the desired course of action during the upcoming virtual F2F meeting on October 24-26. The possible approaches are:

1) Leave the "/s-ramp/{ModelType}/{ArtifactType}" syntax for the URIs and query grammar, but change the Atom Binding to expose this structure in the service document. In other words, the structure remains fixed whereas the service document would follow good RESTful conventions by dynamically exposing this structure (and any implementation-specific model types or artifact types).

2) Decouple the query grammar from the literal resource URI structure: continue to use the "/s-ramp/{ModelType}/{ArtifactType}" syntax in the query grammar (where the syntax would define the logical structure used for constraints), but repository implementations are free to use a completely different resource URI structure and would expose this structure within the service document. I'm not sure if this approach even makes sense.

3) No longer define the resource URI structure for use by the repository and queries. The "location-path" rule within the query grammar would need to be made more general, and the variations in the current rule would need more description. The proposed changes to the Foundation document mentioned capture this approach, though I would like some suggestions for exactly how to change the "location-path" rule.

> 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