Ontology PSIG Agenda

OMG Technical Meeting

2020-06-21 to 2020-06-26
Timezone: UTC-04

Up to date agenda can be found at: https://omg.org/events/2020Q2/agendas/OntologyPSIGCalendar.html

Additional information can be found at: https://omg.org/events/2020Q2/agendas-temp/OntologyPSIGCalendar-aux.pdf

Thu 2020-06-25
09:00-09:45Ontological spectrum
Discussion of the spectrum of different sorts of ontologies that may be published as standards using the same formalism and the different development methodologies and requirements that may be appropriate for them (Mike Bennett, Hypercube)
09:45-10:30W3C PROV-O Issues
Issues with reusing the W3C PROV-O ontology, which otherwise could be among the vocabularies consistently used for ontology and specification metadata (Elisa Kendall, Thematix)
10:30-11:30Metadata Requirements
Discussion of metadata requirements for OMG ontology specifications and requirements for ontology artifacts associated with them (Elisa Kendall, Thematix)
Enterprise Knowledge Graph Foundation (EKGF) organization and its tools that enable development of ontology content for standards. (Pete Rivett, Adaptive)

General notes:

OMG Ontology Platform Special Interest Group plenary meeting

OMG virtual Technical Meeting

Thursday, 25 June 2020

Acting chair: Evan Wallace


Meeting Theme: What are the sorts of ontologies that are appropriate to be developed as standards and what are the characteristics that make them such?  These characteristics may include: producibility[1], utility, usability, adaptability, understandability, and sustainability[2].  What methodology(ies) produce ontologies with these characteristics?


Meeting Goal: Understand the range (and perhaps key categories) of ontology artifacts that we would like OMG to produce and the sorts of processes, requirements, meta-standards, and tools needed to produce them.



Determine which elements of ontology development methodologies are needed to produce ontology artifacts of particular desired classes and the requirements that are appropriate for them.  Ultimately, we would like this activity to identify which requirements for ontology artifacts should apply to all, and identify which requirements apply only to specific subcategories of ontologies.  

Also, identify tools available that may help us manage ontology development processes and evaluate ontology content to suite the identified requirements.

[1] Utility is about the usefulness of the artifact in returning value against whatever objective/need a user might have.

[2] Adaptability is the ease and extent to which one can apply or extend the original artifact to purposes or domains not directly part of the use cases and requirements driving the design of the original artifact.

Call in info:

Elisa Kendall invites you to join this Webex meeting.

Meeting number (access code): 126 142 4804

Meeting password: omgONTJune2020

Thursday, June 25, 2020

6:00 am | (UTC-07:00) Pacific Time (US & Canada) | 3 hrs

Join meeting

Tap to join from a mobile device (attendees only)

+1-650-479-3208,,1261424804##  Call-in toll number (US/Canada)

Join by phone

1-650-479-3208 Call-in toll number (US/Canada)

Generated at: 2020-07-10 13:22