Closed michmech closed 7 months ago
The distinction between what the commenter calls "top-down" (the parent says who its child is) and "bottom-up" (the child says who its parent is) is only relevant for relational database-like serializations. It's irrelevant for all other serializations (XML, JSON, NVH and RDF). I see no need to make any comments about this in the text.
No further action is required, in my opinion. I suggest to close this issue.
(Submitted by Jonatan Steller, talking about his DMLex implementation in TYPO3)
An easy challenge during the implementation was the direction in which parent/child relations are designed in the part of the spec dealing with relational databases. The spec decides in favour of children indicating their parents while the automatic forms generated by TYPO3 can be used more easily (and in a more user-friendly way) when parents identify their children. The spec already treats the respective section as a suggestion rather than normative content, but a simple note on parent/child relations being possible top-down or bottom-up could help others implement DMLex with less friction.