Industrial Ontologies Foundry (IOF) Workshop: Difference between revisions

From NCOR Wiki
Jump to navigationJump to search
 
(6 intermediate revisions by 2 users not shown)
Line 8: Line 8:
'''Venue''' '''[http://doubletree3.hilton.com/en/hotels/new-york/doubletree-by-hilton-hotel-buffalo-amherst-BUFFLDT/index.html DoubleTree Hotel in Amherst]''' in Buffalo, NY, USA
'''Venue''' '''[http://doubletree3.hilton.com/en/hotels/new-york/doubletree-by-hilton-hotel-buffalo-amherst-BUFFLDT/index.html DoubleTree Hotel in Amherst]''' in Buffalo, NY, USA


''Note'': To book your stay at the group rate, please contact the front desk of the hotel directly and say that are coming for the 'Industrial Ontologies Foundry (IOF) Workshop taking place July 18th and 19th'.  
''Note'': To book your stay at the group rate, you may contact the front desk of the hotel directly and say that are coming for the 'Industrial Ontologies Foundry (IOF) Workshop taking place July 18th and 19th' or visit the following link: [http://doubletree.hilton.com/en/dt/groups/personalized/B/BUFFLDT-TIO-20180718/index.jhtml].  


'''Registration''' '''[http://www.buffalo.edu/cas/philosophy/events/iof-workshop-2018.html Registration Page]'''
'''Registration''' '''[http://www.buffalo.edu/cas/philosophy/events/iof-workshop-2018.html Registration Page]'''
Line 14: Line 14:
''Note'': The workshop requires an $80 registration fee, which covers catering, workspace, and technology for two days. However, there is also an optional multi-course dinner for $40 that may be paid in advance at registration.  
''Note'': The workshop requires an $80 registration fee, which covers catering, workspace, and technology for two days. However, there is also an optional multi-course dinner for $40 that may be paid in advance at registration.  


'''[https://drive.google.com/drive/u/0/folders/1D_7Y65g8GKmiCThRu9OeBXKWQjyiXso2 Link]''' to conference discussion documents
*'''For further information please contact [mailto:neilotte@gmail.com Neil Otte]'''
*'''For further information please contact [mailto:neilotte@gmail.com Neil Otte]'''


== Draft Agenda, Wednesday, July 18 ==
== Draft Agenda, Wednesday, July 18 ==


8:00 Arrival and breakfast
0. Arrival and breakfast (8:00am).


8:30 Use Case Q&A, Buttom-up WGs discussions, Updates from Domain (Bottom Up) working groups, if any. Maybe identifying some requirements  
1. Use Case Q&A, Buttom-up WGs discussions, Updates from Domain (Bottom Up) working groups, if any. Maybe identifying some requirements (8:30 - 9:30am)


9:30 Report from Top-Down working group: Identify technical challenges.
2. Report from Top-Down working group (9:30 - 10:30am)
Hope to identify technical challenges.


10:30 Coffee Break
3. Coffee Break (10:30 - 11:00am)


11:00 Where are we now?
4.  Report from the Governance Board (Jim Wilson)  (11 - 11:30am)


11:30 Roadmap discussion (first round)
5. Where are we now? Summarizing where we are now based on the earlier part. Starting of the roadmap discussion. (11:30 - 12:30pm)


12:30 - 1:30pm Lunch, including discussion:
12:30 - 1:30pm Lunch, including discussion on Ontologies for industrial data: is there a convincing business case? introduced by Melinda Hodkiewicz (University of Western Australia)
*Ontologies for industrial data: is there a convincing business case? introduced by Melinda Hodkiewicz (University of Western Australia)


13:30 Roadmap (second round)
6. Roadmap continued (1:30 - 2:30)


14:30 Technical principles
7.  Technical Principle (2:30 - 3:30)


15:30 Break
Break 3:30-4:00pm


16:00 Technical principles (continued)
8 Technical principle continued (4:00 - 5:00)  


17:00 Close
What is the domain dependent ontologies based on the diagram in the charter, should it be within the IOF? If not, how do you govern the usage (maybe this is the licensing issue). There are questions left in the doc. The focus would be to iron out those questions. Some of them are independent from the challenges.
 
18:00 Dinner
 
Link to questions will be provided


== Draft Agenda, Thursday, July 19 ==
== Draft Agenda, Thursday, July 19 ==


8:00 Arrival
0. Arrival and breakfast (8:00am).


8:30 Discussion of challenges
1. Challenges discussion (8:30-12:30):


What are the challenges to discuss?
What are the challenges to discuss?


Use of existing standards.
2. Use of existing standards. (Megan)


How to design IOF ontology by leveraging existing standards which may not be ontology?
How to design IOF ontology by leveraging existing standards which may not be ontology?


How to design IOF ontology by leveraging existing ontologies?
How to design IOF ontology by leveraging existing ontology?
 
10:15 Break


10:30 Discussion of challenges (continued)
3. Ontology merging. Will diversity of ontologies in a particular area be allowed? (Barry will give an introduction)
 
Ontology merging. Will diversity of ontologies in a particular area be allowed? (Introduced by Barry Smith)


Diversity of ontologies in IOF.
Diversity of ontologies in IOF.
Line 71: Line 64:
Dealing with diversity outside of IOF.
Dealing with diversity outside of IOF.


Ontology Merging: How do we resolve conflicts among ontologies within the IOF? (Introduced by Dimitris Kiritsis)
4. Ontology Merging: How do we resolve conflicts among ontologies within the IOF? Introduced by Dimitris Kiritsis (Lausanne)
 
Best practices and software environments for collaborative distributed ontology development
 
IRI for the IOF
 
12:30 Lunch
 
13:30 Discussion of challenges (continued)
 
14:30 Break
 
15:00 Roadmap (second round)
 
'''Notes;;;
 
Johan: 4D does not work with OWL DL. Is IOF tied to OWL DL?
 
Todd: IOF intends to use at least OWL and CL, and not necessary limit to this two.
 
Potential clusters of use cases
 
Maintenance planning (any industry specific?) (Melinda)
 
Possible ontology modules
 
Process plan/maintenance plan
 
Time
 
Units
 
Resource/Equipment/Asset
 
Topology/Geolocation
 
Production planning and scheduling of discrete manufacturing (Dusan, Peter, Walter)
 
'''Possible ontology modules'''
 
Process knowledge/capability
 
Process plan
 
Resource/Equipment/Asset
 
Time
 
Units
 
Topology/Geolocation
 
Supply chain (Farhad Ameri)
 
Product/Process requirement
 
Organization/Agent
 
Could we agree on which module which group will focus on?
 
How do we deal with modules needed by a group that is to be produced by another group.
 
Could we agree on a common starting point for some of these modules?
 
 
'''From CHAMP'''
 
1. Review of Use Cases
 
2. Reports from Domain (Bottom Up) working groups
 
3. Report from Top-Down working group
 
4. Where are we now?
 
5. Roadmap (first round)
 
12:00 Lunch, including discussion on Ontologies for industrial data: is there a convincing business case? introduced by Melinda Hodkiewicz (University of Western Australia)
 
6. Discussion of Technical Principles
 
Example A: Will diversity of ontologies in a particular area be allowed Introduced by Barry Smith (Buffalo)
 
Arrival 8:00
 
Challenges discussion (8:30-12:30):
 
What are the challenges to discuss?
 
• Use of existing standards.
 
• How to design IOF ontology by leveraging existing standards which may not be ontology?
 
• How to design IOF ontology by leveraging existing ontology?
 
• ''Ontology merging. Will diversity of ontologies in a particular area be allowed?'' Introduced by Barry Smith (Buffalo)
 
• Diversity of ontologies in IOF.
 
• Dealing with diversity outside of IOF.


• ''Ontology Merging: How do we resolve conflicts among ontologies within the IOF?'' Introduced by Dimitris Kiritsis (Lausanne)
5. Should reference ontologies contain axioms that support shared understanding of the concept. If so, how should it be done? E.g., Car has transport function\role. If we want to have that kind of axiom in the reference ontology how it should be done, e.g., Car ‘has intended’ function\role (Chris, Evan, Hyunmin). We will likely need a use case to ground this discussion.


Best Practices and and Software Environments for Collaborative Distributed Ontology Development
6. Best Practices and and Software Environments for Collaborative Distributed Ontology Development (Chris Will, Stephen Karman)


IRI for the IOF.
7. IRI for the IOF.


Lunch (12:30 - 1:30)
Lunch (12:30 - 1:30)


Challenge discussion continued (1:30-2:30pm)
8. Challenge discussion continued (1:30-2:30pm)


Break (2:30-3pm)
Break (2:30-3pm)


Roadmap (second round) (3 - 5pm)
9. Roadmap (second round) (3 - 5pm)

Latest revision as of 12:24, 18 July 2018

The Industrial Ontologies Foundry (IOF) Workshop, USA

Date: July 18th and 19th, 2018

Time: 8:00am-5pm, both days

Venue DoubleTree Hotel in Amherst in Buffalo, NY, USA

Note: To book your stay at the group rate, you may contact the front desk of the hotel directly and say that are coming for the 'Industrial Ontologies Foundry (IOF) Workshop taking place July 18th and 19th' or visit the following link: [1].

Registration Registration Page

Note: The workshop requires an $80 registration fee, which covers catering, workspace, and technology for two days. However, there is also an optional multi-course dinner for $40 that may be paid in advance at registration.

Link to conference discussion documents

  • For further information please contact Neil Otte

Draft Agenda, Wednesday, July 18

0. Arrival and breakfast (8:00am).

1. Use Case Q&A, Buttom-up WGs discussions, Updates from Domain (Bottom Up) working groups, if any. Maybe identifying some requirements (8:30 - 9:30am)

2. Report from Top-Down working group (9:30 - 10:30am) Hope to identify technical challenges.

3. Coffee Break (10:30 - 11:00am)

4. Report from the Governance Board (Jim Wilson) (11 - 11:30am)

5. Where are we now? Summarizing where we are now based on the earlier part. Starting of the roadmap discussion. (11:30 - 12:30pm)

12:30 - 1:30pm Lunch, including discussion on Ontologies for industrial data: is there a convincing business case? introduced by Melinda Hodkiewicz (University of Western Australia)

6. Roadmap continued (1:30 - 2:30)

7. Technical Principle (2:30 - 3:30)

Break 3:30-4:00pm

8 Technical principle continued (4:00 - 5:00)

What is the domain dependent ontologies based on the diagram in the charter, should it be within the IOF? If not, how do you govern the usage (maybe this is the licensing issue). There are questions left in the doc. The focus would be to iron out those questions. Some of them are independent from the challenges.

Draft Agenda, Thursday, July 19

0. Arrival and breakfast (8:00am).

1. Challenges discussion (8:30-12:30):

What are the challenges to discuss?

2. Use of existing standards. (Megan)

How to design IOF ontology by leveraging existing standards which may not be ontology?

How to design IOF ontology by leveraging existing ontology?

3. Ontology merging. Will diversity of ontologies in a particular area be allowed? (Barry will give an introduction)

Diversity of ontologies in IOF.

Dealing with diversity outside of IOF.

4. Ontology Merging: How do we resolve conflicts among ontologies within the IOF? Introduced by Dimitris Kiritsis (Lausanne)

5. Should reference ontologies contain axioms that support shared understanding of the concept. If so, how should it be done? E.g., Car has transport function\role. If we want to have that kind of axiom in the reference ontology how it should be done, e.g., Car ‘has intended’ function\role (Chris, Evan, Hyunmin). We will likely need a use case to ground this discussion.

6. Best Practices and and Software Environments for Collaborative Distributed Ontology Development (Chris Will, Stephen Karman)

7. IRI for the IOF.

Lunch (12:30 - 1:30)

8. Challenge discussion continued (1:30-2:30pm)

Break (2:30-3pm)

9. Roadmap (second round) (3 - 5pm)