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
I was not using computed element constructors as I did not realize namespaces could be dynamically constructed. A better way to handle this is to have somewhere in the config (I think) a list of the namespaces that should occur based on the entity type.
This can be created in the config module and used by the transform and templating scripts to dictate the output of the xmlns declarations on the TEI element (this avoids any duplication in the sub-elements).
The current setup does not allow entity-specific customization of which namespaces are declared on the TEI root element. Changing to something like the below should be much more useful
I was not using computed element constructors as I did not realize namespaces could be dynamically constructed. A better way to handle this is to have somewhere in the config (I think) a list of the namespaces that should occur based on the entity type.
This can be created in the config module and used by the transform and templating scripts to dictate the output of the xmlns declarations on the TEI element (this avoids any duplication in the sub-elements).
The current setup does not allow entity-specific customization of which namespaces are declared on the TEI root element. Changing to something like the below should be much more useful
In config, then, loop through the namespace elements, test if
@entity
is all or the one selected and add create a namespace usingThis list of prefixes can then be added to the element constructor for the TEI root element.
Priority because of #39
The text was updated successfully, but these errors were encountered: