'Ontology Design Patterns' - User contributions [en]

'Ontology Design Patterns':KIELD2010

2010-07-09T16:44:55Z

FrancoisScharffe:

== Welcome to the 1st Workshop on Knowledge Injection into and Extraction from Linked Data ==

The first workshop on knowledge injection into and extraction from linked data is a co-located event with [http://ekaw2010.inesc-id.pt/ EKAW 2010], [http://ekaw2010.inesc-id.pt/conference-venue.html held in Lisbon (Portugal)] on October 2010.

'''Notice: the exact date of the workshop is still to be fixed. It will be either October 11th or 15th.'''

__TOC__

== Motivation and objectives ==
The first workshop on Knowledge Injection to and Extraction from Linked Data (KIELD2010 at [http://ekaw2010.inesc-id.pt/ EKAW 2010]) will gather three prominent sub-communities of Knowledge Engineering and Management: Knowledge Modelling, Knowledge Discovery and Linked Data. The rapid growth of the Linked Data cloud, in parallel with on-the-fly design of relevant vocabularies, presents new opportunities for traditional research disciplines.

Most notably:
* Although the popular vocabularies reflect today needs, they sometimes lack deeper ontological reflections. State-of-the-art knowledge modelling, especially the pattern-based ontology design principles, could help connect Linked Data vocabularies to more sophisticated models, while keeping themselves simple. Furthermore, collaborative ontology design methodologies could find their way to the process of vocabulary design, currently undertaken by VoCamp communities and stand-alone groups.
* The linked data themselves represent a large and growing resource woven from numerous components. Empirical knowledge discovery in linked data, carried out by machine learning and data mining algorithms, could reveal interesting patterns on frequently used structures, which could then be fuelled back to the vocabulary design. Existing techniques for mining network-structured data, such as graph databases or web links, are likely to require adaptation so as to take account of links that are typed according to semantically rich and heterogeneous schemata.

Aside the [http://ekaw2010.inesc-id.pt/ EKAW 2010] conference itself, the workshop is informally associated with the series of [[WOP:2009|WOP workshops - Workshops on Ontology Patterns]]. Participants of the previous successful WOP (1st edition at ISWC2009) are encouraged to submit to KIELD 2010.

By this interdisciplinary nature KIELD2010 aims at being of high interest for both researchers and practitioners of all three areas mentioned above. Furthermore, it will give space to ongoing and pioneering research activities, which would still be too preliminary as conference publications, although extremely hot as topics in the semantic technology field.

== Key topics ==

The workshop welcomes research, application, and position papers on the following topics (non-exclusive):

=== Ontology engineering for Linked Data ===
* Methodologies
* Ontology patterns extraction
* Ontology patterns identification and discovery
* Pattern-based triplification
* Anti-patterns or worst practices

=== Data mining from Linked Data ===
* Entity recognition
* Link prediction
* Pattern mining
* Sequential patterns
* Rule mining

=== Linked Data in use ===
* Domain applications based-on linked data
* Linked data exploitation
* Interaction with linked data

== Paper Submission ==

Two types of submissions will be accepted: full papers presenting recent research results, and position papers presenting either research in progress or key issues in the scientific discussion.

All submissions have to be formatted according to the Springer LNCS format, in PDF. Full papers are limited to 12 pages and position papers to 6 pages.

All submissions must be performed through [http://www.easychair.org/conferences/?conf=kield2010 KIELD EasyChair].

The accepted papers will be published in workshop notes, under CEUR. (to be confirmed)

== Program Committee ==

* Eva Blomqvist, ISTC-CNR, Italy
* Ciro Cattuto, ISI Foundation, Italy
* Claudia d'Amato, University of Bari, Italy
* Mathieu d'Aquin, KMI Open University, UK
* Nicola Fanizzi, University of Bari, Italy
* Aldo Gangemi, STLab ISTC-CNR, Italy
* Alfio Gliozzo, STLab ISTC-CNR, Italy
* Marko Grobelnik, Jozef Stefan Institute, Slovenia
* Tom Heath, Talis, UK
* Luigi Iannone, Manchester University, UK
* David Jensen, University of Massachusetts Amherst, USA
* Agnieszka Lawrynowicz, Poznan University of Technology, Poland
* Pascal Poncelet, LIRMM, Université Montpellier 2, France
* Marko Rodriguez, AT&T, and Vrije Universiteit Brussels, Belgium
* Steffen Staab, University of Koblenz-Landau, Germany

== Organizers ==

* Valentina Presutti, ISTC-CNR Rome, Italy
* E-mail: valentina.presutti_at_cnr.it

* Francois Scharffe, INRIA Grenoble Rhone-Alpes, France
* E-mail: francois.scharffe_at_inria.fr

* Vojtech Svatek, University of Economics, Prague, Czech Republic
* E-mail: svatek_at_vse.cz

== Important dates ==

* July 15, 2010: Paper submission deadline
* August 9, 2010: Paper acceptance notification
* August 25, 2010: Camera-ready versions of papers
* October 11th: Workshop day

[[Category:Event]]
{{Event
|Name=1st Workshop on Knowledge Injection into and Extraction from Linked Data (KIELD2010)
|HasStartDate=2010/10/11
|HasEndDate=2010/10/11
}}
{{Submission deadline
|deadline=2010/07/15
|expired=The submission deadline has expired!
|intime=You are in time for submitting your paper.
}}

'Ontology Design Patterns':News/8

2010-04-06T13:32:35Z

FrancoisScharffe: New page: {{NewsInfo |SubmittedBy=FrancoisScharffe |PostedOn=2010-04-6T13:13:28 }} {{TitleDescription Template |Title=VOCamp in Paris - #vocampparis2010 |Description=The company Hypios organizes a [...

{{NewsInfo
|SubmittedBy=FrancoisScharffe
|PostedOn=2010-04-6T13:13:28
}}
{{TitleDescription Template
|Title=VOCamp in Paris - #vocampparis2010
|Description=The company Hypios organizes a [http://vocamp.org/wiki/HypiosVoCampParisMay2010 VOCamp in Paris] next 13th and 14th of May. The ODP community will be represented and we hope to see a few nicely designed vocabularies to emerge from this event !
}}

Submissions:Class correspondence defined by relation domain

2010-03-04T09:15:42Z

FrancoisScharffe: New page: {{Alignment_OP_Proposal_toolbar}} {{Graphical representation header}} {{Graphical representation |ImageName=Class-by-relation-domain.png }} {{Alignment OP General Template |Name=Class corr...

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Class-by-relation-domain.png
}}
{{Alignment OP General Template
|Name=Class correspondence defined by relation domain
|SubmittedBy=FrancoisScharffe,
|AlsoKnownAs=Subclass correspondence defined by relation domain
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class in one ontology is equivalent to the subclass of a class in a second ontology of exactly those instances which are in the domain of a specified relation.

|Solution=This pattern establishes a correspondence between a class and relation in one ontology and a class in another

}}
{{Alignment OP Example Template
|Solution=

<Cell>
<entity1>
<Class rdf:about="o1:Parent"/>
</entity1>
<entity2>
<Class>
<and>
<Class rdf:about="o2:Animal">
</and>
<and>
<AttributeOccurenceCondition>
<onAttribute>
<Relation rdf:about="o2:children"/>
</onAttribute>
<AttributeOccurenceCondition>
</and>
</Class>
</entity2>
<relation>subsumption</relation>
</Cell>

}}
{{Alignment OP References Template
|RelatedTo=Class by Attribute Occurence Correspondence
}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

'Ontology Design Patterns':Partners

2010-03-04T08:41:47Z

FrancoisScharffe:

[[Image:Partners.jpg|70px]]

The following institutions contribute to the portal site editorial work.

{| border="0" style="background:transparent;"
|-
|
[[Image:EcoleCentraleLogo.gif|100px|left|thumb|Ecole Centrale Paris]] [http://www.ecp.fr/ ECP]
||
[[Image:koblenzLogo.jpeg|100px|left|thumb| ISWeb Research Group - University of Koblenz-Landau]] [http://isweb.uni-koblenz.de/ ISWeb]
||
[[Image:SalzburgLogo.png|100px|left|thumb| Salzburg Research]] [http://www.salzburgresearch.at/company/index.php Salzburg Research]
||
[[Image:VSElogo.png|100px|left|thumb| Vysoka Skola Ekonomicka Prague]] [http://www.vse.cz/index-en.php VSE]
||
[[Image:Stlab_B.png|100px|left|thumb| Semantic Technology Laboratory ISTC-CNR]] [http://stlab.istc.cnr.it STLab]
||
[[Image:kmiLogo.png|100px|left|thumb| Knowledge Media Institute - UK Open University]] [http://kmi.open.ac.uk/ KMI]
||
[[Image:OEGLogo.png|100px|left|thumb| Ontology Engineering Group - Universidad Politécnica de Madrid]] [http://www.oeg-upm.net/ OEG]
||
[[Image:ManchesterLogo.png|100px|left|thumb| The University of Manchester]] [http://www.manchester.ac.uk/ Manchester Univ]
|-
|
[[Image:Exmo-medium.gif|100px|left|thumb| EXMO team, French Research Institute in Computer Science and Control]] [http://www.inrialpes.fr/exmo/ INRIA EXMO]
|}

File:Exmo-medium.gif

2010-03-04T08:41:24Z

FrancoisScharffe:

'Ontology Design Patterns':Partners

2010-03-04T08:40:43Z

FrancoisScharffe:

[[Image:Partners.jpg|70px]]

The following institutions contribute to the portal site editorial work.

{| border="0" style="background:transparent;"
|-
|
[[Image:EcoleCentraleLogo.gif|100px|left|thumb|Ecole Centrale Paris]] [http://www.ecp.fr/ ECP]
||
[[Image:koblenzLogo.jpeg|100px|left|thumb| ISWeb Research Group - University of Koblenz-Landau]] [http://isweb.uni-koblenz.de/ ISWeb]
||
[[Image:SalzburgLogo.png|100px|left|thumb| Salzburg Research]] [http://www.salzburgresearch.at/company/index.php Salzburg Research]
||
[[Image:VSElogo.png|100px|left|thumb| Vysoka Skola Ekonomicka Prague]] [http://www.vse.cz/index-en.php VSE]
||
[[Image:Stlab_B.png|100px|left|thumb| Semantic Technology Laboratory ISTC-CNR]] [http://stlab.istc.cnr.it STLab]
||
[[Image:kmiLogo.png|100px|left|thumb| Knowledge Media Institute - UK Open University]] [http://kmi.open.ac.uk/ KMI]
||
[[Image:OEGLogo.png|100px|left|thumb| Ontology Engineering Group - Universidad Politécnica de Madrid]] [http://www.oeg-upm.net/ OEG]
||
[[Image:ManchesterLogo.png|100px|left|thumb| The University of Manchester]] [http://www.manchester.ac.uk/ Manchester Univ]
|-
|
[[Image:EXMO-medium.gif|100px|left|thumb| EXMO team, French Research Institute in Computer Science and Control]] [http://www.inrialpes.fr/exmo/ INRIA EXMO]
|}

'Ontology Design Patterns':Partners

2010-03-04T08:37:33Z

FrancoisScharffe:

[[Image:Partners.jpg|70px]]

The following institutions contribute to the portal site editorial work.

{| border="0" style="background:transparent;"
|-
|
[[Image:EcoleCentraleLogo.gif|100px|left|thumb|Ecole Centrale Paris]] [http://www.ecp.fr/ ECP]
||
[[Image:koblenzLogo.jpeg|100px|left|thumb| ISWeb Research Group - University of Koblenz-Landau]] [http://isweb.uni-koblenz.de/ ISWeb]
||
[[Image:SalzburgLogo.png|100px|left|thumb| Salzburg Research]] [http://www.salzburgresearch.at/company/index.php Salzburg Research]
||
[[Image:VSElogo.png|100px|left|thumb| Vysoka Skola Ekonomicka Prague]] [http://www.vse.cz/index-en.php VSE]
||
[[Image:Stlab_B.png|100px|left|thumb| Semantic Technology Laboratory ISTC-CNR]] [http://stlab.istc.cnr.it STLab]
||
[[Image:kmiLogo.png|100px|left|thumb| Knowledge Media Institute - UK Open University]] [http://kmi.open.ac.uk/ KMI]
||
[[Image:OEGLogo.png|100px|left|thumb| Ontology Engineering Group - Universidad Politécnica de Madrid]] [http://www.oeg-upm.net/ OEG]
||
[[Image:ManchesterLogo.png|100px|left|thumb| The University of Manchester]] [http://www.manchester.ac.uk/ Manchester Univ]
|-
|
[[Image:INRIA.gif|100px|left|thumb| French Research Institute in Computer Science and Control]] [http://www.inria.fr INRIA]
|}

File:INRIA.gif

2010-03-04T08:37:09Z

FrancoisScharffe:

'Ontology Design Patterns':Partners

2010-03-04T08:33:44Z

FrancoisScharffe:

[[Image:Partners.jpg|70px]]

The following institutions contribute to the portal site editorial work.

{| border="0" style="background:transparent;"
|-
|
[[Image:EcoleCentraleLogo.gif|100px|left|thumb|Ecole Centrale Paris]] [http://www.ecp.fr/ ECP]
||
[[Image:koblenzLogo.jpeg|100px|left|thumb| ISWeb Research Group - University of Koblenz-Landau]] [http://isweb.uni-koblenz.de/ ISWeb]
||
[[Image:SalzburgLogo.png|100px|left|thumb| Salzburg Research]] [http://www.salzburgresearch.at/company/index.php Salzburg Research]
||
[[Image:VSElogo.png|100px|left|thumb| Vysoka Skola Ekonomicka Prague]] [http://www.vse.cz/index-en.php VSE]
||
[[Image:Stlab_B.png|100px|left|thumb| Semantic Technology Laboratory ISTC-CNR]] [http://stlab.istc.cnr.it STLab]
||
[[Image:kmiLogo.png|100px|left|thumb| Knowledge Media Institute - UK Open University]] [http://kmi.open.ac.uk/ KMI]
||
[[Image:OEGLogo.png|100px|left|thumb| Ontology Engineering Group - Universidad Politécnica de Madrid]] [http://www.oeg-upm.net/ OEG]
||
[[Image:ManchesterLogo.png|100px|left|thumb| The University of Manchester]] [http://www.manchester.ac.uk/ Manchester Univ]
|-
|
[[Image:INRIA.png|100px|left|thumb| French Research Institute in Computer Science and Control]] [http://www.inria.fr INRIA]
|}

'Ontology Design Patterns':Partners

2010-03-04T08:32:59Z

FrancoisScharffe:

[[Image:Partners.jpg|70px]]

The following institutions contribute to the portal site editorial work.

{| border="0" style="background:transparent;"
|-
|
[[Image:EcoleCentraleLogo.gif|100px|left|thumb|Ecole Centrale Paris]] [http://www.ecp.fr/ ECP]
||
[[Image:koblenzLogo.jpeg|100px|left|thumb| ISWeb Research Group - University of Koblenz-Landau]] [http://isweb.uni-koblenz.de/ ISWeb]
||
[[Image:SalzburgLogo.png|100px|left|thumb| Salzburg Research]] [http://www.salzburgresearch.at/company/index.php Salzburg Research]
||
[[Image:VSElogo.png|100px|left|thumb| Vysoka Skola Ekonomicka Prague]] [http://www.vse.cz/index-en.php VSE]
||
[[Image:Stlab_B.png|100px|left|thumb| Semantic Technology Laboratory ISTC-CNR]] [http://stlab.istc.cnr.it STLab]
||
[[Image:kmiLogo.png|100px|left|thumb| Knowledge Media Institute - UK Open University]] [http://kmi.open.ac.uk/ KMI]
||
[[Image:OEGLogo.png|100px|left|thumb| Ontology Engineering Group - Universidad Politécnica de Madrid]] [http://www.oeg-upm.net/ OEG]
||
[[Image:ManchesterLogo.png|100px|left|thumb| The University of Manchester]] [http://www.manchester.ac.uk/ Manchester Univ]
||
[[Image:INRIA.png|100px|left|thumb| French Research Institute in Computer Science and Control]] [http://www.inria.fr INRIA]
|}

Submissions:Class by attribute type

2010-03-03T16:19:37Z

FrancoisScharffe: New page: {{Alignment_OP_Proposal_toolbar}} {{Graphical representation header}} {{Graphical representation |ImageName=Class-by-attribute-type.png }} {{Alignment OP General Template |Name=Class by at...

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Class-by-attribute-type.png
}}
{{Alignment OP General Template
|Name=Class by attribute type
|SubmittedBy=FrancoisScharffe
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Problem=A class in one ontology is aligned to a class in the other ontology. However, only those instances for which an attribute value corresponding to a certain type (subclass of the attribute range) is given are aligned.

|Solution=This pattern establishes a mapping between a class/attribute combination in one
ontology and a class in another. In many cases this pattern will be used many times to fully cover the range of the attribute over various classes of the other ontology.

}}
{{Alignment OP Example Template
|Solution=

<Cell>
<entity1>
<Class>
<and>
<Class rdf:about="o1:Human"/>
</and>
<and>
<AttributeTypeCondition>
<onAttribute>
<Relation rdf:about="o1:culturalGroup"/>
</onAttribute>
<value><Instance rdf:about="o1:WesternEurope"></value>
</AttributeTypeCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2:WesternEuropean"/>
</entity2>
</Cell>

}}
{{Alignment OP References Template}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class by attribute occurence

2010-03-03T15:57:56Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Class-by-attribute-occurence.png
}}
{{Alignment OP General Template
|Name=Class by attribute occurence
|SubmittedBy=FrancoisScharffe
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class in one ontology is aligned to a class in the other ontology. However, only those instances for which a value is given to particular attribute are aligned. This pattern is agnostic as to whether the correspondence is unidirectional or bidirectional, direction of the correspondence can be achieved through combination of the pattern with the equivalentClassCorrespondence or subClassCorrespondence
pattern.
|Solution=This pattern establishes a mapping between a class/attribute combination in one
ontology and a class in another.
}}
{{Alignment OP Example Template
|Solution=<Cell>
<entity1>
<Class>
<and>
<Class rdf:about="o1:Human">
</and>
<and>
<AttributeOccurenceCondition>
<onAttribute>
<Property rdf:about="o1:hasMedal"/>
</onAttribute>
</AttributeOccurenceCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2:Champion"/>
</entity2>
</Cell>
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence, Class subsumption
}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class equivalence

2010-03-03T15:48:24Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=class-equivalence.png
}}
{{Alignment OP General Template
|Name=Class equivalence
|SubmittedBy=FrancoisScharffe
|AlsoKnownAs=Equivalent classes
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Problem=Two classes in two ontologies have the same intension.
|Solution=The pattern relates the two classes by specifying them as being equivalent.
}}
{{Alignment OP Example Template
|Scenario=Human vs Person
|Solution=Example solution in the ontology alignment language:
<Cell>
<entity1><Class rdf:about="O1:Human"/></entity1>
<entity2><Class rdf:about="O2:Person"/></entity2>
<relation>equivalence</relation>
</Cell>
|Consequences=The equivalent classed are related by an equivalence correspondence.
}}
{{Alignment OP References Template
|KnownUse=This is a very common correspondence.
|RelatedTo=Lexico Syntactic ODP corresponding to Equivalence relation between Classes ODP, SynonymOrEquivalence (SOE)
}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class equivalence

2010-03-03T15:47:54Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=class-equivalence.png
}}
{{Alignment OP General Template
|Name=Class equivalence
|SubmittedBy=FrancoisScharffe
|AlsoKnownAs=Equivalent classes
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Problem=Two classes in two ontologies have the same intension.
|Solution=The pattern relates the two classes by specifying them as being equivalent.
}}
{{Alignment OP Example Template
|Scenario=Human vs Person
|Solution=Example solution in the ontology alignment language:
<Cell>
<entity1><Class rdf:about="O1:Human"/></entity1>
<entity2><Class rdf:about="O2:Person"/></entity2>
<relation>equivalence</relation>
</Cell>
|Consequences=The equivalent classed are related by an equivalence correspondence.
}}
{{Alignment OP References Template
|KnownUse=This is a very common correspondence.
|RelatedTo=Lexico Syntactic ODP corresponding to Equivalence relation between Classes ODP, SynonymOrEquivalence
}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class equivalence

2010-03-03T15:47:23Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=class-equivalence.png
}}
{{Alignment OP General Template
|Name=Class equivalence
|SubmittedBy=FrancoisScharffe
|AlsoKnownAs=Equivalent classes
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Problem=Two classes in two ontologies have the same intension.
|Solution=The pattern relates the two classes by specifying them as being equivalent.
}}
{{Alignment OP Example Template
|Scenario=Human vs Person
|Solution=Example solution in the ontology alignment language:
<Cell>
<entity1><Class rdf:about="O1:Human"/></entity1>
<entity2><Class rdf:about="O2:Person"/></entity2>
<relation>equivalence</relation>
</Cell>
|Consequences=The equivalent classed are related by an equivalence correspondence.
}}
{{Alignment OP References Template
|KnownUse=This is a very common correspondence.
|RelatedTo=Lexico Syntactic ODP corresponding to Equivalence relation between Classes ODP, Submissions:SynonymOrEquivalence
}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class equivalence

2010-03-03T15:46:54Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=class-equivalence.png
}}
{{Alignment OP General Template
|Name=Class equivalence
|SubmittedBy=FrancoisScharffe
|AlsoKnownAs=Equivalent classes
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Problem=Two classes in two ontologies have the same intension.
|Solution=The pattern relates the two classes by specifying them as being equivalent.
}}
{{Alignment OP Example Template
|Scenario=Human vs Person
|Solution=Example solution in the ontology alignment language:
<Cell>
<entity1><Class rdf:about="O1:Human"/></entity1>
<entity2><Class rdf:about="O2:Person"/></entity2>
<relation>equivalence</relation>
</Cell>
|Consequences=The equivalent classed are related by an equivalence correspondence.
}}
{{Alignment OP References Template
|KnownUse=This is a very common correspondence.
|RelatedTo=Lexico Syntactic ODP corresponding to Equivalence relation between Classes ODP, Submissions:SynonymOrEquivalence_SOE
}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class equivalence

2010-03-03T15:44:56Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=class-equivalence.png
}}
{{Alignment OP General Template
|Name=Class equivalence
|SubmittedBy=FrancoisScharffe
|AlsoKnownAs=Equivalent classes
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Problem=Two classes in two ontologies have the same intension.
|Solution=The pattern relates the two classes by specifying them as being equivalent.
}}
{{Alignment OP Example Template
|Scenario=Human vs Person
|Solution=Example solution in the ontology alignment language:
<Cell>
<entity1><Class rdf:about="O1:Human"/></entity1>
<entity2><Class rdf:about="O2:Person"/></entity2>
<relation>equivalence</relation>
</Cell>
|Consequences=The equivalent classed are related by an equivalence correspondence.
}}
{{Alignment OP References Template
|KnownUse=This is a very common correspondence.
|RelatedTo=Lexico Syntactic ODP corresponding to Equivalence relation between Classes ODP
}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class by attribute occurence

2010-03-03T15:35:45Z

FrancoisScharffe: New page: {{Alignment_OP_Proposal_toolbar}} {{Graphical representation header}} {{Graphical representation |ImageName=Class-by-path-attribute-occurence.png }} {{Alignment OP General Template |Name=C...

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Class-by-path-attribute-occurence.png
}}
{{Alignment OP General Template
|Name=Class by attribute occurence
|SubmittedBy=FrancoisScharffe
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class in one ontology is aligned to a class in the other ontology. However, only those instances for which a value is given to particular attribute are aligned. This pattern is agnostic as to whether the correspondence is unidirectional or bidirectional, direction of the correspondence can be achieved through combination of the pattern with the equivalentClassCorrespondence or subClassCorrespondence
pattern.

|Solution=This pattern establishes a mapping between a class/attribute combination in one
ontology and a class in another.
}}
{{Alignment OP Example Template
|Solution=
<Cell>
<entity1>
<Class>
<and>
<Class rdf:about="o1:Human">
</and>
<and>
<AttributeOccurenceCondition>
<onAttribute>
<Property rdf:about="o1:hasMedal"/>
</onAttribute>
</AttributeOccurenceCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2:Champion"/>
</entity2>
</Cell>
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence, Class subsumption
}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class by path attribute value

2010-03-03T12:56:59Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Class-by-path-attribute-value.png
}}
{{Alignment OP General Template
|Name=Class by path attribute value
|SubmittedBy=FrancoisScharffe
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class in one ontology is aligned to a class in another ontology and the criteria
for membership in the class are specified by an attribute value at the end of a path.
|Solution=The two classes in two ontologies are provided along with a statement involving
either one class or both classes. This statement is a precondition for the correspondence. This pattern is agnostic to whether the correspondence is unidirectional or bidirectional. However, if the correspondence is bidirectional (equivalence relation), the same precondition applies for both directions.
}}
{{Alignment OP Example Template
|Scenario=A Commuter concept in one ontology is related to a Person concept in another ontology if and only if the person home city is different with the person working place city
|Solution=Example correspondence:

<Cell>
<entity1>
<Class>
<and>
<Class rdf:about="o1 :Person"/>
<AttributeValueCondition>
<onAttribute>
<Property>
<first>
<Relation rdf:about="o1 :workplace"/>
</first>
<next>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/></next>
</next>
</Property>
</next>
</Property>
</onAttribute>
<comparator rdf:resource="xsd:not-equal"/>
<value>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/>
</next>
</Property>
</value>
</AttributeValueCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2 :Commuter">
</entity2>
</Cell>
}}
{{Alignment OP References Template}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class by path attribute value

2010-03-03T12:55:24Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Class-by-path-attribute-value.png
}}
{{Alignment OP General Template
|Name=Class by path attribute value
|SubmittedBy=FrancoisScharffe
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class in one ontology is aligned to a class in another ontology and the criteria
for membership in the class are specified by an attribute value at the end of a path.
|Solution=The two classes in two ontologies are provided along with a statement involving
either one class or both classes. This statement is a precondition for the correspondence. This pattern is agnostic to whether the correspondence is unidirectional or bidirectional. However, if the correspondence is bidirectional (equivalence relation), the same precondition applies for both directions.
}}
{{Alignment OP Example Template
|Solution=Example correspondence:

<Cell>
<entity1>
<Class>
<and>
<Class rdf:about="o1 :Person"/>
<AttributeValueCondition>
<onAttribute>
<Property>
<first>
<Relation rdf:about="o1 :workplace"/>
</first>
<next>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/></next>
</next>
</Property>
</next>
</Property>
</onAttribute>
<comparator rdf:resource="xsd:not-equal"/>
<value>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/>
</next>
</Property>
</value>
</AttributeValueCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2 :Commuter">
</entity2>
</Cell>
}}
{{Alignment OP References Template}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class by path attribute value

2010-03-03T12:54:59Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=Class-by-path-attribute-value.png
}}
{{Alignment OP General Template
|Name=Class by path attribute value
|SubmittedBy=FrancoisScharffe
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class in one ontology is aligned to a class in another ontology and the criteria
for membership in the class are specified by an attribute value at the end of a path.
|Solution=The two classes in two ontologies are provided along with a statement involving
either one class or both classes. This statement is a precondition for the correspondence. This pattern is agnostic to whether the correspondence is unidirectional or bidirectional. However, if the correspondence is bidirectional (equivalence relation), the same precondition applies for both directions.
}}
{{Alignment OP Example Template
|Solution=Example correspondence:

<Cell>
<entity1>
<Class>
<and>
<Class rdf:about="o1 :Person"/>
<AttributeValueCondition>
<onAttribute>
<Property>
<first>
<Relation rdf:about="o1 :workplace"/>
</first>
<next>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/></next>
</next>
</Property>
</next>
</Property>
</onAttribute>
<comparator rdf:resource="xsd:not-equal"/>
<value>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/>
</next>
</Property>
</value>
</AttributeValueCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2 :Commuter">
</entity2>
</Cell>
}}
{{Alignment OP References Template}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}

Submissions:Class by path attribute value

2010-03-03T12:54:00Z

FrancoisScharffe: New page: {{Alignment_OP_Proposal_toolbar}} {{Graphical representation |ImageName=Class-by-path-attribute-value.png }} {{Alignment OP General Template |Name=Class by path attribute value |SubmittedB...

{{Alignment_OP_Proposal_toolbar}}
{{Graphical representation
|ImageName=Class-by-path-attribute-value.png
}}
{{Alignment OP General Template
|Name=Class by path attribute value
|SubmittedBy=FrancoisScharffe
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class in one ontology is aligned to a class in another ontology and the criteria
for membership in the class are specified by an attribute value at the end of a path.
|Solution=The two classes in two ontologies are provided along with a statement involving
either one class or both classes. This statement is a precondition for the correspondence. This pattern is agnostic to whether the correspondence is unidirectional or bidirectional. However, if the correspondence is bidirectional (equivalence relation), the same precondition applies for both directions.

}}
{{Alignment OP Example Template
|Solution=
<Cell>
<entity1>
<Class>
<and>
<Class rdf:about="o1 :Person"/>
<AttributeValueCondition>
<onAttribute>
<Property>
<first>
<Relation rdf:about="o1 :workplace"/>
</first>
<next>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/></next>
</next>
</Property>
</next>
</Property>
</onAttribute>
<comparator rdf:resource="xsd:not-equal"/>
<value>
<Property>
<first>
<Relation rdf:about="o1 :address"/>
</first>
<next>
<Property rdf:about="o1 :city"/>
</next>
</Property>
</value>
</AttributeValueCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2 :Commuter">
</entity2>
</Cell>
}}
{{Alignment OP References Template}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}

Ontology:Music Ontology

2010-02-17T07:27:59Z

FrancoisScharffe:

{{Ontology
|Name=Music Ontology
|OntologyAuthor=Yeves Raimond, Frederick Giasson
|Description=The Music Ontology Specification provides main concepts and properties for describing music (i.e. artists, albums, tracks, but also performances, arrangements, etc.) on the Semantic Web.
|SubmittedBy=FrancoisScharffe
|OntologyPurpose=Describing music
|OWLImplementation=http://www.musicontology.com/
|Justification=Had many revisions, is widely used (see the linked data cloud).
|RecommendedBy=François Scharffe
}}

Ontology:Music Ontology

2010-02-17T07:27:06Z

FrancoisScharffe: New page: {{Ontology |Name=Music Ontology |OntologyAuthor=Yeves Raimond, Frederick Giasson |Description=The Music Ontology Specification provides main concepts and properties for describing music (i...

{{Ontology
|Name=Music Ontology
|OntologyAuthor=Yeves Raimond, Frederick Giasson
|Description=The Music Ontology Specification provides main concepts and properties for describing music (i.e. artists, albums, tracks, but also performances, arrangements, etc.) on the Semantic Web. This document contains a detailed description of the Music Ontology.
|SubmittedBy=FrancoisScharffe
|OntologyPurpose=Describing music
|OWLImplementation=http://www.musicontology.com/
|Justification=Had many revisions, is widely used (see the linked data cloud).
|RecommendedBy=François Scharffe
|Domain=Music
}}

Training:PhD Course on Computational Ontologies @ University of Bologna/PhD Course on Computational Ontologies @ University of Bologna/Hands-on (Day6): ontology alignment tutorial

2010-02-09T10:17:14Z

FrancoisScharffe: New page: {{Exercise Description Template |Tutorial=PhD Course on Computational Ontologies @ University of Bologna |Title=PhD Course on Computational Ontologies @ University of Bologna/Hands-on (Day...

{{Exercise Description Template
|Tutorial=PhD Course on Computational Ontologies @ University of Bologna
|Title=PhD Course on Computational Ontologies @ University of Bologna/Hands-on (Day6): ontology alignment tutorial
|Problem=Two ontologies describing the same domain need to be aligned.

We will learn to use the alignment API:
http://alignapi.gforge.inria.fr/tutorial/
}}

Training:PhD Course on Computational Ontologies @ University of Bologna 2010

2010-02-05T09:58:37Z

FrancoisScharffe:

{{Tutorial Template
|Title=PhD Course on Computational Ontologies @ University of Bologna
|Author=AldoGangemi, ValentinaPresutti, EvaBlomqvist, FrancoisScharffe
|Goal=The course aims at providing attendees with a good understanding of state-of-the-art techniques for ontology design, with special focus on the semantic web context. The course targets PhD students in Computer Science, Information Technology, Computer Engineering, Mathematics, Logics, Philosophy, Computational
Linguistics, and other disciplines that employ, or might consider to
employ, techniques and theories connected to semantic
technologies, with particular focus on Semantic Web technologies. It also targets
Master students in the above mentioned disciplines who are doing
a master thesis, or plan to enroll in a PhD program, on these subjects.
|Description=Course content includes: Introduction to semantic technologies, Semantic Web, and computational ontologies.
Semantic Web languages such as RDF, OWL, and SPARQL.
Tools for ontology editing.
Methodologies for, and principles of ontology design.
Definition of ontology design pattern (ODP) and theoretical foundation.
Types of ODP and detailed analysis of Logical, Correspondence, and Content ODPs.
Overview of XD and analogy with eXtreme Programming (XP).
Ontology requirements and competency questions.
Defining unit tests for ontologies.
Matching requirements with ODPs and ODP selection.
ODP specialization and composition.
Collaboration and Integration issues.
The XD tool.
}}
{{Tutorial resources begin}}
{{External Resource Template
|Location=http://stlab.istc.cnr.it/documents/PhDCourse/Bologna2010/Introduction.pdf
}}
{{External Resource Template
|Location=http://stlab.istc.cnr.it/documents/PhDCourse/Bologna2010/ODPs.pdf
}}
{{External Resource Template
|Location=http://www.scharffe.fr/presentations/PhD%20seminar%20Bologna%20-%2002.2010.pdf
}}
{{Tutorial exercises}}
== Venue ==

* [http://www.cs.unibo.it Dipartimento di Scienze dell'Informazione - Università di Bologna]
* [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=mura+anteo+zamboni+7+bologna&vps=1&jsv=202c&sll=44.497454,11.356301&sspn=0.008005,0.018926&num=10&abstate=A Mura Anteo Zamboni 7, Bologna]

== Tutors ==

* [http://stlab.istc.cnr.it/User:AldoGangemi Aldo Gangemi]
* [http://stlab.istc.cnr.it/User:ValentinaPresutti Valentina Presutti]
* [http://stlab.istc.cnr.it/User:EvaBlomvist Eva Blomqvist]
* [http://www.scharffe.fr/ Francois Scharffe]

== Detailed Program ==

The course is divided into the following modules that include both lectures and hands-on sessions.

=== Module 1: Semantic Technologies and Computational ontologies ===

* Introduction to semantic technologies, Semantic Web and computational ontologies.
* Semantic Web languages such as RDF, OWL, and SPARQL.
* Tools for ontology editing.
* Methodologies for, and principles of ontology design.

=== Module 2: Ontology design patterns ===

* Definition of ontology design pattern (ODP) and theoretical foundation.
* Types of ODP and detailed analysis of Logical, Correspondence, and Content ODPs.

=== Module 3: eXtreme Design (XD): ODP-based Methodology for ontology design===

* Overview of XD and analogy with eXtreme Programming (XP).
* Ontology requirements and competency questions.
* Defining unit tests for ontologies.
* Matching requirements with ODPs and ODP selection.
* ODP specialization and composition.
* Collaboration and Integration issues.
* The XD tool.

=== Module 4: Project {Students’ Evaluation} ===

Students will be evaluated through a project assignment, that will be developed collaboratively and on-site, the last day of the course in a 8 hours session. They will apply the notions and experiences acquired during the course to a realistic scenario. The students will be organized as an ontology developing team according to the XD methodology. The team will be assigned with a set of requirements and will have to collaboratively develop an ontology based on those requirements. The tutors will act as customers and will advise the team on methodological issues.
The aim of the project is on one hand to evaluate the single students for the sake of the PhD curriculum, on the other hand to make them experience a realistic scenario, and further discuss open problems in the area.

== Schedule ==

{| border="1"
| February 2nd || 09:00-13:00 || [[Training:PhD_Course_on_Computational_Ontologies_%40_University_of_Bologna#Module_1:_Semantic_Technologies_and_Computational_ontologies | Module 1]] || Sala Riunioni 1
|-
| February 3rd || 09:00-13:00 || [[Training:PhD_Course_on_Computational_Ontologies_%40_University_of_Bologna#Module_1:_Semantic_Technologies_and_Computational_ontologies | Module 1]] (II part) || Sala Riunioni 2
|-
| February 4th || 09:00-18:30 || [[Training:PhD_Course_on_Computational_Ontologies_%40_University_of_Bologna#Module_2:_Ontology_design_patterns | Module 2]] || Sala Riunioni 1
|-
| February 5th || 09:00-13:00 || [[Training:PhD_Course_on_Computational_Ontologies_%40_University_of_Bologna#Module_2:_Ontology_design_patterns | Module 2]] (II part) || Sala Riunioni 2
|-
| February 8th || 09:30-18:30 || [[Training:PhD_Course_on_Computational_Ontologies_%40_University_of_Bologna#Module_3:_eXtreme_Design_.28XD.29:_ODP-based_Methodology_for_ontology_design | Module 3]] || Sala Riunioni 2
|-
| February 9th || 09:00-13:00 || [[Training:PhD_Course_on_Computational_Ontologies_%40_University_of_Bologna#Module_2:_Ontology_design_patterns | Module 2]] (III part) || Sala Riunioni 2
|-
| February 10th || 09:00-18:30 || [[Training:PhD_Course_on_Computational_Ontologies_%40_University_of_Bologna#Module_4:_Project_.7BStudents.E2.80.99_Evaluation.7D | Module 4]] (evaluation) || Sala Riunioni 1
|}

== Application ==

Applications must be submitted by email to vpresutti@gmail.com before
January 25th 2010. Applicants must include a short CV.
Registration is free, since the course is sponsored by the EU FP6
project [http://www.neon-project.eu NeOn] in collaboration with the [http://www.cs.unibo.it Dipartimento di Scienze dell'Informazione of the University of Bologna]. Participants are expected to attend all the classes of the course in order to earn the credit for the PhD CV.
The course will be held at the Dipartimento of Scienze dell’Informazione of the University of Bologna.
For details regarding, traveling, hotels, logistic information and any
further information, please email to vpresutti@gmail.

== Tutors' CV ==

'''[http://stlab.istc.cnr.it/User:AldoGangemi Aldo Gangemi]''' is a Senior Researcher at, and scientific coordinator of the [http://stlab.istc.cnr.it Semantic Technology Laboratory] of the [http://www.istc.cnr.it Institute for Cognitive Sciences and Technology] at the [http://www.cnr.it Italian National Research Council]. He is co-founder of the [http://www.loa-cnr.it Laboratory for Applied Ontology], leading research units in the areas of conceptual modeling, formal ontology, and ontology engineering and of the [http://stlab.istc.cnr.it Semantic Technology Laboratory], leading research unit in the areas of semantic web technologies, ontology engineering, and natural language processing. His research topics include knowledge engineering, the semantic web, NLP, and business modeling, with about 100 publications on international refereed journals, books and conferences. He has been working in many national and EU projects, spanning from the pioneering biomedical ontology project GALEN (1992) to the current largest ontology engineering projects [http://www.neon-project.com NeOn] and [http://www.iks-project.org IKS].
He is currently coordinating the workpackage on collaborative aspects of ontology design in NeOn, and an Italian project on the use of semantic technologies in organizational intranets. He is reviewer for the EU and Italian governmental agencies, and consultant for Italian and international organizations.

'''[http://stlab.istc.cnr/User:ValentinaPresutti Valentina Presutti]''' is a Researcher at the [http://stlab.istc.cnr.it Semantic Technology Laboratory] of the [http://stlab.istc.cnr.it Semantic Technology Laboratory] of the [http://www.istc.cnr.it Institute for Cognitive Sciences and Technology] at the [http://www.cnr.it Italian National Research Council]. She received her Ph.D. in computer science at the [http://www.cs.unibo.it University of Bologna]. Her research interests include ontology design good practices, ontology-driven software engineering, Semantic Wikis and CMS. She is currently one of the key researchers of the EU projects [http://www.neon-project.com NeOn] and [http://www.iks-project.org IKS].

'''[http://stlab.istc.cnr/User:EvaBlomqvist Eva Blomqvist]''' is a Researcher at the [http://stlab.istc.cnr.it Semantic Technology Laboratory] of the [http://stlab.istc.cnr.it Semantic Technology Laboratory] of the [http://www.istc.cnr.it Institute for Cognitive Sciences and Technology] at the [http://www.cnr.it Italian National Research Council]. She obtained her Ph.D at Linköping University. Her researcher interests focus on the Semantic Web and its applications in the business world. Specific areas include semi-automatic ontology engineering (Ontology Learning) and methods to determine semantic similairty. She is currently one of the key researchers of the EU projects [http://www.neon-project.com NeOn] and [http://www.iks-project.org IKS].

'''[http://www.scharffe.fr/ François Scharffe]''' is a Researcher at the [http://www.inria.fr/index.en.html French Institute for Research in Computer Science and Control (INRIA)], Grenoble (FR). He holds a PhD focused on ontology alignment representation obtained at the University of Innsbruck, Austria. He was involved in the Semantic Enabled Knowledge Technologies (SEKT) project and a member of the Knowledge Web network of excellence where he extensively worked on ontology mediation. He published several articles around ontology mediation and is an author of two book chapters on the topic. His latest research brought him to study the application of semantic integration techniques to the problem of cultural archives integration as part of the EASAIER project. He is currently working on a system for Web data integration.

Submissions:Class by attribute value

2010-02-02T16:44:56Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=class-by-attribute-value.png
}}
{{Alignment OP General Template
|Name=Class by attribute value
|SubmittedBy=FrancoisScharffe
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Problem=A class in one ontology is equivalent to the subclass of an ontology in a second
ontology of exactly those instances which have a specified property value.
|Solution=This pattern establishes a mapping between a class/property/property-value combination in one ontology and a class in another. This pattern is agnostic as to whether the mapping is unidirectional or bidirectional direction of the mapping can be achieved through combination of the pattern with the equivalent classes or class subsumption correspondence patterns.
|Workflow=The scope of a class in one ontology is narrower than the scope of a class
in the other ontology. Both scopes can be matched by restricting one class to those instances having a particular value for a certain property.
}}
{{Alignment OP Example Template
|Solution=Example in EDOAL:
<Cell>
<entity1>
<Class>
<and>
<Class rdf:about="vin:Vin">
</and>
<and>
<AttributeValueCondition>
<onAttribute>
<Property rdf:about="vin:terroir"/>
</onAttribute>
<comparator>xsd:Equal</comparator>
<value>geo:Bordelais</value>
</AttributeValueCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="wine:BordeauxWine"/>
</entity2>
</Cell>
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence, Class subsumption,
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Class by attribute value

2010-02-02T16:44:21Z

FrancoisScharffe: initial submission

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=class-by-attribute-value.png
}}
{{Alignment OP General Template
|Name=Class by attribute value
|SubmittedBy=FrancoisScharffe
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Problem=A class in one ontology is equivalent to the subclass of an ontology in a second
ontology of exactly those instances which have a specified property value.
|Solution=This pattern establishes a mapping between a class/property/property-value combination in one ontology and a class in another. This pattern is agnostic as to whether the mapping is unidirectional or bidirectional direction of the mapping can be achieved through combination of the pattern with the equivalent classes or class subsumption correspondence patterns.
|Workflow=The scope of a class in one ontology is narrower than the scope of a class
in the other ontology. Both scopes can be matched by restricting one class to those instances having a particular value for a certain property.
}}
{{Alignment OP Example Template
|Solution= <Cell>
<entity1>
<Class>
<and>
<Class rdf:about="vin:Vin">
</and>
<and>
<AttributeValueCondition>
<onAttribute>
<Property rdf:about="vin:terroir"/>
</onAttribute>
<comparator>xsd:Equal</comparator>
<value>geo:Bordelais</value>
</AttributeValueCondition>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="wine:BordeauxWine"/>
</entity2>
</Cell>
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence, Class subsumption,
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Disjoint Classes

2010-02-01T15:27:38Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=disjoint-classes-correspondences.png
}}
{{Alignment OP General Template
|Name=Disjoint Classes
|SubmittedBy=FrancoisScharffe
|AlsoKnownAs=Class disjointness
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=Two classes have a different intension, and no intersection of their extension.
Specifying a disjoint correspondence may help a matcher in not proposing any correspondences between these classes.
|Solution=This pattern establishes correspondence stating that classes are disjoint.
}}
{{Alignment OP Example Template
|Solution=Example in EDOAL, the expressive and declarative ontology alignment language
<Cell>
<entity1><Class rdf:about="O1:Top"/></entity1>
<entity2><Class rdf:about="O2:Top"/></entity2>
<relation>Disjoint</relation>
</Cell>
}}
{{Alignment OP References Template
|RelatedTo=DisjointAttributes, DisjointInstances
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Disjoint Classes

2010-02-01T15:21:44Z

FrancoisScharffe: initial submission

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=disjoint-classes.png
}}
{{Alignment OP General Template
|Name=Disjoint Classes
|SubmittedBy=FrancoisScharffe
|AlsoKnownAs=Class disjointness
|Author=Francois Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=Two classes have a different intension, and no intersection of their extension.
Specifying a disjoint correspondence may help a matcher in not proposing any correspondences between these classes.
|Solution=This pattern establishes correspondence stating that classes are disjoint.
}}
{{Alignment OP Example Template
|Solution=Example in EDOAL, the expressive and declarative ontology alignment language
<Cell>
<entity1><Class rdf:about="O1:Top"/></entity1>
<entity2><Class rdf:about="O2:Top"/></entity2>
<relation>Disjoint</relation>
</Cell>
}}
{{Alignment OP References Template
|RelatedTo=DisjointAttributes, DisjointInstances
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Class Union

2010-01-28T09:13:55Z

FrancoisScharffe: initial submission

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=class-union.png
}}
{{Alignment OP General Template
|Name=Class Union
|SubmittedBy=FrancoisScharffe
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Problem=A class denoted in one ontology is the union of two classes in the second ontology
|Solution=This pattern establishes a correspondence between a pair of classes in the first ontology and a single class in the other. This pattern is agnostic as to whether the correspondence is unidirectional or bidirectional. Direction of the correspondence can be achieved through combination of the pattern with the Class equivalence or Class Subsumption pattern.
}}
{{Alignment OP Example Template
|Solution=Exemple in the alignment language RDF/XML syntax:
<Cell>
<entity1>
<Class>
<or rdf:ParseType="Collection">
<Class rdf:about="O1:PersonBornInCanada"/>
<Class rdf:about="O1:PersonWithCanadianParent"/>
</or>
</Class>
</entity1>
<entity2>
<Class rdf:about="O2:CanadianCitizenByBirth"/>
</entity2>
<relation>equivalence</relation>
</Cell>
|Consequences=A correspondence is established between the two classes
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence, Class Subsumption
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Class subsumption

2010-01-27T13:09:18Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=class-subsumption.png
}}
{{Alignment OP General Template
|Name=Class subsumption
|SubmittedBy=FrancoisScharffe
|Author=FrancoisScharffe
}}
{{Alignment OP Description Template
|Domain=general
|Problem=A class in one ontology is a subclass of a class in a second ontology but there is
no functional description of the exact mapping. There is no way of expressing
additional properties of the subclass.
|Solution=This pattern establishes a unidirectional correspondence from a more specific class
in one ontology to a broader class in another ontology. The relation is broadened
to allow class expressions in addition to merely class names.
}}
{{Alignment OP Example Template
|Solution=Example solution in the ontology alignment language:
<Cell>
<entity1><Class rdf:about="O1:Mammal"/></entity1>
<entity2><Class rdf:about="O2:Vertebrate"/></entity2>
<relation>subsumedBy</relation>
</Cell>
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Class intersection

2010-01-27T13:08:32Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=class-intersection.png
}}
{{Alignment OP General Template
|Name=Class intersection
|SubmittedBy=FrancoisScharffe
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class denoted in one ontology is the intersection of two classes in the second
ontology.
|Solution=This pattern establishes a correpondence between a pair of classes in the first ontology and a single class in the other. This pattern is agnostic as to whether the correspondence is unidirectional or bidirectional. Direction of the correspondence can be achieved through combination of the pattern with the Equivalent Class or Class subsumption patterns.
}}
{{Alignment OP Example Template
|Scenario=Class intersection scenario
|Solution=Example solution in the ontology alignment language:
<Cell>
<entity1>
<Class>
<and rdf:ParseType="Collection">
<Class rdf:about="o1:Human"/>
<Class rdf:about="o1:FemaleAnimal/>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2:HumanFemale"/>
</entity2>
<relation>equivalence</relation>
</Cell>
|Consequences=A correspondence is established between a class in a source ontology and the intersection of a set of classes in a target ontology.
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence, Class subsumption
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Class intersection

2010-01-27T13:07:58Z

FrancoisScharffe:

Submissions:Class intersection

2010-01-27T13:06:24Z

FrancoisScharffe: initial submission

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=class-intersection.png
}}
{{Alignment OP General Template
|Name=Class intersection
|SubmittedBy=FrancoisScharffe
|Author=François Scharffe
}}
{{Alignment OP Description Template
|Domain=General
|Problem=A class denoted in one ontology is the intersection of two classes in the second
ontology.
|Solution=This pattern establishes a correpondence between a pair of classes in the first ontology and a single class in the other. This pattern is agnostic as to whether the correspondence is unidirectional or bidirectional. Direction of the correspondence can be achieved through combination of the pattern with the Equivalent Class or Class subsumption patterns.
}}
{{Alignment OP Example Template
|Scenario=Class intersection scenario
|Solution=<Cell>
<entity1>
<Class>
<and rdf:ParseType="Collection">
<Class rdf:about="o1:Human"/>
<Class rdf:about="o1:FemaleAnimal/>
</and>
</Class>
</entity1>
<entity2>
<Class rdf:about="o2:HumanFemale"/>
</entity2>
<relation>equivalence</relation>
</Cell>
|Consequences=A correspondence is established between a class in a source ontology and the intersection of a set of classes in a target ontology.
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence, Class subsumption
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Class subsumption

2010-01-27T12:53:03Z

FrancoisScharffe:

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=class-subsumption.png
}}
{{Alignment OP General Template
|Name=Class subsumption
|SubmittedBy=FrancoisScharffe
|Author=FrancoisScharffe
}}
{{Alignment OP Description Template
|Domain=general
|Problem=A class in one ontology is a subclass of a class in a second ontology but there is
no functional description of the exact mapping. There is no way of expressing
additional properties of the subclass.
|Solution=This pattern establishes a unidirectional correspondence from a more specific class
in one ontology to a broader class in another ontology. The relation is broadened
to allow class expressions in addition to merely class names.
}}
{{Alignment OP Example Template
|Solution=<Cell>
<entity1><Class rdf:about="O1:Mammal"/></entity1>
<entity2><Class rdf:about="O2:Vertebrate"/></entity2>
<relation>subsumedBy</relation>
</Cell>
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Class subsumption

2010-01-27T12:51:17Z

FrancoisScharffe: adding a diagram

{{Alignment_OP_Proposal_toolbar}}
{{Include Image
|ImageName=class-subsumption
}}
{{Alignment OP General Template
|Name=Class subsumption
|SubmittedBy=FrancoisScharffe
|Author=FrancoisScharffe
}}
{{Alignment OP Description Template
|Domain=general
|Problem=A class in one ontology is a subclass of a class in a second ontology but there is
no functional description of the exact mapping. There is no way of expressing
additional properties of the subclass.
|Solution=This pattern establishes a unidirectional correspondence from a more specific class
in one ontology to a broader class in another ontology. The relation is broadened
to allow class expressions in addition to merely class names.
}}
{{Alignment OP Example Template
|Solution=<Cell>
<entity1><Class rdf:about="O1:Mammal"/></entity1>
<entity2><Class rdf:about="O2:Vertebrate"/></entity2>
<relation>subsumedBy</relation>
</Cell>
}}
{{Alignment OP References Template
|RelatedTo=Class equivalence
}}

{{Scenarios about me}}
{{Reviews about me}}

Submissions:Class subsumption

2010-01-26T13:43:56Z

FrancoisScharffe: This pattern capture a subsumption correspondence between two classes in two ontologies

{{Alignment_OP_Proposal_toolbar}}
{{Include Image}}
{{Alignment OP General Template
|Name=Class subsumption
|SubmittedBy=FrancoisScharffe
|Author=FrancoisScharffe
}}
{{Alignment OP Description Template
|Domain=general
|Problem=A class in one ontology is a subclass of a class in a second ontology but there is
no functional description of the exact mapping. There is no way of expressing
additional properties of the subclass.
|Solution=This pattern establishes a unidirectional correspondence from a more specific class
in one ontology to a broader class in another ontology. The relation is broadened
to allow class expressions in addition to merely class names.
}}
{{Alignment OP Example Template
|Solution=<Cell>
<entity1><Class rdf:about="O1:Mammal"/></entity1>
<entity2><Class rdf:about="O2:Vertebrate"/></entity2>
<relation>subsumedBy</relation>
</Cell>

}}
{{Alignment OP References Template
|RelatedTo=Class equivalence
}}

{{Scenarios about me}}
{{Reviews about me}}

File:Transitive-relation.png

2009-11-27T16:16:51Z

FrancoisScharffe:

File:Symmetric-relation.png

2009-11-27T16:16:37Z

FrancoisScharffe:

File:Relation-subsumption.png

2009-11-27T16:16:23Z

FrancoisScharffe:

File:Relation-by-range-restriction.png

2009-11-27T16:16:11Z

FrancoisScharffe:

File:Relation-by-domain-restriction.png

2009-11-27T16:15:52Z

FrancoisScharffe:

File:Rca-a-concat-pattern.png

2009-11-27T16:15:35Z

FrancoisScharffe:

File:Property-value.png

2009-11-27T16:15:15Z

FrancoisScharffe:

File:Property-subsumption.png

2009-11-27T16:14:43Z

FrancoisScharffe:

File:Property-relation-composite.png

2009-11-27T16:13:26Z

FrancoisScharffe:

File:Property-relation.png

2009-11-27T16:13:02Z

FrancoisScharffe: uploaded a new version of "Image:Property-relation.png": Reverted to version as of 16:12, 27 November 2009

File:Property-relation.png

2009-11-27T16:12:46Z

FrancoisScharffe: uploaded a new version of "Image:Property-relation.png"

File:Property-relation.png

2009-11-27T16:12:30Z

FrancoisScharffe: