Skip to end of metadata
Go to start of metadata

Thursday, July 12, 10 AM US Eastern Time

Connection Info

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap :
    US: +16468769923,,952326581#  or +16699006833,,952326581# 
Or Telephone:
    Dial(for higher quality, dial a number based on your current location): 
        US: +1 646 876 9923  or +1 669 900 6833  or +1 408 638 0968 
    Meeting ID: 952 326 581
    International numbers available:

more details»  copy to my calendar



  1. Updates 
    1. from China
      1. Discussions with Mark Musen
      2. Discussions with Stefan Decker
    2. Other updates
  2. Use of XMLLiteral and VIVO-1528
  3. Priorities for the ontology
    1. Modules, for example clinical trials, identifiers
    2. Cleaning, for example, adding definitions, providing super Classes, removing/replacing singletons, DOI definition as URL
    3. Internationalization, labels (and annotations?) in multiple languages
    4. Adding new terms/modules, for example, humanities
      1. VIVO-1089 - Getting issue details... STATUS
    5. Improving modeling, for example vcard, academic degrees, organizations, relationships
    6. Alignments, for example
  4. Versioning: We should publish a release now and start to improve the ontology from there. Questions:
    1. SemVer?
    2. Review and release processes
    3. Documentation
  5. ... additional items here ...


  1. Updates:
    1. China
    2. Mike tries to get control about the entry in Bioportal:
    3. is not an ontology, more use in VIVO is appreciated.
  2. Regarding use of XMLLiteral.  vivo.owl currently has 220 datatype properties.  They have ranges tabulated below:


    Here's the query I ran (using robot on vivo.owl in the released version)

    PREFIX owl: <>
    PREFIX rdfs: <>
    SELECT (count(DISTINCT ?s) AS ?nrange) ?r
    WHERE {
      ?s a owl:DatatypeProperty . 
      OPTIONAL { ?s rdfs:label ?l }
      OPTIONAL { ?s rdfs:range ?r }
    GROUP BY ?r
    ORDER BY DESC(?nrange)
  3. Following discussion the group recommends the use of rdf:HTML as range on datatype properties that require HTML editing.  All other datatype property ranges (including no ranges) are edited using a plain text edit editor unless already handled by range. It appears that 4 datatype properties (bibo:abstract, vivo:overview, vivo:teachingOverview, vivo:researchOverview) should have range specified as rdf:HTML.  Note:  other fields may require rdf:HTML type, and other edge cases may be discovered.  The group discussed the impact of language tags, the need to add HTML to some labels, and other potential edge cases.  The group recommends testing in a branch to discover unintended consequences and edge cases.  Existing fields may contain HTML that under this proposal would no longer be able to contain HTML.  Such fields may need to be stripped of HTML by site data managers.
  4. Priorities

See Marijane's meeting notes at

In Progress or Review Ontology Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

Open Ontology Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  • No labels