Closed dosumis closed 7 years ago
Plan to add the ability to specify regex patterns. Synonyms can the be specified by a mix of concatenation & regex given input synonyms.
Scope algebra looks good.
One thing we use in TG to exclude synonyms are (custom) scopes. For example PO has a custom scope for non-english translations, which should be avoided for the synonym generation. Maybe consider a white list or a black list of scopes as configuration option.
What should be included/excluded is often driven by the external ontology and how the use synonyms (i.e. ChEBI IUPAC synonyms are not useful).
Good point
This could be configured either within the template, or as some kind of additional parameter or conf file passed in to the generator. The latter has the advantage of not complicating the pattern language. Also some rule may end up being procedural, which also points to outside configuration.
On 12 Oct 2015, at 11:28, hdietze wrote:
One thing we use in TG to exclude synonyms are (custom) scopes. For example PO has a custom scope for non-english translations, which should be avoided for the synonym generation. Maybe consider a white list or a black list of scopes as configuration option.
What should be included/excluded is often driven by the external ontology and how the use synonyms (i.e. ChEBI IUPAC synonyms are not useful).
Reply to this email directly or view it on GitHub: https://github.com/dosumis/dead_simple_owl_design_patterns/issues/3#issuecomment-147483642
A basic synonym scope algebra for combining concepts:
Rules for synonym types are other properties will likely be domain-specific. But some general ones:
I think it might be useful to have a type for trivial lexical shuffling. For example, a display may want to hide "development of lung" if the primary label is "lung development".
In general it would be useful to track evidence for a synonym, so we can do cascading deletes. I wonder how many stale synonyms we have in GO, or cases where we need to auto-fill.