[OASIS Issue Tracker] Updated: (CAMP-166) CLONE - Response to call for comments: "application packag", "_uri", and "DP example"

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

     [ http://tools.oasis-open.org/issues/browse/CAMP-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Chapman  updated CAMP-166:
---------------------------------

    Description: 
https://lists.oasis-open.org/archives/camp-comment/201403/msg00000.html



2. Do the property names need "_uri" on the end? By putting that on, you prevent using the same property name in future for an inlined version of the linked resource (if a future spec version allows it, e.g. to allow the reduction of HTTP requests needed to get certain information/resources). A property named "operations" on an assembly resource (as indeed the arrow is labelled in the 2nd diagram in section 2.2.6) would have exactly the same semantics as a property named "operations_uri", when the value is a string containing a URI. The advantage of the former would be the possible widening of the allowed value type in future, as mentioned just now, where the value would be a JSON object rather than a string.



  was:
https://lists.oasis-open.org/archives/camp-comment/201403/msg00000.html

1. In section 1.3 Example, it talks about "application package". Is this the same thing as a "Plan resource" (compare with section 2.3)?

2. Do the property names need "_uri" on the end? By putting that on, you prevent using the same property name in future for an inlined version of the linked resource (if a future spec version allows it, e.g. to allow the reduction of HTTP requests needed to get certain information/resources). A property named "operations" on an assembly resource (as indeed the arrow is labelled in the 2nd diagram in section 2.2.6) would have exactly the same semantics as a property named "operations_uri", when the value is a string containing a URI. The advantage of the former would be the possible widening of the allowed value type in future, as mentioned just now, where the value would be a JSON object rather than a string.

3. Example 5 (s4.2.2.1) still says "DP" while example 6 has changed this to "Plan"


Some spelling/grammar points which aren't part of changes from the previous comment period:

4. Section 2.7 Representation skew: "it exists but it an intermediate state" should be "it exists but in an intermediate state".

5. In various places the informal spelling "thru" is used. I would expect this to be "through".


> CLONE - Response to call for comments: "application packag", "_uri", and "DP example"
> -------------------------------------------------------------------------------------
>
>                 Key: CAMP-166
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-166
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: SPEC PR2
>            Reporter: Martin Chapman 
>
> https://lists.oasis-open.org/archives/camp-comment/201403/msg00000.html
> 2. Do the property names need "_uri" on the end? By putting that on, you prevent using the same property name in future for an inlined version of the linked resource (if a future spec version allows it, e.g. to allow the reduction of HTTP requests needed to get certain information/resources). A property named "operations" on an assembly resource (as indeed the arrow is labelled in the 2nd diagram in section 2.2.6) would have exactly the same semantics as a property named "operations_uri", when the value is a string containing a URI. The advantage of the former would be the possible widening of the allowed value type in future, as mentioned just now, where the value would be a JSON object rather than a string.

-- 
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