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: FW: [camp-comment] Response to call for comments: "application packag", "_uri", and "DP example"


 

 

From: Martin Chapman
Sent: 03 March 2014 16:18
To: Martin P Pain; camp-comment@lists.oasis-open.org
Subject: RE: [camp-comment] Response to call for comments: "application packag", "_uri", and "DP example"

 

Martin,

 

Many thanks for taking the time to read and comment.

I have logged this feedback in https://tools.oasis-open.org/issues/browse/CAMP-164

The TC will discuss this during one of its meetings and I will let you know of the outcome.

 

Regards,

  Martin Chapman.

 

 

From: Martin P Pain [mailto:martinpain@uk.ibm.com]
Sent: 03 March 2014 10:37
To: camp-comment@lists.oasis-open.org
Subject: [camp-comment] Response to call for comments: "application packag", "_uri", and "DP example"

 

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



Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
Open Services for Lifecycle Collaboration - Automation WG joint chair


E-mail: martinpain@uk.ibm.com
Find me on:
LinkedIn: http://www.linkedin.com/profile/view?id=99869908 and within IBM on: IBM Connections: https://w3-connections.ibm.com/profiles/html/profileView.do?userid=12c849c0-ddd5-1030-9b5f-d70a3a891b7f 

IBM




IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU



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