John Dziurlaj

There is something elegant in reusing the existing schema structures when adding this feature. I don't think constraining the arrays to simple JSON types would provide a lot of value....

Was this reproducible? I can produce a test case as well, if needed.

It is my understanding that the Google "Civics Data Format" is based on 1500-100v1 with custom extensions. So there could be some confusion if you reference both the Google "CDF"...

We are using the XML version of the specification in order to be able to add extensions to the format via namespaced elements. We cannot do that with JSON in...

We could make properties work for our current use case. We are exploring another use case for extending [service definition](https://cyclonedx.org/use-cases/#service-definition) which would almost certainly require the creation of structures beyond...

Yes I had. I pulled the clean one on this repo and reran and got this: ``` code: "XPST0081" ​ message: "No namespace binding for prefix 'xforms'" ​ name: "XError"...

As a workaround I can get this to function if I specify `position="child"` for `xf:insert` which seems to avoid the problematic `copy-of` in the XSLT.