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
There seems to be an option to define the version of the guidelines that will be used as the basis to generate the schema. I added the source attribute as such to <schemaSpec>:
4.5.0 is mentioned by @lehkost in the issue on gender #46 . Interestingly this is a version that I can set in my setup, but a more recent one produces an error in the Oxygen ODD Framework Transformation. So I make it 4.5.0 for now because making any version explicit is probably better than the way it was before
If I set it to 4.4.0 we don't have the teidata.gender thingy. So, if we simply want to reflect the state of affairs before the gender-related changes were made (see #46) we use 4.4.0 as the base for our first (?) more or less stable version. We could then iterate on the funny ODD discussion and adaption process it with a newer version when a) the transformation works (means after me having updated the ODD framework) and b) we have decided how we go about the "new" gender possibilities; and solve other open questions regarding the schema and encoding practices.
There seems to be an option to define the version of the guidelines that will be used as the basis to generate the schema. I added the
source
attribute as such to<schemaSpec>
:4.5.0
is mentioned by @lehkost in the issue on gender #46 . Interestingly this is a version that I can set in my setup, but a more recent one produces an error in the Oxygen ODD Framework Transformation. So I make it 4.5.0 for now because making any version explicit is probably better than the way it was before#67
The text was updated successfully, but these errors were encountered: