slide ISO TC184/SC4 Open Technical Forum, Louisville Beyond data models (what we can do with vocabularies/ontologies alone) David Leal

slide ISO TC184/SC4 Open Technical Forum, Louisville Semantic Web technologies RDF (Resource Description Framework) –making statements on the Web – N3 (Notation 3) –a simple way of writing down an RDF statement – A opportunity to: record information more simply enable others to use our concepts use the concepts of others

slide ISO TC184/SC4 Open Technical Forum, Louisville Jane believes Getting started Janet John loves RDF diagram N3 :Janet :loves :John. :Jane :believes { }

slide ISO TC184/SC4 Open Technical Forum, Louisville Getting started people:Janet relationship:loves people: relationships: namespaces identify the people identify the human relationships

slide ISO TC184/SC4 Open Technical Forum, Louisville What we do well Blobs –Encapsulate the data that defines the shape –Encapsulate the data that is the specification of the part. –Encapulate the data that is the specification of the analysis. The data inside the blob and the data outside the blob are separate – what is inside can be specified in a contract. It is “data push” – I tell you what you need to know. The blob can be an attachment – it can be downloaded by FTP. This is what the EXPRESS data model + part 21 / 28 file methodology achieves.

slide ISO TC184/SC4 Open Technical Forum, Louisville When is what we do well useful? Command driven processes –I tell you what to do, and what you need to know to do it. Processes where the data within the blob can be easily defined –Shape information is our success story – it has a well defined scope –Engineering analysis has not taken off – the scope is fuzzy and much larger Processes where the blob has a particular destination system –CAD, CAE, CAM, PDM You need to know the type of destination system is before selecting the type of the blob. This is why we have different types of blob – AP 203, AP209, AP210, AP214, …

slide ISO TC184/SC4 Open Technical Forum, Louisville What we cannot do yet Enable a user to publish data on the Web – where the user makes his or her own decision about what data are published –Somebody else can use the data, if they want to. Enable a user to use SC4 standards for some data and other standards for other data –There cannot be two-way links between objects in a blob defined by a STEP AP and an IFC or OpenGIS object –All we can do is make external references by “magic strings” Enable groups of users to extent SC4 standards as they wish –All we can do is allow user defined “magic strings” In the real world, data is defined using many different vocabularies – the SC4 vocabulary is one of many. The Semantic Web provides a technology which can cope with this.

slide ISO TC184/SC4 Open Technical Forum, Louisville Tracking back materials information item: part:toDesign model:ABC456_v3 ; part:madeFromBatch item: model: alcoa: URI of an individual part URI of a design URI of a batch of material URI of a vocabulary about part:

slide ISO TC184/SC4 Open Technical Forum, Louisville Tracking back materials information alcoa:PQR mat:materialProductType mil5:XYZ2048-asSheet ; mat:manufacturingProcess alcoa:LineA item: part:toDesign model:ABC456_v3 ; part:madeFromBatch alcoa:PQR a classification with respect to a standard the actual manufacturing process a vocabulary for manufacturing processes – perhaps not ISO 10303

slide ISO TC184/SC4 Open Technical Forum, Louisville Tracking back materials information alcoa:LineA mat:performedBy alcoa:LineA ; act:startTime [ iso8601:utc “ T09:00” ] ; act:endTime [ iso8601:utc “ T17:00” ]. alcoa:PQR mat:materialProductType mil5:XYZ2048-asSheet ; mat:manufacturingProcess alcoa:LineA item: part:toDesign model:ABC456_v3 ; part:madeFromBatch alcoa:PQR more manufacturing vocabulary facility that performed the process generic work flow vocabulary other ISO committees work on time

slide ISO TC184/SC4 Open Technical Forum, Louisville Tracking back materials information alcoa:specimen part:madeFromBatch alcoa:PQR ; part:toDesign test:SpecimenTypeXYZ. alcoa:LineA mat:performedBy alcoa:LineA ; act:startTime [ iso8601:utc “ T09:00” ] ; act:endTime [ iso8601:utc “ T17:00” ]. alcoa:PQR mat:materialProductType mil5:XYZ2048-asSheet ; mat:manufacturingProcess alcoa:LineA item: part:toDesign model:ABC456_v3 ; part:madeFromBatch alcoa:PQR a standard specimen type a use of our vocabulary in a different environment Our vocabularies cannot be re-used by others – our data models cannot be

slide ISO TC184/SC4 Open Technical Forum, Louisville Tracking back materials information alcoa:Test obs:onSpecimen alcoa:specimen ; act:toProcedure test:MaterialTestTypePQR ; obs:givesResult alcoa:Result alcoa:specimen part:madeFromBatch alcoa:PQR ; part:toDesign test:SpecimenTypeXYZ. alcoa:LineA mat:performedBy alcoa:LineA ; act:startTime [ iso8601:utc “ T09:00” ] ; act:endTime [ iso8601:utc “ T17:00” ]. alcoa:PQR mat:materialProductType mil5:XYZ2048-asSheet ; mat:manufacturingProcess alcoa:LineA item: part:toDesign model:ABC456_v3 ; part:madeFromBatch alcoa:PQR more generic workflow vocabulary a standard test method a generic measurement and observations vocabulary

slide ISO TC184/SC4 Open Technical Forum, Louisville Tracking back materials information alcoa:Result { alcoa:specimen mat:compressiveYieldStress [ iso:MPA “201.3” ] } alcoa:Test obs:onSpecimen alcoa:specimen ; act:toProcedure test:MaterialTestTypePQR ; obs:givesResult alcoa:Result alcoa:LineA mat:performedBy alcoa:LineA ; act:startTime [ iso8601:utc “ T09:00” ] ; act:endTime [ iso8601:utc “ T17:00” ]. alcoa:PQR mat:materialProductType mil5:XYZ2048-asSheet ; mat:manufacturingProcess alcoa:LineA item: part:toDesign model:ABC456_v3 ; part:madeFromBatch alcoa:PQR alcoa:specimen part:madeFromBatch alcoa:PQR ; part:toDesign test:SpecimenTypeXYZ. a statement with provenance

slide ISO TC184/SC4 Open Technical Forum, Louisville Many vocabularies – only a few are within the scope of SC4 product design units manufacture material handbook material test workflow observations inventory personnel maintain electrical networks GIS earth sciences life cycle assessment

slide ISO TC184/SC4 Open Technical Forum, Louisville Data models Data models are good –they specify exactly what data should be supplied for a particular activity –they have constraints to ensure that the data is complete and correct But –different activities need different data –different activities have different ideas about what “complete” means So –There are lots of similar but overlapping data models

slide ISO TC184/SC4 Open Technical Forum, Louisville Vocabularies/ontologies Vocabularies/ontologies are good –precise statements can be made about things –different vocabularies can be used together to say what you want But –there is no constraint on what is said –you may not say all that needs to be said So –vocabularies are not enough to specify the data flow between activities –replacing data models with vocabularies + rules is a research activity

slide ISO TC184/SC4 Open Technical Forum, Louisville What next We need vocabularies/ontologies as well as data models –cannot be generated automatically from out EXPRESS schemas –people have to read the words –real work – but if we don’t do it others will duplicate what we have done We need to address the type of business problem for which a data model is not the solution, but a standard vocabulary is Other standards committees have similar problems –data models in UML, or XML Schema electrical networks GIS building and construction materials information, earth sciences

slide ISO TC184/SC4 Open Technical Forum, Louisville Concretely Make a start with vocabularies corresponding to ISO module ARMs –Publish as a TS “Gellish” (proposal from the Netherlands) is a possible addition to this vocabulary Look at vocabularies from other standards –Agree owl:sameAs statements – a “same as” is a success! –Find who’s vocabularies we can use, and do more in that area. If two data models overlap it is a problem – which do you use? If two vocabularies overlap it is a success – you have synonyms