Changes

Jump to navigation Jump to search
1,026 bytes added ,  10:02, 13 October 2022
Line 64: Line 64:  
== Implementation ==
 
== Implementation ==
 
Do we need a hierarchy or can some aspects be handled by properties? When to decide for one, and when to decide for the other?
 
Do we need a hierarchy or can some aspects be handled by properties? When to decide for one, and when to decide for the other?
 +
 +
 +
Possible implementations:
 +
 +
* Using taxonomy parents to add "structuring" parent entries
 +
** stephane: We use taxonomies a lot for analysis / parsing. It's important that we differentiate "actual" entries from "structuring" entries. e.g. if there's some regexp that looks for [a label] [an ingredient] --> we don't want parents that are not in fact labels to be recognized. One way around it could be to have a property to indicate that an entry is just "structuring", and that it should not be used for analysis, as a suggestion in autocomplete etc.
 +
* Using properties to indicate entries belong to specific categories
 +
** aleene: Proposal: lets remove all parent entries from the taxonomy and only keep the actual labels we want to detect. Each label has a property that specify the category. This category is listed in another taxonomy (label categories), where all the relations between categories are listed.
 +
 +
 +
To be considered:
 +
 +
* It would be good to implement a solution that could work for other taxonomies than labels
       
[[Category:Taxonomies]]
 
[[Category:Taxonomies]]
 
[[Category:Labels taxonomy]]
 
[[Category:Labels taxonomy]]

Navigation menu