Even though the documentation appears to say that Karma only accepts
ontologies in RDF/XML form it actually also accepts Turtle syntax (and thus
N-triples). However, it appears that the discrimination is by file extension,
and everything except extension ttl is treated as RDF/XML

Hello,
Firstly this is not an issue with the code. Sorry for posting this under issues.

I wanted to get some additional documentation on using the module.

Suppose I want get a list of all the entities with a certain property.
The current documentation Wikidata client library for Python only shows how to get a propert

Label: New Term Request

In annotating diseases with HPO, we would like to be able to use phenotypic gender as a clinical modifier (e.g. to note specific disease phenotypes that may only be present or more frequent in one gender). That idea is alluded to in the documentation of the new annotation format, but the terms are missing from the Clinical Modifier subontology. Can you add these terms?

Sometimes it is a good practice, to facilitate the understanding of the ontology, to bring in into the OWL file the definition of a class or property from another ontology, with its corresponding labels and documentation, so that those opening the OWL ontology in tools like Protégé can see them more easily, instead of importing the whole ontology and getting all those classes and properties that m

Adding a checkbox to show/hide a collection from the public view ? Sometimes we need items and collections to be in the database, but we do not them to be seen...

This builds on #733. We've done the work, but don't have clear documentation. Sources:

• discussion in #733
• the table-sorting code, which distinguished tiers: foundry, library, orphaned, obsolete
• validation script

We have a README-editors.md file in this repo, as per convention with other OBO ontologies.

The first line states:

A step-by-step guide for GO Ontology Editors can be found at http://go-ontology.readthedocs.io/.

But we decided to move from RTD to the wiki. This should be updated.

It then goes on to say

This Jenkins job will create releases https

We've documented the notion of placeholder and concrete concepts, where placeholders are intended primarily to structure EDAM, and concrete concepts are intended primarily for annotation purposes. I know this does not stand up to ontological purity, it's a practical thing - intended to give hints (eventually

E.g. when loading cgd we get

2017-05-01 10:16:25,974 INFO  (GafSolrDocumentLoader:189) Skipping taxon closures for unknown id: NCBITaxon:1136231
2017-05-01 10:16:25,980 INFO  (GafSolrDocumentLoader:189) Skipping taxon closures for unknown id: NCBITaxon:1136231
2017-05-01 10:16:25,984 INFO  (GafSolrDocumentLoader:189) Skipping taxon closures for unknown id: NCBITaxon:1136231

First

Many of the methods in the Ontology class (ontol.py) have terse documentation that doesn't include a description of the argument-types. For example, add_synonym takes a single argument syn that is meant to be a Synonym object - not a simple string - but that's not obvious to a newcomer to the library, and requires examination of the source code.

Complete documentation would make the libr

Could someone explain (or give example) to me how can I use taxonomy fields? I've created simple thesaurus that contains hierarchy (broader, narrower). Using the solr admin panel I can query documents that contain fields "tag_ss_taxonomy_X_ss" but how can I use those fields in search?

For example, I have 2 fields:
`"tag_ss_taxonomy_0_ss":["Human",
"Human",
"Human",

Could you please add a couple of output examples? Before I see something, I have little incentive to try the tool.

Have moved most of the data collection routines to rawdata package, so need to redo the documentation to show decent use cases

Maybe we can add a section in the README-editors.md, or create a seperate doc ala HPO. In any case it would be good if QC is clearly explained somewhere (on a by ontology basis, thinking of configurable ROBOT report levels and so on).

The release notes provide great highlights and in-depth detail for the Development version.
Are there similar release notes for Production or does the detail bullet point indicate whether the change was propagated from DEV to PROD?
Thanks

need to document all the annotation usage for editors

such as:
Mondo:equivalentTo
Mondo:obsoleteEquvialent
etc
etc