'Ontology Design Patterns' - User contributions [en]

'Ontology Design Patterns':News/10

2011-10-28T00:14:41Z

RimDJEDIDI: New page: {{NewsInfo |SubmittedBy=RimDJEDIDI |PostedOn=2011-10-27T23:23:04 |ShortText=Lim&Bio Lab (Paris 13 University) organized an ODP Seminar with Valentina Presutti and Aldo Gangemi (STLab – C...

{{NewsInfo
|SubmittedBy=RimDJEDIDI
|PostedOn=2011-10-27T23:23:04
|ShortText=Lim&Bio Lab (Paris 13 University) organized an ODP Seminar with Valentina Presutti and Aldo Gangemi (STLab – CNR – Italy). The purpose of the seminar was to present ODP patterns (examples, use cases, pattern typology) and to discuss relevant modeling problems and ODP reuse and extension.
}}
{{TitleDescription Template
|Title=ODP Seminar in Lim&Bio Lab - Paris 13 University - 16th June 2011
|Description=Lim&Bio Lab (Medical Informatics Laboratory of Paris 13 University) organized an ODP Seminar with Valentina Presutti and Aldo Gangemi (STLab – CNR – Italy).

The purpose of the seminar was to present ODP patterns (examples, use cases, pattern typology) and to discuss relevant modeling problems and ODP reuse and extension.

}}

'Ontology Design Patterns':Partners

2011-10-27T23:45:02Z

RimDJEDIDI:

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

The following institutions contribute to the portal site editorial work.

{| border="0" style="background:transparent;"
|-
|
[[Image:Logo_limbio.png|100px|left|thumb|Medical Informatics Lab Paris 13 University]] [http://www-limbio.smbh.univ-paris13.fr/site/index.php/lang-en]
||
[[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

2011-10-27T23:44:15Z

RimDJEDIDI:

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

The following institutions contribute to the portal site editorial work.

{| border="0" style="background:transparent;"
|-
|
[[Image:Logo_limbio.png|100px|left|thumb|Biomedical Informatics Lab Paris 13 University]] [http://www-limbio.smbh.univ-paris13.fr/site/index.php/lang-en]
||
[[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]
|}

User:RimDJEDIDI

2011-10-27T23:36:03Z

RimDJEDIDI:

{{User Template
|FirstName=Rim
|LastName=DJEDIDI
|Gender=Female
|Picture=ODPUser.png
|EmailAddress=rim.djedidi@gmail.com
|HomePage=http://sites.google.com/site/rimdjedidi/
|Organization=Paris 13 University - Lim&Bio Laboratory (Medical Informatics & Bioinformatics Laboratory)
|OrganizationType=Educational Training and Research Institution
|Country=France (FR)
|Role=Researcher
}}
{{Account Request Template
|Motivation=I work on ontology engineering and knowledge-based medical decision support system. My main motivation is to interact with the ODP community to share modeling experience, propose ontology patterns and have feedback, and participate in evaluating submitted ones.
|PossibleMainContribution=To have some help to solve modeling problems, To help other users to solve modeling problems
|DomainsOfInterest=Community:Ontology, Community:Healthcare, Community:Decision-making, Community: Recommendation, Community:General, Community: Participation, Community:Parts and Collections, Community:Time, Community:Workflow, Community: Upper Ontology, Community:Vocabulary, Community:Linguistic, Community: Music
|ExpertOfDomains=Community:Ontology
|HowDidIKnowAbout=conference/public events, surfing the web
}}
[[Category:EBMember]]

'Ontology Design Patterns':Partners

2011-10-27T23:00:25Z

RimDJEDIDI:

'Ontology Design Patterns':Partners

2011-10-27T22:59:38Z

RimDJEDIDI:

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

The following institutions contribute to the portal site editorial work.

{| border="0" style="background:transparent;"
|-
|
[[Image:Logo_limbio.png|100px|left|thumb|Medical Informatics Lab Paris13 Univ.]] [http://www-limbio.smbh.univ-paris13.fr/site/index.php/lang-en]
||
[[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:Logo limbio.png

2011-10-27T22:54:52Z

RimDJEDIDI:

User:RimDJEDIDI

2010-10-26T14:52:42Z

RimDJEDIDI:

{{User Template
|FirstName=Rim
|LastName=DJEDIDI
|Gender=Female
|Picture=ODPUser.png
|EmailAddress=rim.djedidi@gmail.com
|HomePage=http://sites.google.com/site/rimdjedidi/
|Organization=Paris 13 University - Lim&Bio Laboratory (Medical Informatics & Bioinformatics Laboratory)
|OrganizationType=Educational Training and Research Institution
|Country=France (FR)
|Role=Researcher
}}
{{Account Request Template
|Motivation=I work on OWL ontology change management patterns. My main motivation is to interact with the ODP community to share modeling experience, propose ontology patterns and have feedback.
|PossibleMainContribution=To have some help to solve modeling problems, To help other users to solve modeling problems
|DomainsOfInterest=Community:Ontology, Community:Healthcare, Community:Biology, Community:Ontology Alignement, Community:General, Community:Parts and Collections, Community:Vocabulary
|ExpertOfDomains=Community:Ontology
|HowDidIKnowAbout=conference/public events, surfing the web
}}
[[Category:EBMember]]

Reviews:RimDJEDIDI about Symmetric n-ary relationship

2010-09-16T14:31:24Z

RimDJEDIDI: New page: {{Content OP Proposal Review Template |CreationDate=2010/9/16 |SubmittedBy=RimDJEDIDI |ContentOPUnderReview=Symmetric n-ary relationship |RevisionID=10106 |Score=0 - needs major revision |...

{{Content OP Proposal Review Template
|CreationDate=2010/9/16
|SubmittedBy=RimDJEDIDI
|ContentOPUnderReview=Symmetric n-ary relationship
|RevisionID=10106
|Score=0 - needs major revision
|ReviewSummary=This pattern is proposed to model Symmetric n-ary relationship by explicitly expressing that participating classes have the same attributes and values of these attributes; while avoiding redundancy representation.

the general problem addressed by this pattern (modeling issues) is not defined. Besides, the pattern is not explained neither presented as a generic solution. Solution description is not sufficiently convincing : do cardinality and equivalentClass axioms guarantee the purpose of the pattern?

Explanation, proof and implementation are missed. And this is very important when proposing an ODP to be reused.

the given example is not suitable as it is based on a symmetric binary-relationship.

|ReviewConfidence=Competence in ODPs in general and addressed problem.
}}

Reviews:RimDJEDIDI about Faceted Classification Scheme

2010-09-15T15:39:15Z

RimDJEDIDI: New page: {{Content OP Proposal Review Template |CreationDate=2010/9/15 |SubmittedBy=RimDJEDIDI |ContentOPUnderReview=Faceted Classification Scheme |RevisionID=10067 |Score=1 - needs minor revision ...

{{Content OP Proposal Review Template
|CreationDate=2010/9/15
|SubmittedBy=RimDJEDIDI
|ContentOPUnderReview=Faceted Classification Scheme
|RevisionID=10067
|Score=1 - needs minor revision
|ReviewSummary=This pattern could be a useful solution to model a specific domain as A Faceted Classification Scheme (FCS)and classify its items(classes or individuals).

The evaluation of this pattern should take into account the one of Normalization ODP pattern submitted. There is important mapping between the two patterns.

Some remarks (to verify):
- Mutual exclusion between categories of FCS (as mentioned in the definition) is not included in Normalization ODP generic structure (part ontology).
- In the description of part "Process", considering the Normalization ODP, Facet_i should "has" and not "become" an object property :hasFacet_i.
- There is a little difference between the first item example in the description of "Example of Non-Ontological Resource" and in the graphical representation of "Ontology Example" as well as in the description of "Process example".
-the OWL defined class "ManualDishDetergent" in the graphical representation of "Ontology example" should be "PersonDishDetergent".
- in the graphical representation of "Process example", there is the generic representation of the process and not the example.

Questions
-Is there any difference between Normalization ODP modeling issues and FCS modeling issues?

|ReviewConfidence=Competence in ODPs in general and the problem addressed.
|ReviewUnderstandability=Easy to understand with clear details.
}}

File:Djedidi LOP2 WOP09.pdf

2009-09-24T18:21:38Z

RimDJEDIDI: uploaded a new version of "Image:Djedidi LOP2 WOP09.pdf": This file contains graphical representations illustrating the Logical OP "Enlarge Class Definition for Resolving Disjointness due to Subsomption"

this logical pattern propose a solution to resolve a disjointness inconsistency in an ontology due to a subsomption

Submissions:Enlarge Class Definition for Resolving Disjointness due to Subsomption

2009-09-24T18:19:36Z

RimDJEDIDI: This pattern helps resolving a logical inconsistency triggered by a situation of disjoint classes subsuming a common sub-class.

{{Logical_OP_Proposal_toolbar}}
{{Include Image
|ImageName=Djedidi_LOP2_WOP09.pdf
}}
{{Logical OP General Template
|Name=Enlarge Class Definition for Resolving Disjointness due to Subsumption.
|SubmittedBy=RimDjedidi
|Author=Rim DJEDIDI
}}
{{Logical OP Description Template
|Motivation=Problem :

This pattern helps resolving a logical inconsistency triggered by a situation of disjoint classes subsuming a common sub-class. When we need to define – for some modeling issues related to domain of interest – a class as a sub-class of two disjoint classes, a disjointness inconsistency is caused. The problem can be illustrated by the following scenario: let’s consider a class Sub_Class defined as a sub-class of a class Disjoint_Class 2; and a class Disjoint_Class 1 disjoint with the Disjoint_Class 2 (see diagram in attached file). If we need to add a sub-class relation between the Sub_Class and the Disjoint_Class 1, this generates a disjointness inconsistency:

- If the extension of the Sub_Class contains individuals instantiating this sub-class, the logical inconsistency will be extended to the knowledge base; - If the Sub_Class is not instantiated to individuals, it will be diagnosed as an unsatisfiable class.

To solve this inconsistency, one can think about deleting the disjointness axiom. However, this can alter the semantics expressed in the ontology, and negatively affect consistency checking and automatic evaluation of existing individuals as explained in [1]. This pattern tackles the questions of how to resolve the inconsistency caused by such kind of subsumption while preserving existing knowledge.

[1] Völker, J., Vrandecic, D., Sure, Y., Hotho, A.: Learning Disjointness. In F., Enrico, K., Michael, May. Wolfgang (Eds.). Proceedings of the 4th European Semantic Web Conference, ESWC 2007. LNCS: Vol. 4519 pp: 175-189. (2007)
|Aim=Intent: The purpose of this pattern is to support the semantics of a subsumption defined under two disjoint classes and resolve the resulting inconsistency.

Covered Requirements: The pattern solves a problem of disjointness inconsistency caused by a subsumption relation without deleting the disjointness axiom so that existing knowledge can be preserved.
|Solution=The pattern resolves a disjointness inconsistency –caused by a subsumption– by enlarging the definition of the sub-class object of the disjointness inconsistency, based on the definition of the involved disjoint classes. The definition of the sub-class is enlarged by the union (OR) of the definitions of the disjoint classes.

The application of the solution can be described by the following process (see diagram in attached file):
1) The pattern enlarges the definition of the sub-class object of the disjointness inconsistency by defining –in its description– a union of the definitions of the disjoint classes involved in the inconsistency to be resolved.
|Elements=the following elements are manipulated by the pattern:

ID of the sub-class to enlarge (Sub_Class).
ID of the first disjoint class (Disjoint_Class 1).
ID of the second disjoint class (Disjoint_Class 2).
}}
{{Logical OP Example Template
|ProblemExample=Let’s consider the OWL ontology O defined by the following axioms:

{Animal ⊑Fauna-Flora, Plant ⊑Fauna-Flora, Carnivorous-Plant ⊑Plant, Plant ⊑ Not(Animal)}

If we apply a change to the ontology defining Carnivorous-Plant class as a sub-class of the class Animal, we cause a disjointness inconsistency. The proposed pattern resolves this kind of inconsistency.
|Consequences=The application of the pattern to resolve the example above is performed as follow:
1) The pattern enlarges the definition of the sub-class object of the disjointness inconsistency Carnivorous-Plant by defining –in its description– a union of the definitions of the disjoint classes involved in the inconsistency: the classes Animal and Plant.
}}
{{Logical OP Reference Template
|KnownUse= This pattern is proposed as another solution to the problem solved by the Logical OP "Define Hybrid Class Resolving Disjointness due to Subsumption"
}}
[[Category:Review assigned]]
{{Scenarios about me}}
{{Reviews about me}}
{{Submission to event
|Event=WOP2009:Main
}}

File:Djedidi LOP2 WOP09.pdf

2009-09-24T17:59:26Z

this logical pattern propose a solution to resolve a disjointness inconsistency in an ontology due to a subsomption

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-09-24T17:55:50Z

RimDJEDIDI:

{{Logical_OP_Proposal_toolbar}}
{{Include Image
|ImageName=Djedidi_LOP1_WOP09.pdf
}}
{{Logical OP General Template
|Name=Define Hybrid Class Resolving Disjointness due to Subsumption
|SubmittedBy=RimDjedidi
|Author=Rim Djedidi, Marie-Aude Aufaure
}}
{{Logical OP Description Template
|Motivation=Problem :
This pattern helps resolving a logical inconsistency triggered by a situation of disjoint classes subsuming a common sub-class. When we need to define – for some modeling issues related to domain of interest – a class as a sub-class of two disjoint classes, a disjointness inconsistency is caused.
The problem can be illustrated by the following scenario: let’s consider a class Sub_Class defined as a sub-class of a class Disjoint_Class 2; and a class Disjoint_Class 1 disjoint with the Disjoint_Class 2 (see diagram in attached file). If we need to add a sub-class relation between the Sub_Class and the Disjoint_Class 1, this generates a disjointness inconsistency:

- If the extension of the Sub_Class contains individuals instantiating this sub-class, the logical inconsistency will be extended to the knowledge base;
- If the Sub_Class is not instantiated to individuals, it will be diagnosed as an unsatisfiable class.

To solve this inconsistency, one can think about deleting the disjointness axiom. However, this can alter the semantics expressed in the ontology, and negatively affect consistency checking and automatic evaluation of existing individuals as explained in [1].
This pattern tackles the questions of how to resolve the inconsistency caused by such kind of subsumption while preserving existing knowledge.

[1] Völker, J., Vrandecic, D., Sure, Y., Hotho, A.: Learning Disjointness. In F., Enrico, K., Michael, May. Wolfgang (Eds.). Proceedings of the 4th European Semantic Web Conference, ESWC 2007. LNCS: Vol. 4519 pp: 175-189. (2007)
|Aim=Intent: The purpose of this pattern is to support the semantics of a subsumption defined under two disjoint classes and resolve the resulting inconsistency.

Covered Requirements: The pattern solves a problem of disjointness inconsistency caused by a subsumption relation without deleting the disjointness axiom so that existing knowledge can be preserved.
|Solution=The pattern resolves a disjointness inconsistency –due to a subsumption–by defining a Hybrid Class based on the definition of disjoint classes implicated in the inconsistency; and redistributing correctly sub-class relations between the sub-class, the hybrid class, and the most specific common super-class of the disjoint classes implicated. The definition of the Hybrid Class is the union (OR) of the definitions of the disjoint classes.
The application of the solution can be described by the following process (see diagram in attached file):

1.The pattern defines a Hybrid Class as a union of the definitions of the disjoint classes implicated in the inconsistency to be resolved;
2.The pattern defines a subsumption between the most specific common super-class of the disjoint classes implicated in the inconsistency, and the Hybrid Class created;
3.The pattern defines a subsumption between the Hybrid Class and the sub-class involved in the inconsistency.

Consequences: The application of the pattern resolves the disjointness inconsistency (even if the involved sub-class is instantiated by individuals) and preserves existing knowledge. As a Logical OP, this pattern is independent from a specific domain of interest. However, it depends on the expressivity of the logical formalism used for the representation of the ontology. Therefore, the language of the targeted ontology should allow expressing class union.
|Elements=The following elements are manipulated by the pattern:
ID of the sub-class (Sub_Class).
ID of the first disjoint class (Disjoint_Class 1).
ID of the second disjoint class (Disjoint_Class 2).
ID of the most specific common super-class of the disjoint classes involved (Common_Super_Class).
}}
{{Logical OP Example Template
|ProblemExample=Let’s consider the OWL ontology O defined by the following axioms:
{Animal ⊑Fauna-Flora, Plant ⊑Fauna-Flora, Carnivorous-Plant ⊑Plant, Plant ⊑ Not(Animal)}

If we apply a change to the ontology defining Carnivorous-Plant class as a sub-class of the class Animal, we cause a disjointness inconsistency. The proposed pattern resolves this kind of inconsistency.
|Consequences=The application of the pattern to resolve the example above is performed as follow:
1.The pattern defines a class Animal_Plant as a union of the definitions of the disjoint classes Animal and Plant;
2.The pattern defines a subsumption between the most specific common super-class of the disjoint classes Fauna-Flora and the hybrid class created Animal_Plant;
3.The pattern defines a subsumption between the defined hybrid class Animal_Plant and the sub-class Carnivorous-Plant involved in the inconsistency.
}}
{{Logical OP Reference Template}}
[[Category:Review assigned]]
{{Scenarios about me}}
{{Reviews about me}}
{{Submission to event
|Event=WOP2009:Main
}}

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-09-24T17:52:32Z

RimDJEDIDI:

File:Djedidi LOP1 WOP09.pdf

2009-09-24T17:31:47Z

RimDJEDIDI: uploaded a new version of "Image:Djedidi LOP1 WOP09.pdf": This file contains graphical representations illustrating the Logical OP "Define Hybrid Class Resolving Disjointness due to Subsumption"

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-09-24T17:27:17Z

RimDJEDIDI: Solving a problem of disjointness inconsistency caused by a subsumption relation.

{{Logical_OP_Proposal_toolbar}}
{{Include Image
|ImageName=Djedidi_LOP1_WOP09.pdf
}}
{{Logical OP General Template
|Name=Define Hybrid Class Resolving Disjointness due to Subsumption
|SubmittedBy=RimDjedidi
|Author=Rim Djedidi, Marie-Aude Aufaure
}}
{{Logical OP Description Template
|Motivation=Problem :
This pattern helps resolving a logical inconsistency triggered by a situation of disjoint classes subsuming a common sub-class. When we need to define – for some modeling issues related to domain of interest – a class as a sub-class of two disjoint classes, a disjointness inconsistency is caused.
The problem can be illustrated by the following scenario: let’s consider a class Sub_Class defined as a sub-class of a class Disjoint_Class 2; and a class Disjoint_Class 1 disjoint with the Disjoint_Class 2 (see diagram in attached file). If we need to add a sub-class relation between the Sub_Class and the Disjoint_Class 1, this generates a disjointness inconsistency:

- If the extension of the Sub_Class contains individuals instantiating this sub-class, the logical inconsistency will be extended to the knowledge base;
- If the Sub_Class is not instantiated to individuals, it will be diagnosed as an unsatisfiable class.

To solve this inconsistency, one can think about deleting the disjointness axiom. However, this can alter the semantics expressed in the ontology, and negatively affect consistency checking and automatic evaluation of existing individuals as explained in [1].
This pattern tackles the questions of how to resolve the inconsistency caused by such kind of subsumption while preserving existing knowledge.

1. Völker, J., Vrandecic, D., Sure, Y., Hotho, A.: Learning Disjointness. In F., Enrico, K., Michael, May. Wolfgang (Eds.). Proceedings of the 4th European Semantic Web Conference, ESWC 2007. LNCS: Vol. 4519 pp: 175-189. (2007)

|Aim=Intent: The purpose of this pattern is to support the semantics of a subsumption defined under two disjoint classes and resolve the resulting inconsistency.

Covered Requirements: The pattern solves a problem of disjointness inconsistency caused by a subsumption relation without deleting the disjointness axiom so that existing knowledge can be preserved.

|Solution=The pattern resolves a disjointness inconsistency –due to a subsumption–by defining a Hybrid Class based on the definition of disjoint classes implicated in the inconsistency; and redistributing correctly sub-class relations between the sub-class, the hybrid class, and the most specific common super-class of the disjoint classes implicated. The definition of the Hybrid Class is the union (OR) of the definitions of the disjoint classes.
The application of the solution can be described by the following process (see diagram in attached file):

1.The pattern defines a Hybrid Class as a union of the definitions of the disjoint classes implicated in the inconsistency to be resolved;
2.The pattern defines a subsumption between the most specific common super-class of the disjoint classes implicated in the inconsistency, and the Hybrid Class created;
3.The pattern defines a subsumption between the Hybrid Class and the sub-class involved in the inconsistency.

Consequences: The application of the pattern resolves the disjointness inconsistency (even if the involved sub-class is instantiated by individuals) and preserves existing knowledge. As a Logical OP, this pattern is independent from a specific domain of interest. However, it depends on the expressivity of the logical formalism used for the representation of the ontology. Therefore, the language of the targeted ontology should allow expressing class union.

|Elements=The following elements are manipulated by the pattern:
ID of the sub-class (Sub_Class).
ID of the first disjoint class (Disjoint_Class 1).
ID of the second disjoint class (Disjoint_Class 2).
ID of the most specific common super-class of the disjoint classes involved (Common_Super_Class).
}}
{{Logical OP Example Template
|ProblemExample=Let’s consider the OWL ontology O defined by the following axioms:
{Animal ⊑Fauna-Flora, Plant ⊑Fauna-Flora, Carnivorous-Plant ⊑Plant, Plant ⊑ Not(Animal)}

If we apply a change to the ontology defining Carnivorous-Plant class as a sub-class of the class Animal, we cause a disjointness inconsistency. The proposed pattern resolves this kind of inconsistency.

|Consequences=The application of the pattern to resolve the example above is performed as follow:
1.The pattern defines a class Animal_Plant as a union of the definitions of the disjoint classes Animal and Plant;
2.The pattern defines a subsumption between the most specific common super-class of the disjoint classes Fauna-Flora and the hybrid class created Animal_Plant;
3.The pattern defines a subsumption between the defined hybrid class Animal_Plant and the sub-class Carnivorous-Plant involved in the inconsistency.

}}
{{Logical OP Reference Template}}
[[Category:Review assigned]]
{{Scenarios about me}}
{{Reviews about me}}
{{Submission to event
|Event=WOP2009:Main
}}

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-09-24T00:38:16Z

RimDJEDIDI:

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-09-24T00:33:43Z

RimDJEDIDI:

Submissions:Classification scheme - adjacency list model - to Taxonomy

2009-09-07T10:40:52Z

RimDJEDIDI: Review has been created. Annotation 'assigned' has been removed. Annotation 'waiting' has been removed.

{{Reengineering_OP_Proposal_toolbar}}
{{Reengineering OP Proposal General Information Template
|Name=Classification scheme - adjacency list model - to Taxonomy
|Problem=Re-engineering a classification scheme which follows the adjacency list model to design a taxonomy.
}}
{{Reengineering OP Proposal NOR Template
|Description=A non-ontological resource holds a classification scheme which follows the adjacency list model.
A classification scheme is a rooted tree of concepts, in which each concept groups entities by some particular degree of similarity.
The semantics of the hierarchical relation between parents and children concepts may vary depending of the context.
The adjacency list data model for hierarchical classifications proposes to create an entity which holds a list of items with a linking column associated to their parent items.
|Graphical Representation=AdjacencyList.png
}}
{{Reengineering OP Proposal Ontology Template
|Description=The generated ontology will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are mapped to subClassOf relations.
|Graphical Representation=Ontology.png
}}
{{Reengineering OP Proposal Process Template
|Description=1. Identify the classification scheme items which do not have a parent key value, i.e. classification scheme items without parents. Formally, every cei, which caparentID = NULL.

2. For each one of the above identified classification scheme items cei:

2.1. Create the corresponding ontology class, Ci class.

2.2. Identify the classification scheme items, cej , which are children of cei, by using the parent key values.

2.3. For each one of the above identified classification scheme items cej :

2.3.1. Create the corresponding ontology class, Cj class.

2.3.2. Set up the subClassOf relation between Cj and Ci.

2.3.3. Repeat from step 2.2 for cej as a new cei.

3. If there are more than one classification scheme items without parent cei

3.1. Create an ad-hoc class as the root class of the ontology.

3.2. Set up the subClassOf relation between Ci class and the root class.
|Graphical Representation=wfcsalso.png
}}
{{Reengineering OP Proposal Scenario Example Template
|Description=Suppose that someone wants to build an ontology based on the water areas classification published by FAO. This classification scheme follows the adjacency list data model.
}}
{{Reengineering OP Proposal NOR Example Template
|Description=The FAO classification for water areas groups them according to some different criteria as environment, statistics, and jurisdiction, among others.
|Graphical Representation=AdjacencyListWaterAreas.png
|Web Reference=http://www.fao.org/figis/servlet/RefServlet
}}
{{Reengineering OP Proposal Ontology Example Template
|Description=The generated ontology will be based on the taxonomy architectural pattern (AP-TX-01). Each category in the classification scheme is mapped to a class, and the semantics of the relationship between children and parent categories are mapped to subClassOf relations.
|Graphical Representation=WaterAreaOntology.png
|Web Reference=http://www.fao.org/aims/neon.jsp
}}
{{Reengineering OP Proposal Process Example Template
|Description=1. Create the Water area class.

2. Create the Environmental area class, and set up the subClassOf relation between the Environmental area class and the Water area class.

2.1. Create the Inland/marine class, and set up the subClassOf relation between the Inland/marine class and the Environmental area class.

2.2. Create the Ocean class, and set up the subClassOf relation between the Ocean class and the Environmental area class.

2.3. Create the North/South/Equatorial class, and set up the subClassOf relation between the North a South a Equatorial class and the Environmental area class.

3. Create the Fishing Statistical area class, and set up the subClassOf relation
between the Fishing Statistical area class and the Water area class.

3.1. Create the FAO statistical area class, and set up the subClassOf relation between the FAO statistical area class and the Fishing Statistical area class.

3.2. Create the Areal grid system class, and set up the subClassOf relation between the Areal grid system class and the Fishing Statistical area class.

4. Create the Jurisdiction area class, and set up the subClassOf relation between the Jurisdiction area class and the Water area class.
|Graphical Representation=wfcsalsoexample.png
}}
{{Reengineering OP Proposal Additional Information Template
|SubmittedBy=Boris Villazón Terrazas,
|Author=Boris Villazón Terrazas,
|Also known as=Classification scheme to Taxonomy (adjacency list model)
|Related to=Use the Architectural Pattern: TX-AP-01
}}

{{Scenarios about me}}
{{Reviews about me}}
{{Submission to event
|Event=WOP2009:Main
}}

[[Category:Review assigned]]

Reviews:RimDJEDIDI about Classification scheme - adjacency list model - to Taxonomy

2009-09-07T10:40:51Z

RimDJEDIDI: New page: {{Content OP Proposal Review Template |CreationDate=2009/9/7 |SubmittedBy=RimDJEDIDI |ContentOPUnderReview=Classification scheme - adjacency list model - to Taxonomy |RevisionID=5625 |Scor...

{{Content OP Proposal Review Template
|CreationDate=2009/9/7
|SubmittedBy=RimDJEDIDI
|ContentOPUnderReview=Classification scheme - adjacency list model - to Taxonomy
|RevisionID=5625
|Score=1 - needs minor revision
|ReviewSummary=This re-engineering pattern is proposed for re-engineering a non-ontological resource following the adjacency list model to design a taxonomy.

Suitability for WOP discussion: Relevant

Pattern Quality: an interesting initial version to be enriched
|ReviewConfidence=ODPs in general : High
The addressed Problem (adjacency list model): Medium
Taxonomy modeling : High
|ReviewProblems=1- The non-ontological resource (adjacency list model) re-engineered by this pattern is described as a rooted tree of concepts grouped by some particular degree of similarity. But it is stated that the semantics of hierarchical relation between concepts may vary depending on the context. So, if the relation between adjacency list entities related by a linking column (and expressed by the column title) is more rich than a kind of similarity or a generalization, re-engineering it to a taxonomy classification (mapping the relationship to a subClassOf relation) may reduce the original semantic relation between concepts.

2- There is no reference to the multi-inheritance case, however it is implicitly supported by the process. It should be explicitly clarified whether it is considered in this re-engineering or not modeled in a adjacency list.

3- Cyclic relationship: as a consequence to the first problem described above, a mutual relation between adjacency list concepts may lead to cyclic relation in the taxonomy when applying the process. The hierarchical structure of a taxonomy is typically organized by a subClassOf relation. So, cyclic relation will lead to confusing modeling of subClassOf, equivalent and symmetric semantic relations.

|ReviewRelevance=the intent of the pattern targets a relevant problem in re-engineering non-ontological resources which is how to re-engineer an adjacency list model? However, it needs to include more related issues.
|ReviewReusability=The pattern could be unsuitable for some kind of adjacency list. Its usability should be explicitly defined to avoid inappropriate reuse.
|ReviewUnderstandability=The pattern description is understandable. May be for documentation purpose and to facilitate its reuse particularly for novice or learner users, it would be more clear to add a definition for the different parameters used in the process at the beginning of its description.

|ReviewClearProblem=In the "non-ontological resource description" property, it is stated that the considered classification is a rooted tree, so if this means that adjacency list cannot represent a graph, it should be mentioned explicitly to avoid ambiguity about cyclic relation.
Besides, it should be made precise whether the re-engineering is specifically proposed to hierarchical classification adjacency list.

In summary, it should be specified under what conditions the pattern is applicable. A proposition could be to add a property "Applicability" to pattern description template?
|ReviewFigures=Figures are clear however, the diagram illustrating the re-engineering process are incomplete and should include the recursive mechanism (2.3.3 step) and the final step of creating the hierarchy's root.
}}

Submissions:Enlarge Class Definition for Resolving Disjointness due to Subsomption

2009-08-21T18:16:21Z

RimDJEDIDI:

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-08-21T18:14:20Z

RimDJEDIDI:

Submissions:Enlarge Class Definition for Resolving Disjointness due to Subsomption

2009-08-21T18:11:46Z

RimDJEDIDI: WOP'09

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-08-21T18:11:06Z

RimDJEDIDI:

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-08-21T18:09:22Z

RimDJEDIDI:

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-08-21T17:58:15Z

RimDJEDIDI:

File:Djedidi LOP2 WOP09.pdf

2009-08-21T17:53:45Z

RimDJEDIDI: this logical pattern propose a solution to resolve a disjointness inconsistency in an ontology due to a subsomption

this logical pattern propose a solution to resolve a disjointness inconsistency in an ontology due to a subsomption

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-08-21T17:51:14Z

RimDJEDIDI:

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-08-21T17:50:09Z

RimDJEDIDI: Wop'09

{{Logical_OP_Proposal_toolbar}}
{{Include Image
|ImageName=Djedidi_LOP1_WOP09
}}
{{Logical OP General Template
|Name=Define Hybrid Class Resolving Disjointness due to Subsomption
|SubmittedBy=RimDjedidi
|Author=Rim Djedidi
}}
{{Logical OP Description Template
|Motivation=Problem : Resolve disjointness –caused by a subsumption– by defining a hybrid class.

Competency Question : How to resolve disjointness –caused by a subsumption– by defining a hybrid class while maintaining the semantic of existing knowledge? Is there any precondition on the application of this resolution alternative?
|Aim=The logical pattern models an alternative resolving disjointness inconsistency –caused by a subsumption– by creating a hybrid class.
|Solution=The pattern resolves a disjointness inconsistency –caused by a subsumption– by defining a hybrid class based on the definition of disjoint classes involved in the inconsistency; and redistributing correctly sub-class relations between classes implicated in the inconsistency.
Process:
1) The pattern defines a hybrid class as a union of the definitions of the disjoint classes involved in the inconsistency to be resolved;
2) The pattern defines a subsumption between the most specific common super-class of the disjoint classes involved in the inconsistency and the hybrid class created;
3) The pattern defines a subsumption between the hybrid class and the sub-class on which the change causing the inconsistency is applied.
|Elements=The following elements are manipulated by the pattern:
ID of the sub-class (sub_classID).
ID of the first disjoint class (ClsDisj1ID).
ID of the second disjoint class (ClsDisj2ID).
ID of the most specific common super-class of the disjoint classes involved (Common_super_classID).
}}
{{Logical OP Example Template
|ProblemExample=Let’s consider the OWL ontology O defined by the following axioms:
{Animal ⊑Fauna-Flora, Plant ⊑Fauna-Flora, Carnivorous-Plant ⊑Plant, Plant ⊑ Not(Animal)}

If we apply a change to the ontology defining Carnivorous-Plant class as a sub-class of class Animal we cause a disjointness inconsistency as the class Carnivorous-Plant and the class Animal are disjointed.
The proposed pattern propose a resolution alternative to this kind of inconsistency

|Consequences=Define a hybrid class Animal_Plant based on the definition of the two disjoint classes involved in the inconsistency: Animal and Plant.
Then, create a sub-class relation between the hybrid class created and a common super-class of the classes Animal and Plant.
And finally, substitute the sub-class relation between the classes Animal and Carnivorous-Plant by a subsumption between the classes Carnivorous-Plant and Animal_Plant.

Process:
1) The pattern defines a class Animal_Plant as a union of the definitions of the disjoint classes Animal and Plant;
2) The pattern defines a subsumption between the most specific common super-class of the disjoint classes Fauna-Flora and the hybrid class created Animal_Plant;
3) The pattern defines a subsumption between the hybrid class Animal_Plant and the sub-class Carnivorous-Plant on which the change causing the inconsistency is applied.

}}
{{Logical OP Reference Template}}

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

Submissions:Define Hybrid Class Resolving Disjointness due to Subsumption

2009-08-21T17:31:15Z

RimDJEDIDI: this logical pattern is proposed as an ontology change alternative to resolve a disjointness inconsistency due a subsumption

File:Djedidi LOP1 WOP09.pdf

2009-08-21T17:26:20Z

RimDJEDIDI:

'Ontology Design Patterns':EB-1st-f2f-2009Feb23

2009-03-02T14:07:33Z

RimDJEDIDI: /* Minutes */

__FORCETOC__

= First Face 2 Face meeting of odp Editorial Board =

=== Agenda ===

* [10.00-11.00] Introduction to the web site, roles, tasks, procedures, and support for ODP editorial board members (Valentina)
* [11.00-11.20] Coffee break
* [11.20- 12.20] Questions and discussion
* [12.20-13.00] Responsible person for ODP areas, plan (next 3 months) for bootstrapping ODP with Action Points
* [13.00-14.30] Lunch
* [14.30-15.00] Fix Review/Certification Procedure
* [15.00-15.20] Dissemination activities - status and proposals (Valentina)
* [15.20-16.20] Question and discussion with proposals
* [16.20-16.50] Plan (next three months)
* [16.50-17.00] Next (remote) meeting date

* [20.00] Dinner

=== Venue ===

The meeting will be held at the '''Institute for Cognitive Science and Technology''', '''Piaget''' room (first floor).

Via San Martino della Battaglia 44, Rome

=== Hotels ===

==== *** ====

'''Hotel Villa delle Rose'''
* Address: Via Vicenza 5
* Phone: +39-06-4451795

* Rates:
** Single room: Euro 75,00
** Double room: Euro 100,00
** Breakfast included

* Distance and Route: walking distance, 3 minutes

* Web site: http://www.villadellerose.it/it/index.htm

'''Hotel S. Marco'''
* Address: Via Villafranca 1
* Phone: +3906490437

* Services:
** Pay tv
** Internet access
** minibar
** From 29.01.2009 to 15.03.2009 (free of charge)

* Rates:
** Single room : Euro 80
** Double room single occupancy: Euro 90
** Double room : Euro 99,00

* Distance and route: 1 minute walking distance

* Web site: http://www.hotelsanmarcoroma.com/

'''Hotel Montecarlo'''
* Address: Via Palestro 17/a
* Phone: +39064460000

* Rates:
** Single room: Euro 70,00
** Double room :Euro 90,00

* Distance and route: 4 minutes walking distance

* Web site: http://laral.istc.cnr.it/address.htm

==== **** ====

'''Hotel Artemide'''

* Address: Via Nazionale 22
* Phone: +3906489911

* Services
** Internet access
** Mini-bar
** Room service
** Satellite TV
** Free daily newspaper

* Rates:
** Single room: Euro 170,00
** Double single use : Euro 170,00
** Breakfast included

* Distance and route: 10 minutes walking

* Web site: http://www.hotelartemide.it/en/index.htm

'''Hotel Cosmopolita'''
* Address: Via di Sant'Eufemia 5 (close to Piazza Venezia)
* Phone: +390699707606

* Services:
** Internet access
** Mini-bar
** Direct phone
** Satellite TV
** Room service

* Rates
** Single room : Euro 120,00
** Double room: Euro 130,00
** Breakfast included

Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini walk for 5 minutes.

* Web site: http://www.hotel-cosmopolita.com/

'''Hotel Pace Elvetia'''
* Address: Via IV Novembre 104
* Phone: +39066795105

* Services:
** Wi-Fi in the hall
** Bar and Rooftop Terrace
** Remote control satellite tv
** Minibar
** Direct-dial telephone

* Rates:
** Single room : Euro 80,00
** Double room: Euro 100,00
** Breakfast included

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini just walk for 5 minutes.

* Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

=== Editorial Board member ===
{{Group eb members}}

=== Attendees ===
* [[User:ValentinaPresutti| Valentina Presutti]]
* [[User:RimDJEDIDI| Rim Djedidi]]
* [[User:VojtechSvatek| Vojtech Svatek]]
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:EnricoDaga| Enrico Daga]]
* [[User:GerdGroener| Gerd Groener]]
* [[User:FrancoisScharffe| Francois Scharffe]]

=== Sunday dinner attendees ===

* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[USer:RimDJEDIDI| Rim Djedidi]]
* [[User:VojtechSvatek| Vojtech Svatek]] (coming quite late, after 11pm, if at all)
* <s>[[User:FrancoisScharffe| Francois Scharffe]]</s> (finally won't make it)

=== Monday dinner attendees ===
* The dinner will be held at [http://www.squisitalia.com/locale.php?id=922 "Osteria della Gensola"]
** Address: Piazza della Gensola 15 (in front of Isola Tiberina)
** google map path (from the meeting site): [http://maps.google.it/maps?f=q&source=s_q&hl=it&geocode=&q=from:+via+san+martino+della+battaglia,+Rome+to:+Piazza+della+Gensola,+15,+00153+Roma+RM&sll=41.89516,12.490125&sspn=0.030539,0.074587&ie=UTF8&z=14]
** From P.zza della Repubblica, take the BUS 'H' and wait for 4 stops, go out on p.zza Sonnino and do 250 meters
* [[USer:ValentinaPresutti| Valentina Presutti]]
* <s>[[User:VojtechSvatek| Vojtech Svatek]]</s> (unfortunately, Alitalia cancelled my flight and replaced with quite an early one for Tuesday, so I will have to go to bed very soon...)
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:GerdGroener| Gerd Groener]]
* [[USer:RimDJEDIDI| Rim Djedidi]]
* [[User:EnricoDaga|Enrico Daga]]

=== Process Modeling Pattern Seminar (attendees) ===
* [http://stlab.istc.cnr.it/index.php/ProcessModelingFeb2009 Seminar details]
* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:GerdGroener| Gerd Groener]]
* [[User:EnricoDaga|Enrico Daga]]
* [[User:RimDJEDIDI|Rim Djedidi]]

=== Minutes ===
Valentina introduce:
EB members (responsibilities on):
* content of the web site
* co-leading, share responsibility and tasks
* dissemination activities

Things todo:
* plan to integrate mailing-list & wiki
* define workflows for each action
* bootstrap web-site
* define new content actions
* area for good - 'beautiful' - ontologies (not patterns)
* add new types of patterns: Logical, Correspondence,
* Define responsible editors for:
** each type of pattern: Logical, Correspondence, Content, Architectural, Re-engineering;
** wrt Content Patterns, the most huge category, focused on specific domains. They need responsible editors for each domain(s);

Review/certification process:
* Community;
* Quality committee (distributed on kind of patterns and/or on kind of domain); (expert and authoritative reviewers, not to be charged too much of work but to be involved as light collaboration)
* Certification: useful for trust/provenance issues

Presentations:
- violeta: connections between patterns and business process modeling (content or re-engineering?)
- gerd: process modeling
- francois: correspondence patterns, patterns in ontology mapping
- eva: content patterns modeling and use
- rim: ontology evolution, change managements patterns (consistency check and maintenance), and e-business model content patterns
- svojtek (remotely connected): pattern recognition of logical/structural elements in ontologies; patterns connect ontologies / legacy systems (databases); recognition of bad practices and refactoring procedures in ontologies.

Others candidates for the editorial board (not attending):
* Mathieu D'Aquin ("beautiful ontologies")
* Denny Vrandecic (logical patterns)
* Tania Tudorache (Biomedical domain, workflows)
* ... others?

We need responsibles for:
# rdf patters: - actually the portal hosts OWL/DL patterns, but RDF patterns are useful for some requirements of expressivity more that computational.
# datasets: building and provide datasets that use ontology design patterns (useful for benchmarking use...)
# usability-profiling, collecting good practices on annotation of patterns
# architectural, how to organize the shape of an ontology? Even if the ontology is modular, it has some architecture (maybe the same that takes care of logical ones)

Things to do next three months:
- Definition of new area
- Contribute in taking dissemination actions

AP:
* put guidelines for forms specifications
* put the list

valentina illustrates the definition of new type of patterns procedure (''will be a wiki page for it'')

(coffee break)

Procedure of proposing an improvement for the web site through the Development area

Valentina shows:
* how to login to the testarea site
* how to submit a new development task
** Form definitions should have a description of the fields related to the semantic properties (field -> SemanticProperty):
*** SemanticProperty already exists: see List of Categories, List of properties
*** SemanticProperty doesn’t exist: to be created
**** Always defining a description for a property (it will be displayed as pop-up tool tips
**** Convention of naming SemanticProperty will be online
* AP (enrico): add the name of the submitter in the list of tasks
* (AP enrico) -> mailing list watching some pages (feedback, developments)
** It will be soon notification service to EB when new user feedback through mailing list and also as a new submitted task (Always take aware about feedbacks, user feedbacks are useful for EB and could be promoted to task)
* NOTE: Patterns could have relations between each others => to mention explicitly when created

Description of the reviewing process by the evaluation
* AP: add autocompletion in the assign review special page;
* NOTE: actually there is no mail notification, so we will start it on the second half of March; BUT if some EB member wants to start the process he can, has to notify personally the reviewer;
* AP (Aldo, Valentina, Eva): define review schema for content patterns;
* A pattern author can put a proposal without asking for a review (if not yet ready/mature for evaluation process) and improve it after
* AP (enrico) fix a bug on the evaluation template for reviews;
* A review must contain:
** rationale justifications/explanations
** recommendations for pattern improvement/correction
** using SemanticProperties

* AP (enrico): remove notification about old version relation in the review template; DONE
* Rim propose the possibility to add comments to the Review by QC member (by the 'add comment' feature). Community people can use the Discussion page
** (AP - enrico adds this feature);
* AP (enrico) Add the rights for certification to the EB member(s)
* Argumentation process (useful between reviewers and editors): Possibility of adding CICERO to the portal as an extension of semantic Wikimedia. We have to define and support argumentation process mechanisms for voting…
* Propose of a New Area. '''Session:''' related to the reviews and to the article; possibility to add arguments about a reviewsession

Review-Certification process:
* the author asks for review
** notifications(beginning of march):
*** to the EB mailing list
*** to the author
** Reviewer assignment (1 Week, will be checked if this amount of time is reasonable):
*** The EB member concerned asks (2-3) reviewers about their availability before assigning them.
*** Assignment based on quality member domain of expertise and the domain of the proposed pattern
*** AP (valentina) write an e-mail template for availability checking
*** AP - enrico add the isExpertOf property to the User template/form and a page for showing who is expert of what in the 'Domains' area
** Review task (3 Weeks – 1 month)
*** EB member will supervise
*** Three review scores:
**** (--) : crap => to reject
**** (-) : major revision => reiterate
**** (+) : need minor revision to be enhanced (reviewers should give recommendations & corrections)
**** (++) : need few revision almost ready for certification
** Argumentation Session (iterative process):
*** If (-): author correct and asks for a new review (the same reviewers will be assigned)
*** If (+)
*** In case of author disagreement (1 month discussion and fixing the final review decision):
**** Solicit author and reviewers to discuss considering the same evaluation criteria (! The review must consider the requirements of the creation of the pattern)
**** Assign other reviewers?
*** If (++): argumentation session should be faster for author to fix (1 day)
** Certification Process (after author fix) (1 month)
* Review schema form:
** Eva proposes to add a decision information field for positive/negative review (indicating the review score)
*** AP - Enrico: a new property for Review schema, HasDecision on the status of the pattern in the proposal
** Valentina proposes to add also a state of the submission field (reviewer assignment, review process, argumentation process, improvement process, certification process)
* AP - Enrico manages difference between article automatic editing when 'minor edit' (no new revision) and when 'edit' (new revision: only on certify action!).
* AP - Eva will review the review process, by testing it in the mirror site (/testarea)
* AP - Rim: create a page in the wiki that describes the review process.

(lunch)

* Overview of the Content OP pattern proposal Page and Form
* Francois ask how to inherit annotation of a pattern from an owl file.
** Valentina: there is an extension for it that works with the CP annotation schema, we can extend it for the Correspondence patterns.
* Valentina propose to discuss the Correspondence form via the mailing list.
* Discussion on the Annotation schema of the CP
** Aldo propose to start from the Content Patterns schema, because the most of the property defined there can fix with other kinds of pattern too,
** When defining forms for other types of patterns, some general annotations used for CP could be reused, other annotations have to be defined as specific to its kind of patterns,
** Francois, Valentina found overlapping between actual CP schema and the correspondence pattern descriptions.
** AP - Francois and Valentina will define a general metamodel for annotation schema of ontology design patterns ODP
** Member who wants to import its own annotation model to describe a proposed pattern could map it to the metamodel
** Svojtek present the issue of the relation between pattern definition and pattern formalization:
*** diagram is labelled as ''diagram of the pattern'' and not '' diagram of the OWL formalization''. He proposes to put the second.
*** Valentina agrees to clarify this relation, and adds that we are now addressing the ODP in the context of the Semantic Web
*** Enrico propose to add more implementations of a pattern, also software blocks (java classes for CP...);
*** Eva also noticed that the description of the objects are independents from the OWL language;
*** Decision token: finally the portal is on semantic web ODPs, and rdf/owl are the w3c standards for it. Anyway is important to support the most used languages;

Valentina illustrates the [[OPTypes|patterns' different types]]

Discussion about lexical issues on ODP taxonomy:
* (Valentina, Francois... others) changing the MappingOP type in the AlignmentOP and the relation with the Correspondence type (are they related? How?). Probably the Mapping term in the francois ontology corresponds with an Alignment in the ODP taxonomy. Mapping, finally is ambiguous term so it becomes Alignment
* Rim: evolution patterns can be intended as change management patterns and versioning patterns
** Valentina: we should be careful is to add elements in the ODP conceptualization by adding relations with other patterns

Responsibilities:
* Alignment patterns -> Francois
* Change managemenet patterns -> Rim
* Content OP -> Eva
* Process modeling patterns (re-engineering, modeling/content) -> Violeta, Gerd
** Content OP in the domain of business process management (BPM)
* Re-engineering patterns -> ?
* Linguistic patterns -> Wim Peters

Deadlines:
* Reviewing process:
** half of march for external user(s)
** 5th March the e-mail notification activation...

* New pattern definition: 7th March

Dissemination:
* Valentina summarize things done until now to disseminate ODP portal, and proposes
** A bulletin of the ODP initiative (a journal), a scientific publication related to the pattern propositions (best three certified patterns) (each six months/one year)
** Event: competition or Vocamp about the portal
** An Open source project
** AP (enrico,all) setup a page readable only by editorial member where everybody can put mailing lists
** Proposition of a pattern camp (similar as Vocamps)
** Workshops on ODPs (involving also authors of the proposals)
** AP (all) should post
** Communication from the portal for inviting and involving different communities: How to formulate => AP (all) prepare e-mail template for inviting people to the ODP community (via the mailing list)
** Which could be an alternative for the pattern visualization. Actually the portal ask for a generic image, but we are looking to a good tool for render automatically a diagram from the pattern definition.

'Ontology Design Patterns':EB-1st-f2f-2009Feb23

2009-03-02T14:04:46Z

RimDJEDIDI: /* Minutes */

__FORCETOC__

= First Face 2 Face meeting of odp Editorial Board =

=== Agenda ===

* [10.00-11.00] Introduction to the web site, roles, tasks, procedures, and support for ODP editorial board members (Valentina)
* [11.00-11.20] Coffee break
* [11.20- 12.20] Questions and discussion
* [12.20-13.00] Responsible person for ODP areas, plan (next 3 months) for bootstrapping ODP with Action Points
* [13.00-14.30] Lunch
* [14.30-15.00] Fix Review/Certification Procedure
* [15.00-15.20] Dissemination activities - status and proposals (Valentina)
* [15.20-16.20] Question and discussion with proposals
* [16.20-16.50] Plan (next three months)
* [16.50-17.00] Next (remote) meeting date

* [20.00] Dinner

=== Venue ===

The meeting will be held at the '''Institute for Cognitive Science and Technology''', '''Piaget''' room (first floor).

Via San Martino della Battaglia 44, Rome

=== Hotels ===

==== *** ====

'''Hotel Villa delle Rose'''
* Address: Via Vicenza 5
* Phone: +39-06-4451795

* Rates:
** Single room: Euro 75,00
** Double room: Euro 100,00
** Breakfast included

* Distance and Route: walking distance, 3 minutes

* Web site: http://www.villadellerose.it/it/index.htm

'''Hotel S. Marco'''
* Address: Via Villafranca 1
* Phone: +3906490437

* Services:
** Pay tv
** Internet access
** minibar
** From 29.01.2009 to 15.03.2009 (free of charge)

* Rates:
** Single room : Euro 80
** Double room single occupancy: Euro 90
** Double room : Euro 99,00

* Distance and route: 1 minute walking distance

* Web site: http://www.hotelsanmarcoroma.com/

'''Hotel Montecarlo'''
* Address: Via Palestro 17/a
* Phone: +39064460000

* Rates:
** Single room: Euro 70,00
** Double room :Euro 90,00

* Distance and route: 4 minutes walking distance

* Web site: http://laral.istc.cnr.it/address.htm

==== **** ====

'''Hotel Artemide'''

* Address: Via Nazionale 22
* Phone: +3906489911

* Services
** Internet access
** Mini-bar
** Room service
** Satellite TV
** Free daily newspaper

* Rates:
** Single room: Euro 170,00
** Double single use : Euro 170,00
** Breakfast included

* Distance and route: 10 minutes walking

* Web site: http://www.hotelartemide.it/en/index.htm

'''Hotel Cosmopolita'''
* Address: Via di Sant'Eufemia 5 (close to Piazza Venezia)
* Phone: +390699707606

* Services:
** Internet access
** Mini-bar
** Direct phone
** Satellite TV
** Room service

* Rates
** Single room : Euro 120,00
** Double room: Euro 130,00
** Breakfast included

Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini walk for 5 minutes.

* Web site: http://www.hotel-cosmopolita.com/

'''Hotel Pace Elvetia'''
* Address: Via IV Novembre 104
* Phone: +39066795105

* Services:
** Wi-Fi in the hall
** Bar and Rooftop Terrace
** Remote control satellite tv
** Minibar
** Direct-dial telephone

* Rates:
** Single room : Euro 80,00
** Double room: Euro 100,00
** Breakfast included

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini just walk for 5 minutes.

* Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

=== Editorial Board member ===
{{Group eb members}}

=== Attendees ===
* [[User:ValentinaPresutti| Valentina Presutti]]
* [[User:RimDJEDIDI| Rim Djedidi]]
* [[User:VojtechSvatek| Vojtech Svatek]]
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:EnricoDaga| Enrico Daga]]
* [[User:GerdGroener| Gerd Groener]]
* [[User:FrancoisScharffe| Francois Scharffe]]

=== Sunday dinner attendees ===

* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[USer:RimDJEDIDI| Rim Djedidi]]
* [[User:VojtechSvatek| Vojtech Svatek]] (coming quite late, after 11pm, if at all)
* <s>[[User:FrancoisScharffe| Francois Scharffe]]</s> (finally won't make it)

=== Monday dinner attendees ===
* The dinner will be held at [http://www.squisitalia.com/locale.php?id=922 "Osteria della Gensola"]
** Address: Piazza della Gensola 15 (in front of Isola Tiberina)
** google map path (from the meeting site): [http://maps.google.it/maps?f=q&source=s_q&hl=it&geocode=&q=from:+via+san+martino+della+battaglia,+Rome+to:+Piazza+della+Gensola,+15,+00153+Roma+RM&sll=41.89516,12.490125&sspn=0.030539,0.074587&ie=UTF8&z=14]
** From P.zza della Repubblica, take the BUS 'H' and wait for 4 stops, go out on p.zza Sonnino and do 250 meters
* [[USer:ValentinaPresutti| Valentina Presutti]]
* <s>[[User:VojtechSvatek| Vojtech Svatek]]</s> (unfortunately, Alitalia cancelled my flight and replaced with quite an early one for Tuesday, so I will have to go to bed very soon...)
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:GerdGroener| Gerd Groener]]
* [[USer:RimDJEDIDI| Rim Djedidi]]
* [[User:EnricoDaga|Enrico Daga]]

=== Process Modeling Pattern Seminar (attendees) ===
* [http://stlab.istc.cnr.it/index.php/ProcessModelingFeb2009 Seminar details]
* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:GerdGroener| Gerd Groener]]
* [[User:EnricoDaga|Enrico Daga]]
* [[User:RimDJEDIDI|Rim Djedidi]]

=== Minutes ===
Valentina introduce:
EB members (responsibilities on):
* content of the web site
* co-leading, share responsibility and tasks
* dissemination activities

Things todo:
* plan to integrate mailing-list & wiki
* define workflows for each action
* bootstrap web-site
* define new content actions
* area for good - 'beautiful' - ontologies (not patterns)
* add new types of patterns: Logical, Correspondence,
* Define responsible editors for:
** each type of pattern: Logical, Correspondence, Content, Architectural, Re-engineering;
** wrt Content Patterns, the most huge category, focused on specific domains. They need responsible editors for each domain(s);

Review/certification process:
* Community;
* Quality committee (distributed on kind of patterns and/or on kind of domain); (expert and authoritative reviewers, not to be charged too much of work but to be involved as light collaboration)
* Certification: useful for trust/provenance issues

Presentations:
- violeta: connections between patterns and business process modeling (content or re-engineering?)
- gerd: process modeling
- francois: correspondence patterns, patterns in ontology mapping
- eva: content patterns modeling and use
- rim: ontology evolution, change managements patterns (consistency check and maintenance), and e-business model content patterns
- svojtek (remotely connected): pattern recognition of logical/structural elements in ontologies; patterns connect ontologies / legacy systems (databases); recognition of bad practices and refactoring procedures in ontologies.

Others candidates for the editorial board (not attending):
* Mathieu D'Aquin ("beautiful ontologies")
* Denny Vrandecic (logical patterns)
* Tania Tudorache (Biomedical domain, workflows)
* ... others?

We need responsibles for:
# rdf patters: - actually the portal hosts OWL/DL patterns, but RDF patterns are useful for some requirements of expressivity more that computational.
# datasets: building and provide datasets that use ontology design patterns (useful for benchmarking use...)
# usability-profiling, collecting good practices on annotation of patterns
# architectural, how to organize the shape of an ontology? Even if the ontology is modular, it has some architecture (maybe the same that takes care of logical ones)

Things to do next three months:
- Definition of new area
- Contribute in taking dissemination actions

AP:
* put guidelines for forms specifications
* put the list

valentina illustrates the definition of new type of patterns procedure (''will be a wiki page for it'')

(coffee break)

Procedure of proposing an improvement for the web site through the Development area

Valentina shows:
* how to login to the testarea site
* how to submit a new development task
** Form definitions should have a description of the fields related to the semantic properties (field -> SemanticProperty):
*** SemanticProperty already exists: see List of Categories, List of properties
*** SemanticProperty doesn’t exist: to be created
**** Always defining a description for a property (it will be displayed as pop-up tool tips
**** Convention of naming SemanticProperty will be online
* AP (enrico): add the name of the submitter in the list of tasks
* (AP enrico) -> mailing list watching some pages (feedback, developments)
** It will be soon notification service to EB when new user feedback through mailing list and also as a new submitted task (Always take aware about feedbacks, user feedbacks are useful for EB and could be promoted to task)
* NOTE: Patterns could have relations between each others => to mention explicitly when created

Description of the reviewing process by the evaluation
** AP: add autocompletion in the assign review special page;
** NOTE: actually there is no mail notification, so we will start it on the second half of March; BUT if some EB member wants to start the process he can, has to notify personally the reviewer;
** AP (Aldo, Valentina, Eva): define review schema for content patterns;
** A pattern author can put a proposal without asking for a review (if not yet ready/mature for evaluation process) and improve it after
** AP (enrico) fix a bug on the evaluation template for reviews;
** A review must contain:
*** rationale justifications/explanations
*** recommendations for pattern improvement/correction
*** using SemanticProperties

** AP (enrico): remove notification about old version relation in the review template; DONE
** Rim propose the possibility to add comments to the Review by QC member (by the 'add comment' feature). Community people can use the Discussion page
*** (AP - enrico adds this feature);
** AP (enrico) Add the rights for certification to the EB member(s)
** Argumentation process (useful between reviewers and editors): Possibility of adding CICERO to the portal as an extension of semantic Wikimedia. We have to define and support argumentation process mechanisms for voting…
** Propose of a New Area. '''Session:''' related to the reviews and to the article; possibility to add arguments about a reviewsession

Review-Certification process:
* the author asks for review
** notifications(beginning of march):
*** to the EB mailing list
*** to the author
** Reviewer assignment (1 Week, will be checked if this amount of time is reasonable):
*** The EB member concerned asks (2-3) reviewers about their availability before assigning them.
*** Assignment based on quality member domain of expertise and the domain of the proposed pattern
*** AP (valentina) write an e-mail template for availability checking
*** AP - enrico add the isExpertOf property to the User template/form and a page for showing who is expert of what in the 'Domains' area
** Review task (3 Weeks – 1 month)
*** EB member will supervise
*** Three review scores:
**** (--) : crap => to reject
**** (-) : major revision => reiterate
**** (+) : need minor revision to be enhanced (reviewers should give recommendations & corrections)
**** (++) : need few revision almost ready for certification
** Argumentation Session (iterative process):
*** If (-): author correct and asks for a new review (the same reviewers will be assigned)
*** If (+)
*** In case of author disagreement (1 month discussion and fixing the final review decision):
**** Solicit author and reviewers to discuss considering the same evaluation criteria (! The review must consider the requirements of the creation of the pattern)
**** Assign other reviewers?
*** If (++): argumentation session should be faster for author to fix (1 day)
** Certification Process (after author fix) (1 month)
* Review schema form:
** Eva proposes to add a decision information field for positive/negative review (indicating the review score)
*** AP - Enrico: a new property for Review schema, HasDecision on the status of the pattern in the proposal
** Valentina proposes to add also a state of the submission field (reviewer assignment, review process, argumentation process, improvement process, certification process)
* AP - Enrico manages difference between article automatic editing when 'minor edit' (no new revision) and when 'edit' (new revision: only on certify action!).
* AP - Eva will review the review process, by testing it in the mirror site (/testarea)
* AP - Rim: create a page in the wiki that describes the review process.

(lunch)

* Overview of the Content OP pattern proposal Page and Form
* Francois ask how to inherit annotation of a pattern from an owl file.
** Valentina: there is an extension for it that works with the CP annotation schema, we can extend it for the Correspondence patterns.
* Valentina propose to discuss the Correspondence form via the mailing list.
* Discussion on the Annotation schema of the CP
** Aldo propose to start from the Content Patterns schema, because the most of the property defined there can fix with other kinds of pattern too,
** When defining forms for other types of patterns, some general annotations used for CP could be reused, other annotations have to be defined as specific to its kind of patterns,
** Francois, Valentina found overlapping between actual CP schema and the correspondence pattern descriptions.
** AP - Francois and Valentina will define a general metamodel for annotation schema of ontology design patterns ODP
** Member who wants to import its own annotation model to describe a proposed pattern could map it to the metamodel
** Svojtek present the issue of the relation between pattern definition and pattern formalization:
*** diagram is labelled as ''diagram of the pattern'' and not '' diagram of the OWL formalization''. He proposes to put the second.
*** Valentina agrees to clarify this relation, and adds that we are now addressing the ODP in the context of the Semantic Web
*** Enrico propose to add more implementations of a pattern, also software blocks (java classes for CP...);
*** Eva also noticed that the description of the objects are independents from the OWL language;
*** Decision token: finally the portal is on semantic web ODPs, and rdf/owl are the w3c standards for it. Anyway is important to support the most used languages;

Valentina illustrates the [[OPTypes|patterns' different types]]

Discussion about lexical issues on ODP taxonomy:
* (Valentina, Francois... others) changing the MappingOP type in the AlignmentOP and the relation with the Correspondence type (are they related? How?). Probably the Mapping term in the francois ontology corresponds with an Alignment in the ODP taxonomy. Mapping, finally is ambiguous term so it becomes Alignment
* Rim: evolution patterns can be intended as change management patterns and versioning patterns
** Valentina: we should be careful is to add elements in the ODP conceptualization by adding relations with other patterns

Responsibilities:
* Alignment patterns -> Francois
* Change managemenet patterns -> Rim
* Content OP -> Eva
* Process modeling patterns (re-engineering, modeling/content) -> Violeta, Gerd
** Content OP in the domain of business process management (BPM)
* Re-engineering patterns -> ?
* Linguistic patterns -> Wim Peters

Deadlines:
* Reviewing process:
** half of march for external user(s)
** 5th March the e-mail notification activation...

* New pattern definition: 7th March

Dissemination:
* Valentina summarize things done until now to disseminate ODP portal, and proposes
** A bulletin of the ODP initiative (a journal), a scientific publication related to the pattern propositions (best three certified patterns) (each six months/one year)
** Event: competition or Vocamp about the portal
** An Open source project
** AP (enrico,all) setup a page readable only by editorial member where everybody can put mailing lists
** Proposition of a pattern camp (similar as Vocamps)
** Workshops on ODPs (involving also authors of the proposals)
** AP (all) should post
** Communication from the portal for inviting and involving different communities: How to formulate => AP (all) prepare e-mail template for inviting people to the ODP community (via the mailing list)
** Which could be an alternative for the pattern visualization. Actually the portal ask for a generic image, but we are looking to a good tool for render automatically a diagram from the pattern definition.

'Ontology Design Patterns':EB-1st-f2f-2009Feb23

2009-02-24T08:50:31Z

RimDJEDIDI: /* Process Modeling Pattern Seminar (attendees) */

__FORCETOC__

= First Face 2 Face meeting of odp Editorial Board =

=== Agenda ===

* [10.00-11.00] Introduction to the web site, roles, tasks, procedures, and support for ODP editorial board members (Valentina)
* [11.00-11.20] Coffee break
* [11.20- 12.20] Questions and discussion
* [12.20-13.00] Responsible person for ODP areas, plan (next 3 months) for bootstrapping ODP with Action Points
* [13.00-14.30] Lunch
* [14.30-15.00] Fix Review/Certification Procedure
* [15.00-15.20] Dissemination activities - status and proposals (Valentina)
* [15.20-16.20] Question and discussion with proposals
* [16.20-16.50] Plan (next three months)
* [16.50-17.00] Next (remote) meeting date

* [20.00] Dinner

=== Venue ===

The meeting will be held at the '''Institute for Cognitive Science and Technology''', '''Piaget''' room (first floor).

Via San Martino della Battaglia 44, Rome

=== Hotels ===

==== *** ====

'''Hotel Villa delle Rose'''
* Address: Via Vicenza 5
* Phone: +39-06-4451795

* Rates:
** Single room: Euro 75,00
** Double room: Euro 100,00
** Breakfast included

* Distance and Route: walking distance, 3 minutes

* Web site: http://www.villadellerose.it/it/index.htm

'''Hotel S. Marco'''
* Address: Via Villafranca 1
* Phone: +3906490437

* Services:
** Pay tv
** Internet access
** minibar
** From 29.01.2009 to 15.03.2009 (free of charge)

* Rates:
** Single room : Euro 80
** Double room single occupancy: Euro 90
** Double room : Euro 99,00

* Distance and route: 1 minute walking distance

* Web site: http://www.hotelsanmarcoroma.com/

'''Hotel Montecarlo'''
* Address: Via Palestro 17/a
* Phone: +39064460000

* Rates:
** Single room: Euro 70,00
** Double room :Euro 90,00

* Distance and route: 4 minutes walking distance

* Web site: http://laral.istc.cnr.it/address.htm

==== **** ====

'''Hotel Artemide'''

* Address: Via Nazionale 22
* Phone: +3906489911

* Services
** Internet access
** Mini-bar
** Room service
** Satellite TV
** Free daily newspaper

* Rates:
** Single room: Euro 170,00
** Double single use : Euro 170,00
** Breakfast included

* Distance and route: 10 minutes walking

* Web site: http://www.hotelartemide.it/en/index.htm

'''Hotel Cosmopolita'''
* Address: Via di Sant'Eufemia 5 (close to Piazza Venezia)
* Phone: +390699707606

* Services:
** Internet access
** Mini-bar
** Direct phone
** Satellite TV
** Room service

* Rates
** Single room : Euro 120,00
** Double room: Euro 130,00
** Breakfast included

Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini walk for 5 minutes.

* Web site: http://www.hotel-cosmopolita.com/

'''Hotel Pace Elvetia'''
* Address: Via IV Novembre 104
* Phone: +39066795105

* Services:
** Wi-Fi in the hall
** Bar and Rooftop Terrace
** Remote control satellite tv
** Minibar
** Direct-dial telephone

* Rates:
** Single room : Euro 80,00
** Double room: Euro 100,00
** Breakfast included

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini just walk for 5 minutes.

* Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

=== Editorial Board member ===
{{Group eb members}}

=== Attendees ===
* [[User:ValentinaPresutti| Valentina Presutti]]
* [[User:RimDJEDIDI| Rim Djedidi]]
* [[User:VojtechSvatek| Vojtech Svatek]]
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:EnricoDaga| Enrico Daga]]
* [[User:GerdGroener| Gerd Groener]]
* [[User:FrancoisScharffe| Francois Scharffe]]

=== Sunday dinner attendees ===

* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[USer:RimDJEDIDI| Rim Djedidi]]
* [[User:VojtechSvatek| Vojtech Svatek]] (coming quite late, after 11pm, if at all)
* <s>[[User:FrancoisScharffe| Francois Scharffe]]</s> (finally won't make it)

=== Monday dinner attendees ===
* The dinner will be held at [http://www.squisitalia.com/locale.php?id=922 "Osteria della Gensola"]
** Address: Piazza della Gensola 15 (in front of Isola Tiberina)
** google map path (from the meeting site): [http://maps.google.it/maps?f=q&source=s_q&hl=it&geocode=&q=from:+via+san+martino+della+battaglia,+Rome+to:+Piazza+della+Gensola,+15,+00153+Roma+RM&sll=41.89516,12.490125&sspn=0.030539,0.074587&ie=UTF8&z=14]
** From P.zza della Repubblica, take the BUS 'H' and wait for 4 stops, go out on p.zza Sonnino and do 250 meters
* [[USer:ValentinaPresutti| Valentina Presutti]]
* <s>[[User:VojtechSvatek| Vojtech Svatek]]</s> (unfortunately, Alitalia cancelled my flight and replaced with quite an early one for Tuesday, so I will have to go to bed very soon...)
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:GerdGroener| Gerd Groener]]
* [[USer:RimDJEDIDI| Rim Djedidi]]
* [[User:EnricoDaga|Enrico Daga]]

=== Process Modeling Pattern Seminar (attendees) ===
* [http://stlab.istc.cnr.it/index.php/ProcessModelingFeb2009 Seminar details]
* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:GerdGroener| Gerd Groener]]
* [[User:EnricoDaga|Enrico Daga]]
* [[User:RimDJEDIDI|Rim Djedidi]]

=== Minutes ===
Valentina introduce:
EB members (rspnsabilities on):
* conent of the web site
* co-leading, share responsability and tasks
* dissemination activities

Things todo:
* plan to integrate mailing-list & wiki
* define workflows for each action
* bootrap web-site
* define new content actions
* area for good - 'beautiful' - ontologies (not patterns)
* add new types of patterns: Logical, Correspondance,
* Define responsable editors for:
** each type of pattern: Logical, Correspondance, Content, Architectural, Reengeneering;
** wrt Content Patterns, the most huge category, focused on specific domains. They need responsable editors for each domain(s);

Review/certification process:
* Community;
* Quality commettee (distributed on kind of patterns and/or on kind of domain); (expert and authoritative reviewers, not to be charged too much of work but to be involved as light collaboration)
* Certification: useful for trust/provenance issues

Presentations:
- violeta: connections between patterns and business process modeling (content or re-engeneering?)
- gard: process modeling
- francois: correspondance patterns, patterns in ontology mapping
- eva: content patterns modeling and use
- rym: ontology evolution, change managements patterns (check consistency, maintainance tasks), and business modeling ontology/patterns
- svojtek (remotely connected): pattern recognition of logical/structual elements in ontologies; patterns connect ontologies / legacy systems (databases); recognition of bad practices and refactoring procedures in ontologies.

Others candidates for the editorial board (not attending):
* Mathieu D'Aquin ("beautiful ontologies")
* Denny Vrandecic (logical patterns)
* Tania Tudorache (Biomedical domain, workflows)
* ... others?

We need responsables for:
# rdf patters: - actually the portal hosts OWL/DL patterns, but RDF patterns are useful for some requirements of expressivity more that computational.
# datasets: building and provide datasets that use ontology design patterns (useful for benchmarking use...)
# usability-profiling, collecting good practices on annotation of patterns
# architectural, how to organize the shape of an ontology? Even if the ontology is modular, it has some architecture (maybe the same that takes care of logical ones)

Things to do next three months:
- Definition of new area

AP:
* put guidelines for forms specifications
* put the list

valentina illustrates the definition of new type of patterns procedure (''will be a wiki page for it'')

(coffee break)

Procedure of proposing an improvement for the web site through the Development area

Valentina shows:
* how to login to the testarea site
* how to submit a new development task
** Form definitions should have a description of the fileds related to the semnatc property:
*** field -> semanticProperty (to be creaed/already present)
* AP (enrico): add the name of the submitter in the list of tasks
* (AP enrico) -> mailing list watching some pages (feedback, developments)

Description of the reviewing process by the evaluation
** AP: add autocompletion in the assign review special page;
** NOTE: actually there is no mail notification, so we will start it on the second half of March; BUT if some eb member wants to start the process he can, has to notify personally the reviewer;
** AP (Aldo, Valentina, Eva): define review schema for content patterns;
** AP (enrico) fix a bug on the evaluation template for reviews;
** AP (enrico): remove notification about old version relation in the review template; DONE
** Rym propose the possibility to add comments to the Review by QC member (by the 'add comment' feature). Community people can use the Discussion page
*** (AP - enrico adds this feaature);
** AP (enrico) Add the rights for certification to the eb member(s)
** Possibility of adding CICERO to the portal.
** Propose of a New Area. '''Session:''' related to the reviews and to the article; possibiliy to add arguments about a reviewsession

Certification process:
* the author asks for review
** notifications:
*** to the mailing list
*** to the author
** wait for assignments (1 week, will be checked if this amount of time is reasonable)
*** AP (valentina) write an e-mail template
** for a review to be done
** (eb member will supervise)
** If there is agreement on the proposal, the certification should be addressed in 1 month
** If there is dis-agreement on the proposal, the discussion should be closed in 1 month
** If the pattern needs to be enhancements

** Eva propose to add a field for positive/negative review.
*** Valentina propose to add it to the review schema (form)
*** State of the submission

* AP - enrico add the isExpertOf property to the User template/form and a page for showing who is expert of what in the 'Domains' area
* AP - enrico manage difference between article automatic editing when 'minor edit' (no new revision) and when 'edit' (new revision: only on certify action!).
* AP - Eva will review the '''review process''', by testing it in the mirror site (/testarea)
* AP - enrico: a new property for Review schema, '''hasdecision''' (Eva proposed) on the status of the pattern in the proposal
* AP - Rym: create a page in the wiki that describes the procedure of pattern proposal and evaluation

(launch)

* Overview of the Content OP pattern proposal Page and Form
* Francois ask how to inherit annotation of a pattern from an owl file.
** Valentina: there is an extension for it that works with the CP annotation schema, we can extend it for the Correspondance patterns.
* Valentina propose to discuss the Correspondance form via the mailing list.
* Discussion on the Annotation schema of the CP
** Aldo propose to start from the Content Patterns schema, becouse the most of the property defined there can fix with other kinds of pattern too.
** Francois, Valentina found overlapping between actual CP schema and the correspondance pattern descriptions.
** AP - Valentina and Francois define a more general schema for ontology design patterns
** Svojtek present the issue of the relation between pattern definition and pattern formalization:
*** diagram is labelled as ''diagram of the pattern'' and not '' diagram of the OWL formalisation''. He proposes to put the second.
*** Valentina agrees to clearify this relation, and adds that we are now addressing the ODP in the context of the Semantic Web
*** Enrico propose to add more implementations of a pattern, also software blocks (java classes for CP...);
*** Eva also noticed that the description of the objects are independents from the OWL language;
*** Decision token: finally the portal is on semantic web ODPs, and rdf/owl are the w3c standards for it. Anyway is important to support the most used languages;

Valentina illustrates the [[OPTypes|patterns' different types]]

Discussion about lexical issues on ODP taxonomy:
* (Valentina, Froncois... others) changing the MappingOP type in the AlignmentOP and the relation with the Correspondance type (are they related? How?). Probably the Mapping term in the francois ontology corresponds with an Alignment in the ODP taxonomy. Mapping, finally is ambigous term so it becomes Alignement
* Rym: evolution patterns can be intended as change management patterns
** Valentina: we should be carefoul is to add elements in the ODP conceptualization by adding relations with other patterns

Responsabilities:
* Alignment patterns -> Francois
* Change managemenet patterns -> Rym
* Content OP -> Eva
* Process modeling patterns (re-engeneering, modeling/content) -> Violeta, Gerd
** Content OP in the domain of business process management (BPM)
* Re-engeneering patterns -> ?
* Linguistic patterns -> Wim Peters

Deadline for reviewing process:
* half of march for external user(s): waiting for the e-mail notification activation...
* 5th March

Deadline for new pattern definition:
* 7th March

Dissamination:
* Valentina summarize things done until now to dissaminate ODP portal, and proposes
** A buletin of the ODP initiative (a journal), a scientific publication related to the pattern propositions (each six months/one year)
** Event: competition or voccamp about the portal
** An Open source project
** AP (enrico,all) setup a page readable only by editorial member where everybody can put mailing lists
** Proposition of a pattern camp (similar as voccamps)
** Workshops on ODPs (involving also authors of the proposals)
** AP (all) should post
** AP (all) prepare e-mail template for inviting people to the ODP community (via the mailing list)

** Wich could be an alternative for the pattern visualization. Actually the portal ask for a generic image, but we are looking to a good tool for render automatically a diagram from the pattern definition.

'Ontology Design Patterns':EB-1st-f2f-2009Feb23

2009-02-06T10:04:10Z

RimDJEDIDI: /* Monday dinner attendees */

__FORCETOC__

= First Face 2 Face meeting of odp Editorial Board =

=== Agenda ===

=== Venue ===

The meeting will be held at the '''Institute for Cognitive Science and Technology''', '''Piaget''' room (first floor).

Via San Martino della Battaglia 44, Rome

=== Hotels ===

==== *** ====

'''Hotel Villa delle Rose'''
* Address: Via Vicenza 5
* Phone: +39-06-4451795

* Rates:
** Single room: Euro 75,00
** Double room: Euro 100,00
** Breakfast included

* Distance and Route: walking distance, 3 minutes

* Web site: http://www.villadellerose.it/it/index.htm

'''Hotel S. Marco'''
* Address: Via Villafranca 1
* Phone: +3906490437

* Services:
** Pay tv
** Internet access
** minibar
** From 29.01.2009 to 15.03.2009 (free of charge)

* Rates:
** Single room : Euro 80
** Double room single occupancy: Euro 90
** Double room : Euro 99,00

* Distance and route: 1 minute walking distance

* Web site: http://www.hotelsanmarcoroma.com/

'''Hotel Montecarlo'''
* Address: Via Palestro 17/a
* Phone: +39064460000

* Rates:
** Single room: Euro 70,00
** Double room :Euro 90,00

* Distance and route: 4 minutes walking distance

* Web site: http://laral.istc.cnr.it/address.htm

==== **** ====

'''Hotel Artemide'''

* Address: Via Nazionale 22
* Phone: +3906489911

* Services
** Internet access
** Mini-bar
** Room service
** Satellite TV
** Free daily newspaper

* Rates:
** Single room: Euro 170,00
** Double single use : Euro 170,00
** Breakfast included

* Distance and route: 10 minutes walking

* Web site: http://www.hotelartemide.it/en/index.htm

'''Hotel Cosmopolita'''
* Address: Via di Sant'Eufemia 5 (close to Piazza Venezia)
* Phone: +390699707606

* Services:
** Internet access
** Mini-bar
** Direct phone
** Satellite TV
** Room service

* Rates
** Single room : Euro 120,00
** Double room: Euro 130,00
** Breakfast included

Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini walk for 5 minutes.

* Web site: http://www.hotel-cosmopolita.com/

'''Hotel Pace Elvetia'''
* Address: Via IV Novembre 104
* Phone: +39066795105

* Services:
** Wi-Fi in the hall
** Bar and Rooftop Terrace
** Remote control satellite tv
** Minibar
** Direct-dial telephone

* Rates:
** Single room : Euro 80,00
** Double room: Euro 100,00
** Breakfast included

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini just walk for 5 minutes.

* Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

=== Editorial Board member ===
{{Group eb members}}

=== Attendees ===
* [[User:ValentinaPresutti| Valentina Presutti]]
* [[User:RimDJEDIDI| Rim Djedidi]]
* [[User:VojtechSvatek| Vojtech Svatek]]
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:EnricoDaga| Enrico Daga]]
* [[User:GerdGroener| Gerd Groener]]

=== Sunday dinner attendees ===

* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[USer:RimDJEDIDI| Rim Djedidi]]
* [[User:VojtechSvatek| Vojtech Svatek]] (coming quite late, after 11pm, if at all)

=== Monday dinner attendees ===
* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[User:VojtechSvatek| Vojtech Svatek]]
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:GerdGroener| Gerd Groener]]
* [[USer:RimDJEDIDI| Rim Djedidi]]

=== Process Modeling Pattern Seminar (attendees) ===
* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[User:VioletaDamjanovic| Violeta Damjanovic]]
* [[User:GerdGroener| Gerd Groener]]

=== Minutes ===

'Ontology Design Patterns':EB-1st-f2f-2009Feb23

2009-02-04T14:59:54Z

RimDJEDIDI: /* Sunday dinner attendees */

__FORCETOC__

= First Face 2 Face meeting of odp Editorial Board =

=== Agenda ===

=== Venue ===

The meeting will be held at the '''Institute for Cognitive Science and Technology''', '''Piaget''' room (first floor).

Via San Martino della Battaglia 44, Rome

=== Hotels ===

==== *** ====

'''Hotel Villa delle Rose'''
* Address: Via Vicenza 5
* Phone: +39-06-4451795

* Rates:
** Single room: Euro 75,00
** Double room: Euro 100,00
** Breakfast included

* Distance and Route: walking distance, 3 minutes

* Web site: http://www.villadellerose.it/it/index.htm

'''Hotel S. Marco'''
* Address: Via Villafranca 1
* Phone: +3906490437

* Services:
** Pay tv
** Internet access
** minibar
** From 29.01.2009 to 15.03.2009 (free of charge)

* Rates:
** Single room : Euro 80
** Double room single occupancy: Euro 90
** Double room : Euro 99,00

* Distance and route: 1 minute walking distance

* Web site: http://www.hotelsanmarcoroma.com/

'''Hotel Montecarlo'''
* Address: Via Palestro 17/a
* Phone: +39064460000

* Rates:
** Single room: Euro 70,00
** Double room :Euro 90,00

* Distance and route: 4 minutes walking distance

* Web site: http://laral.istc.cnr.it/address.htm

==== **** ====

'''Hotel Artemide'''

* Address: Via Nazionale 22
* Phone: +3906489911

* Services
** Internet access
** Mini-bar
** Room service
** Satellite TV
** Free daily newspaper

* Rates:
** Single room: Euro 170,00
** Double single use : Euro 170,00
** Breakfast included

* Distance and route: 10 minutes walking

* Web site: http://www.hotelartemide.it/en/index.htm

'''Hotel Cosmopolita'''
* Address: Via di Sant'Eufemia 5 (close to Piazza Venezia)
* Phone: +390699707606

* Services:
** Internet access
** Mini-bar
** Direct phone
** Satellite TV
** Room service

* Rates
** Single room : Euro 120,00
** Double room: Euro 130,00
** Breakfast included

Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini walk for 5 minutes.

* Web site: http://www.hotel-cosmopolita.com/

'''Hotel Pace Elvetia'''
* Address: Via IV Novembre 104
* Phone: +39066795105

* Services:
** Wi-Fi in the hall
** Bar and Rooftop Terrace
** Remote control satellite tv
** Minibar
** Direct-dial telephone

* Rates:
** Single room : Euro 80,00
** Double room: Euro 100,00
** Breakfast included

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini just walk for 5 minutes.

* Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

=== Editorial Board member ===
{{Group eb members}}

=== Attendees ===
* [[User:ValentinaPresutti| Valentina Presutti]]
* [[User:RimDJEDIDI| Rim Djedidi]]

=== Sunday dinner attendees ===

* [[USer:ValentinaPresutti| Valentina Presutti]]
* [[USer:RimDJEDIDI| Rim Djedidi]]

=== Monday dinner attendees ===
* [[USer:ValentinaPresutti| Valentina Presutti]]

=== Process Modeling Pattern Seminar (attendees) ===
* [[USer:ValentinaPresutti| Valentina Presutti]]

=== Minutes ===

'Ontology Design Patterns':EB-1st-f2f-2009Feb23

2009-02-04T14:58:39Z

RimDJEDIDI: /* Attendees */

__FORCETOC__

= First Face 2 Face meeting of odp Editorial Board =

=== Agenda ===

=== Venue ===

The meeting will be held at the '''Institute for Cognitive Science and Technology''', '''Piaget''' room (first floor).

Via San Martino della Battaglia 44, Rome

=== Hotels ===

==== *** ====

'''Hotel Villa delle Rose'''
* Address: Via Vicenza 5
* Phone: +39-06-4451795

* Rates:
** Single room: Euro 75,00
** Double room: Euro 100,00
** Breakfast included

* Distance and Route: walking distance, 3 minutes

* Web site: http://www.villadellerose.it/it/index.htm

'''Hotel S. Marco'''
* Address: Via Villafranca 1
* Phone: +3906490437

* Services:
** Pay tv
** Internet access
** minibar
** From 29.01.2009 to 15.03.2009 (free of charge)

* Rates:
** Single room : Euro 80
** Double room single occupancy: Euro 90
** Double room : Euro 99,00

* Distance and route: 1 minute walking distance

* Web site: http://www.hotelsanmarcoroma.com/

'''Hotel Montecarlo'''
* Address: Via Palestro 17/a
* Phone: +39064460000

* Rates:
** Single room: Euro 70,00
** Double room :Euro 90,00

* Distance and route: 4 minutes walking distance

* Web site: http://laral.istc.cnr.it/address.htm

==== **** ====

'''Hotel Artemide'''

* Address: Via Nazionale 22
* Phone: +3906489911

* Services
** Internet access
** Mini-bar
** Room service
** Satellite TV
** Free daily newspaper

* Rates:
** Single room: Euro 170,00
** Double single use : Euro 170,00
** Breakfast included

* Distance and route: 10 minutes walking

* Web site: http://www.hotelartemide.it/en/index.htm

'''Hotel Cosmopolita'''
* Address: Via di Sant'Eufemia 5 (close to Piazza Venezia)
* Phone: +390699707606

* Services:
** Internet access
** Mini-bar
** Direct phone
** Satellite TV
** Room service

* Rates
** Single room : Euro 120,00
** Double room: Euro 130,00
** Breakfast included

Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini walk for 5 minutes.

* Web site: http://www.hotel-cosmopolita.com/

'''Hotel Pace Elvetia'''
* Address: Via IV Novembre 104
* Phone: +39066795105

* Services:
** Wi-Fi in the hall
** Bar and Rooftop Terrace
** Remote control satellite tv
** Minibar
** Direct-dial telephone

* Rates:
** Single room : Euro 80,00
** Double room: Euro 100,00
** Breakfast included

* Distance and route: Take the bus 40 in Piazza Venezia and get off after three stops at Termini Station. From Termini just walk for 5 minutes.

* Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp

=== Editorial Board member ===
{{Group eb members}}

=== Attendees ===
* [[User:ValentinaPresutti| Valentina Presutti]]
* [[User:RimDJEDIDI| Rim Djedidi]]

=== Sunday dinner attendees ===

* [[USer:ValentinaPresutti| Valentina Presutti]]

=== Monday dinner attendees ===
* [[USer:ValentinaPresutti| Valentina Presutti]]

=== Process Modeling Pattern Seminar (attendees) ===
* [[USer:ValentinaPresutti| Valentina Presutti]]

=== Minutes ===

User:RimDJEDIDI

2009-02-04T14:42:32Z

RimDJEDIDI:

{{User Template
|FirstName=Rim
|LastName=DJEDIDI
|Genre=Female
|Picture=ODPUser.png
|Organization=Computer Science Department Supélec (Gif sur Yvette)
|OrganizationType=Educational Training and Research Institution
|Country=France (FR)
|Role=PhD Student
}}
{{Account Request Template
|Motivation=I work on OWL ontology change management patterns. My main motivation is to interact with the ODP community to share modelling experience, propose ontology patterns and have feedback.
|PossibleMainContribution=To have some help to solve modeling problems, To help other users to solve modeling problems
|DomainsOfInterest=Community:Business, Community:Ontology
|HowDidIKnowAbout=conference/public events, surfing the web
}}
[[Category:EBMember]]