Skip to content
#

obo

obofoundry logo

The mission of the OBO Foundry is to develop a family of interoperable ontologies that are both logically well-formed and scientifically accurate. To achieve this, OBO Foundry participants follow and contribute to the development of an evolving set of principles including open use, collaborative development, non-overlapping and strictly-scoped content, and common syntax and relations, based on ontology models that work well, such as the Operations Committee with Editorial, Technical and Outreach working groups.

Here are 61 public repositories matching this topic...

cmungall
cmungall commented Jul 24, 2017

Currently the Jena CSV/TSV writer is used. We may have to implement our own writer here (should be sraightforward iteration over ResultSet) to implement the two requirements here for TSVs:

Inconsistencies with literals

  • for TSVs, the XSD type for literals is shown, and the literal is quoted, e.g. "foo"^^xsd:string
  • for CSVs, the XSD type is not shown, only the string value of the l
cmungall
cmungall commented Jan 11, 2022
  • add "title" for all nested objects
  • remove unused fields (e.g. do_wiki)
  • deprecate some fields (e.g. google_plus, termgenie)
  • generalize/merge some fields (e.g. DO wiki)
  • harmonize (why do we have both preferred_prefix and preferredPrefix)?
  • other tidying (what is ty)?
  • unify json.schema and jsonld contexts
  • document what suggest means in the
attn: Technical WG good first issue