28 June 2024 TOB Meeting Agenda & Notes

By tschneider
5 min

0) Announcements

  • Next TOB Meeting – 12 July 2024 2023

  • Need ‘contributions’ to Core ‘Issues’

1) Working Group Updates

  • Melinda email a detailed update for the Maintenance working group:

    • A paper about the development of the IOF Maintenance ontology was published on ArXiV in April Iof-maint -- Modular maintenance ontology . We had submitted it to ESWC but one of the reviewers wanted more validation work so we have been doing that and will resubmit next year. With the help of one of our students (Briana), Caitlin and her built a testing script to check IOF-maint 1) can answer the five competency questions in the ROMAIN paper , and 2) run 11 tests to correctness and consistency of simple equivalence, subclass, and disjoint relations within Iof-maint. We are in the process of writing this up. The testing work can be found in the IOF Ontology repository (currently in branch maint_testing under maintenance/scripts/testing/.

    • Tangentially related to this, with another collaborator (Tyler Bikaun) we released the MaintIE schema and data set. There’s a GitHub site and LREC paper. The annotated data set is the largest open entity and relation tagged data set released for maintenance work orders. The process allows for the extraction of annotated triples from unstructured texts. The final schema should allow us to map to IOF-Core and IOF-maint. Although unpublished we have created RDF triples from the outputs of this process and run some reasoning on everyday industry questions that otherwise take ages to answer.

    • Meanwhile now Caitlin has submitted her PhD we are hoping to find time to progress the failure modelling project – how to model failures. I know I talked about this at the IOF meeting in February and there are links to the work being done on a Quality Ontology. Part of the challenge (in my mind) is there are 2 sets of data we need to model – one on failures that could happen and the other on failures that have happened. And the dependency between failure and requirement (failure depends on what function was required). We are hoping to start again on this in August.

    • We are not currently having any regular iof-maint WG meetings. We might start again once we get going with the Failure work but seem to be going ok with on-demand asynchronous communications for now.

    • I am going to be in Europe in October from 10th up to and including to the ISO TC184 SC4 Plenary meeting in Stavanger (Oct 21-25) – anyone going? WG26 is currently dealing with comments on the CD of ISO CD 23726-3 (IDO). I am collaborating on a valve selection ontology (with Aibel, Equinor, DNV, Aker BP) as a demo for IDO which is super interesting. Did IOF get liaison status?

  • Jim Logan – Systems

    • Described their survey efforts, Jim gave a presentation to the OMG systems engineering domain special interest group and asked them to nominate systems engineers to take the survey;

    • There have been presentations about a visual modeling language, the Information Modeling Framework (IMF), developed at the University of Norway, they want to collaborate and align with our with our ontologies;

    • Arco and Miles and Jim are talking about visualizations;

  • Alexandru – Materials Science

    • Working on Qualities ontology;

    • Working with Barry on a couple of issues;

    • We have an activity connected about representing requirements and standards

  • Will – Architecture

    • Have a provisional document on Property chains, normative and non-normative, will be ready for a TOB vote shortly;

      • Use of Property Chains will require a TOB review (make sure that this isn't going to cause any difficulties down the road)

    • Continuing work on the ontology process documentation

  • Ana – Product Service Systems

    • Working on a Bill of Materials for discrete manufacturing, not continuous/process;

    • A special (off schedule) meeting will be held 3 July 2024, will use MS Teams

  • Dusan – Production Planning Scheduling

    • Working on refining definitions to conform to IOF requirements and ontology for future artifacts;

    • Will be working with Gabriela and PSS group on continuous/process manufacturing relevant to scheduling

      • Gabriel is going to be being visiting the US at the end of July; Gabriela and I will do workshop in a conference

  • Farhad – Supply Chain

    • Working on ‘Certificate’, need to add additional ‘Process’ classes, parts may need to be moved to the Core ontology;

    • The IMF gang has some relevant use cases

    • Will be publishing a paper based initial Supply Chain ontology

    • Need to move the current version of the Supply Chain ontology from ‘provisional’ to fully released.

      • Todd said that can be done by submitting the ontology for review and ballot

2) TOB Membership Rules Update – Vote

  • The changes and most recent revisions Evan made were reviewed and discussed

    • Evan explained the reasoning behind the changes

  • Will asked about the status of ‘Task Groups’ vis-à-vis the revised TOB membership rules

    • Todd said, per OAGi rules there are only working groups

  • Serm raised a question about the number of TOB ‘Standing Members’ (in relation to the Number of Working groups) i.e. there cannot be more TOB ‘Standing Members’ than Working Groups;

    • Dusan did a quit count of ‘Standing Members’ and found that there are 8, the same number of Working Groups

  • Jim Logan asked if Quorum were needed (e.g., for a vote) and he were present, would he be able to be counted as a working group member?

  • Evan and Todd answered yes

  • Serm asked if there were term limits for Working Group chairs

    • Todd answered that any such rules are determined solely by each working group

  • Todd asked for a motion to vote on the changes to the TOB Membership rules as presented and discussed

    • Will Sobel made a motion to vote on the changes; Evan Wallace seconded the motion

    • The vote was carried out via Zoom’s chat (i.e. each TOB voting member present cast their vote via chat), with the exception of Barry Smith and Melinda, each of which voted yes (to accept the changes);

      • Of the TOB voting members present and constituting a quorum, all voted ‘Yes’ to accept the changes

      • The changes to the TOB Membership Rules have been adopted

3) Github Branch Creation (via Jira)

  • Will explained the current problem with the current branches in Github (i.e. Github is essentially ‘flat’, not like a file system)

  • He explained how branches should be named based on Jira issues

  • He shared he screen to show in detail how to create a Github branch from/via Jira

  • There was discussion of how working groups should be identified in Jira (and hence Github branches)

  • Will will be creating documentation for all of this

4) Working Groups - Planning Ahead

  • Todd raised the issue of working groups planning ahead so that other working groups might identify commonalities (e.g., to collaborate or avoid duplication)

  • Will Sobel explained how Jira can be used to accomplish this goal

     

NOT COVERED DURING THIS MEETING

5) ‘Comparison of different diagramming styles and tools’

https://oagi.atlassian.net/wiki/spaces/IOF/pages/5045682177

6) Meetings in August (2024)?

Participants

@tschneider @Ana Correia @Alexandru Todor @Dusan Sormaz @Evan Wallace @Farhad Ameri (Unlicensed) @Jim Logan @Jinzhi Lu @Milos Drobnjakovic (Unlicensed) @Serm Kulvatunyou @William Sobel @Yves KERARON

https://oagi.org