-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Vocabularies
-
Labels:None
-
Proposal:
We have several cases of generic clients that can interact with V2 and V4 services and internally only use V4 syntax and semantics. One aspect of this is that the client converts the V2 $metadata into V4 $metadata and needs to "remember" whether the original protocol version - and the one to use for URL generation and payload serialization is something else than V4.