You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The repository.xsd file, allows containers for various elements at the root level, like Messages, Elements, Datatypes, etc. However, it also allows the Datatype element at the root level. Does this have a use case? Or should the Datatype be moved to the repositoryTypes.xsd file instead, where all other types reside?
The text was updated successfully, but these errors were encountered:
Hello everyone. It would be useful if anyone could identify a use case for keeping datatype in repository.xsd. I could not find one and I am suggesting that we move it to repositoryType.xsd, where all other types are described.
I don't think datatype being defined in repository.xsd allows a <fixr:datatype /> element at the root of a repository, as the definition for repository still only includes datatypes, not datatype.
But I do agree that, for consistency with all the other second-level repository elements, we should move datatype into repositorytypes.xsd. As far as I understand, this should have no effect on users of these XSDs, as they are both defined in the same namespace, so even generated code would be in the same Java package, for instance—I believe the separation of the two XSD files is purely organizational.
patricklucas
added a commit
to patricklucas/fix-orchestra
that referenced
this issue
Sep 10, 2024
The repository.xsd file, allows containers for various elements at the root level, like Messages, Elements, Datatypes, etc. However, it also allows the Datatype element at the root level. Does this have a use case? Or should the Datatype be moved to the repositoryTypes.xsd file instead, where all other types reside?
The text was updated successfully, but these errors were encountered: