Handling of the "uima.noNamespace" prefix #170
Comments
jcklie
added a commit
that referenced
this issue
Aug 14, 2021
- Move no namespace handling to xmi - Add better tests for this
jcklie
added a commit
that referenced
this issue
Aug 14, 2021
- Move no namespace handling to xmi - Add better tests for this
reckart
added a commit
that referenced
this issue
Aug 19, 2021
* main: #172 - Naming: cas.add_annotation(s) (#181) #175 - Set a feature if the feature name is in a variable (#180) #175 - Set a feature if the feature name is in a variable #174 - FSes that are only transitively referenced cannot be serialized (#179) #170 - Handling of the "uima.noNamespace" prefix (#178) No issue #173 - Rename add_feature to create_feature (#177) # Conflicts: # cassis/typesystem.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
In XMI files, an artificial "uima.noNamespace" prefix is introduced for types that are not in any package. However, cassis does not only handle this situation in the XMI (de)serializer code but leaks this prefix into the actual type system. The Apache UIMA Java SDK only uses this prefix in the XMI serialization code (also in the legacy JSON serialization code) but not in the actual type system.
Describe the solution you'd like
The XMI deserializer should strip this prefix. The XMI serializer should add it again. The TypeSystem (de)serializer should not have to worry about it at all.
The text was updated successfully, but these errors were encountered: