Lyuba Zehl
Lyuba Zehl
The terminologies, or specifically the terminology definitions should be updated and made a bit more generic. Example, the definition of Subject currently states: "_The investigated experimental subject (animal or person)....
Access and using terminologies (e.g., g-node terminologies) are cumbersome at the moment (cf. example in #74). It would be nice to have convenience functions in the terminology class for this,...
Currently the terminology equivalent of a Section is found in the given repository by matching the Section type. This is problematic for the following reason: A Section type, as I...
While writing the tutorial I realized that the help function in iPython does not always provide proper information. I think the docstrings of the __init__ functions need to be repeated...
Currently odml.Section() takes name, type, parent and definition. For me parent does not make sense here. Especially since odml.Property() does not have a parent args. Another thing: a Section object...
It would be great if the definition of an object is automatic set when an ontology reference is given. We could test this functionality with the [G-Node OEN](https://github.com/G-Node/OEN) which should...
With the separation of more complex odML tree structures from the odML terminology side to a template store side (cf. #136) we could also provide a function that loads an...
The repository attribute should be handled automatically and not manually. In the current implementation the repository can anyway only be used as an attribute in the generation function of a...
While preparing the new documentation I stumbled upon the functionality of terminology for Document and Section objects. Let me demonstrate the cumbersome aspects of the repository functionality for integrating terminologies...
As far as I understood, `repository` should return the actual used terminology-location (uri/url) of the odML object. Currently these attributes/functions behave in the following way (note: the code example is...