Using both entry.text and entry.nif__isString
Some parts of the docs refer to "entry.text", some to "entry.nif__isString". We need plugins to be consistent.
There are several options:
nif:isString
Use We would have to:
- Check code
- Check docs
text
everywhere, add it to the context and adapt all code and docs
Use Tasks:
- Check code
- Check docs
- Add
text
tocontext.jsonld
Create mappings/aliases
Either as properties (more efficient) or as a dictionary of aliases that can be checked in __get/setitem__
or similar. There are several options for this.
- Ad-hoc properties in the entry model
- Add aliases to the schema
- Load aliases by reading the context