Re: [ontology-summit] [ReusableContent] Reuse of Linked Data vis-a-vis R

["Hans Teijgeler" <hans.teijgeler@xxxxxxxxxxx>]

Dear Andrea,

 

Here is an example of an instance of the template ClassOfParticipationDefinition for the RDL (Reference Data Library), in Turtle format:

 

rdl:RDS498493 a tpl:ClassOfParticipationDefinition ;    
    tpl:hasUrClassOfActivity rdl:RDS9706787 ;    
    tpl:hasActivityType rdl:Cc8873cb1-dbc2-11e1-9b23-0800200c9a66 ;    
    tpl:hasUrClassOfParticipant rdl:RDS430694 ;    
    tpl:hasParticipantType rdl:Cc8873cb2-dbc2-11e1-9b23-0800200c9a66 ;    
    tpl:hasParticipantRole rdl:RDS4398439 ;
    tpl:hasDefined rdl:RDS4509302 ;    
    tpl:hasCardinalityOfActivity rdl:RDS4367382 ;    
    tpl:hasCardinalityOfParticipant rdl:RDS2387482 ;    
    meta:valEffectiveDate "2011-09-04T13:45:00+00:00"^^xsd:dateTime .

 

telling that in exactly one member of the ClassOfActivity "hydrostatic testing" one to many members of the ClassOfInanimatePhysicalObject "pressure rated artefact" participate in the Role of "tested".

