Closed RaySinnema closed 9 years ago
+1
+1 for ref
Note that this is a breaking change for anyone using data models.
Why is that? We're just adding the ref
attribute, not taking anything away or changing any existing semantics, are we?
The ref
attribute by itself is not a breaking change, we have several related issues, and the data-model
element is going away.
Is this resolved by the solution in issue #34 ?
Yes.
Consider a system for working with people and organizations they are affiliated with. There would be resources
/organizations/{id}/
and/persons/{id}/
and the representation for both would include an address. With the current schema, we would have two<data-model>
elements that contain nested properties for the address. IOW, we would have to duplicate the address structure.I propose we eliminate that duplication by introducing a reference, e.g. something like: