OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

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

    Resolution: 
Close no action

From 19th March 2014:

            MOTION: m/Gil s/Adrian Close CAMP-166 with no action.
            Discussion: the type of the value of an attribute must not be changed
            Motion carried by UC.


  was:Close no action


> CLONE - Response to call for comments: "application packag", "_uri", and "DP example"
> -------------------------------------------------------------------------------------
>
>                 Key: CAMP-166
>                 URL: https://issues.oasis-open.org/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 was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]