The two UUIDs are there to allow for deprecation of this information without having to change the ID of the "UrClasses", a.k.a. class of state (but that's another story).

The effective date is for provenance reasons.

 

In the real world we may want to put on record that myPump has been hydrostically tested starting 2013-07-14T14:47:00+00:00 :

 

xyz-corp:T0de66920-89a5-11e3-baa8-0800200c9a66 a tpl:ParticipationOfTemporalPartInWholeLifeActivity;
    tpl:hasActivity xyz-corp:Ted2a0510-89a5-11e3-baa8-0800200c9a66 ;
    tpl:hasTemporalWholeOfParticipant xyz-corp:Ted2a2c20-89a5-11e3-baa8-0800200c9a66 ;
    tpl:hasParticipant xyz-corp:Ted2a2c21-89a5-11e3-baa8-0800200c9a66 ;
    tpl:hasParticipationDefinition rdl:RDS4509302 ;
    tpl:valStartTime "2013-07-14T14:47:00+00:00"^^xsd:dateTime .

 

where reference is made to rdl:RDS4509302 in the RDL.

 

Please refer to http://www.15926.org/templatespecs/TP-ACTIV-01.xml for a graph.

 

We can group a set of template instances into a "pattern" in order to bridge the gap between engineering language and the proper representation of same in 15926. Engineering language is often implicit (uses shortcuts), whilst for true information integration you need to be explicit as much as feasible. The reason for that is that later you may have information about the object that has been skipped by that shortcut. 

 

Regards,

Hans

 

Hans Teijgeler,

Laanweg 28,

1871 BJ Schoorl,

Netherlands

www.mnei.nl

---

From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Andrea Westerinen
Sent: donderdag 30 januari 2014 3:44
To: Ontology Summit 2014 discussion
Subject: Re: [ontology-summit] [ReusableContent] Reuse of Linked Data vis-a-vis Reuse of Ontologies

Matthew, I would like to add one more qualification to my statement that:

  Yes ... modules ~= templates.   With supporting documentation.

It is important to be able to get all the relevant entity declarations and axioms for a module/template in a single zip file or package.   Maybe that is published somewhere, but I could not find any examples.  

Also, I am not sure if you have seen the paper, ISO 15926 Templates and the Semantic Web [1]. It discusses "information pattern" and the ISO templates. 

[1] http://www.w3.org/2008/11/ogws-papers/kluwer.pdf

Andrea

On Wed, Jan 29, 2014 at 3:23 AM, Matthew West <dr.matthew.west@xxxxxxxxx> wrote:

Dear Andrea,

OK. So it sounds like your idea of a module is roughly equivalent to the ISO 15926 idea of a template. The model of signs would itself have been made up of several uses of classification and subtype supertype, and critically the representation and class_of_representation relationships in various modules for specific uses (naming, description, etc). Is that more like it?

 

Regards

 

Matthew West                           

Information  Junction

Mobile: +44 750 3385279

Skype: dr.matthew.west

matthew.west@xxxxxxxxxxxxxxxxxxxxxxxxx

http://www.informationjunction.co.uk/

https://www.matthew-west.org.uk/

This email originates from Information Junction Ltd. Registered in England and Wales No. 6632177.

Registered office: 8 Ennismore Close, Letchworth Garden City, Hertfordshire, SG6 2SU.

 

 

 

From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Andrea Westerinen
Sent: 29 January 2014 02:04

To: Ontology Summit 2014 discussion
Subject: Re: [ontology-summit] [ReusableContent] Reuse of Linked Data vis-a-vis Reuse of Ontologies

 

Matthew, My apologies for the delay in answering, but I was travelling and unable to respond.  

 

My replies are inline ...

 

Andrea

 

On Sun, Jan 26, 2014 at 2:52 AM, Matthew West <dr.matthew.west@xxxxxxxxx> wrote:

Dear Andrea,

 

You wrote:

 

I do recognize that a lot of work went into FIBO to create smaller, more reusable content.  In fact, that was one of the positives that I highlighted in my presentation yesterday [1].  It was straightforward to find concepts and the annotation was amazing!

 

But, I did find that for many of the more "advanced" topics, there were imports of most of the FIBO Foundational Ontology. For example, People.rdf imported Organizations (and FormalOrganizations), Locations (and Countries and Addresses), Goals, etc.  So, the more interesting topic ended up being rather "inclusive."

 

Might there be a way to modularize this even more?

 

 

I’m wondering if you are chasing your tail here, but I’m also not sure if I understand exactly what you are proposing. So let me start by asking: what size do you think a module should be?

 

There are two different ways to answer this depending on your definition of a "module".  When I think of a module, I think of a semantic concept, a definitional element, with a description of its design, uses and the context in which it was developed.  It is by no means a complete/integrated data model.   

 

 

If I look at my own experience, we opted to make ISO 15926-2 an integrated data model. It is only 200 entity types, so it is not very large, and we could have modularized it. However, we considered this rather pointless, not because the modules were tightly bound together, but that to do anything significant you had to use most of what would have been the core modules.

 

Agree.  To model a domain, process, etc. requires multiple semantics and therefore multiple modules.

 

Just to give one example, one of the modules would certainly have been about signs. This is an approximately 15-20 entity type section of the model which says that things can be represented by signs (names, descriptions, definitions, …) and that there are useful classifications of these from utterances of names, to names to file formats etc.

 

Signs, names, ... seems like a valuable semantic concept/"module".  15-20 entity types seems like a large number, however.  Given what I remember from neurological studies, visual recall is limited to 12-15 items and aural recall to 4.  I would advocate smaller modules/groupings that in turn may reference other modules.  The key to making this work, however, is tooling.  (Something we don't have.) 

 

Now what do you have that you don’t want to give names and descriptions of? So even though this makes a neat module, there is not much point in having it separate from the rest of the data model, since you are always going to need it.

 

But, other groups will need this "sign" concept as well, but for very different applications.  And, they will want to combine the semantics and use the constructs in their complete/integrated data model.  But, when the entities are in one, large, contiguous definition, it is difficult or impossible to pull the semantics apart.

 

The same is true of about half the entity types in the Part 2 data model (and nothing stops you ignoring the ones you don’t need anyway).

 

This comes down to the issue being discussed in the other thread for Track A, about finding content for reuse.  I did find valuable content for reuse in ISO 15926.  It was just difficult to find.

 

On the other hand, when we were developing Shell’s downstream (oil tanker to gas station) data model, we certainly did divide the data model (some 1700 entity types) into what we called subject areas (some 20+ of them). The core (essentially a subset of ISO 15926-2) was included in all the other models, and there were some other mid-level subject areas like person and organization, and location, that were also widely used (and a good thing too) and specifically developed to support that reuse

 

I would view your subject areas as domain models built from modules.  I tend to think that concepts like Person, Organization, Location, etc. are reusable modules.  FIBO certainly has them.  :-) I would have loved to have seen a basic Person ontology/model/pattern/archetype documented by ISO 15926 (since it came first in time), and then discussed and/extended by the FIBO team, instead of having an ISO 15926 person and a FIBO person.

 

, but the subject areas that looked at supporting specific parts of the business tended not to be imported by other subject areas, so there was something of a hierarchy of these subject areas, with subject areas mostly being imported from above in the hierarchy.

We limited the subject areas to around 200 entity types, with many much smaller. The reason for this limit is that it seems to be about what one person can hold in their mind without getting lost.

 

My experience is that the number is much smaller than 200, unless you clump the abstractions or have tooling to help manage the concepts, hierarchy and relationships.

 

So how does that compare with what you are looking to achieve?

 

Regards

 

Matthew West                           

Information  Junction

Mobile: +44 750 3385279

Skype: dr.matthew.west

matthew.west@xxxxxxxxxxxxxxxxxxxxxxxxx

http://www.informationjunction.co.uk/

https://www.matthew-west.org.uk/

This email originates from Information Junction Ltd. Registered in England and Wales No. 6632177.

Registered office: 8 Ennismore Close, Letchworth Garden City, Hertfordshire, SG6 2SU.

 

 

--

Andrea Westerinen

T: 425.891.8407

arwesterinen@xxxxxxxxx or andreaw@xxxxxxxxxxx

http://ontolog.cim3.net/cgi-bin/wiki.pl?AndreaWesterinen

organizingknowledge.blogspot.com

---

Geen virus gevonden in dit bericht.
Gecontroleerd door AVG - www.avg.com
Versie: 2014.0.4259 / Virusdatabase: 3684/7043 - datum van uitgifte: 01/29/14

_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/   
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/  
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2014/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2014  
Community Portal: http://ontolog.cim3.net/wiki/     (01)