Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Thursday, July 12, 10 AM US Eastern Time

Connection Info

Join from PC, Mac, Linux, iOS or Android: https://duraspace.zoom.us/j/952326581

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: https://duraspace.zoom.us/zoomconference?m=UwwKqz4RbGAsBAZgCE9XMorMuL0CeV4Q

more details»  copy to my calendar

Attendees

Agenda

  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
    1. https://www.w3.org/TR/rdf11-concepts/#section-html
  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. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyVIVO-1089
        1. https://github.com/OIT-ADS-Web/duke_vivo_ontologies
    5. Improving modeling, for example vcard, academic degrees, organizations, relationships
    6. Alignments, for example schema.org
  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 ...

Notes

  1. Updates:
    1. China
    2. Mike tries to get control about the entry in Bioportal: https://bioportal.bioontology.org/ontologies/VIVO
    3. Schema.org 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:

    CountRange
    160None
    34xsd:string
    14xsd:anyURI
    4xsd:dateTime
    3xsd:boolean
    3xsd:int
    1xsd:date

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

    Code Block
    PREFIX owl: <http://www.w3.org/2002/07/owl#>
    PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
    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. It appears that 4 datatype properties (vivo:overview, vivo:teachingOverview, vivo:researchOverview) should have range specified as rdf:HTML.
  4. Priorities


In Progress or Review Ontology Issues

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject="VIVO" and component="Ontology" and (status="In Progress" or status="In Review")
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

Open Ontology Issues

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject="VIVO" and component="Ontology" and (status="Open")
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5