-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: SPEC PR2
-
Labels:None
-
Proposal:
-
Resolution:
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.