EnricoDaga (Talk | contribs) (→Minutes) |
RimDJEDIDI (Talk | contribs) (→Minutes) |
||
(9 intermediate revisions by 2 users not shown) | |||
Line 159: | Line 159: | ||
* The dinner will be held at [http://www.squisitalia.com/locale.php?id=922 "Osteria della Gensola"] | * 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) | ** 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]] | * [[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...) | * <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...) | ||
Line 172: | Line 174: | ||
* [[User:GerdGroener| Gerd Groener]] | * [[User:GerdGroener| Gerd Groener]] | ||
* [[User:EnricoDaga|Enrico Daga]] | * [[User:EnricoDaga|Enrico Daga]] | ||
+ | * [[User:RimDJEDIDI|Rim Djedidi]] | ||
=== Minutes === | === Minutes === | ||
Valentina introduce: | Valentina introduce: | ||
− | EB members ( | + | EB members (responsibilities on): |
− | * | + | * content of the web site |
− | * co-leading, share | + | * co-leading, share responsibility and tasks |
* dissemination activities | * dissemination activities | ||
Line 183: | Line 186: | ||
* plan to integrate mailing-list & wiki | * plan to integrate mailing-list & wiki | ||
* define workflows for each action | * define workflows for each action | ||
− | * | + | * bootstrap web-site |
* define new content actions | * define new content actions | ||
* area for good - 'beautiful' - ontologies (not patterns) | * area for good - 'beautiful' - ontologies (not patterns) | ||
− | * add new types of patterns: Logical, | + | * add new types of patterns: Logical, Correspondence, |
− | * Define | + | * Define responsible editors for: |
− | ** each type of pattern: Logical, | + | ** each type of pattern: Logical, Correspondence, Content, Architectural, Re-engineering; |
− | ** wrt Content Patterns, the most huge category, focused on specific domains. They need | + | ** wrt Content Patterns, the most huge category, focused on specific domains. They need responsible editors for each domain(s); |
Review/certification process: | Review/certification process: | ||
* Community; | * Community; | ||
− | * Quality | + | * 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 | * Certification: useful for trust/provenance issues | ||
Presentations: | Presentations: | ||
− | - violeta: connections between patterns and business process modeling (content or re- | + | - violeta: connections between patterns and business process modeling (content or re-engineering?) |
− | - | + | - gerd: process modeling |
− | - francois: | + | - francois: correspondence patterns, patterns in ontology mapping |
- eva: content patterns modeling and use | - 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/ | + | - 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): | Others candidates for the editorial board (not attending): | ||
Line 210: | Line 213: | ||
* ... others? | * ... others? | ||
− | We need | + | 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. | # 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...) | # datasets: building and provide datasets that use ontology design patterns (useful for benchmarking use...) | ||
Line 218: | Line 221: | ||
Things to do next three months: | Things to do next three months: | ||
- Definition of new area | - Definition of new area | ||
+ | - Contribute in taking dissemination actions | ||
AP: | AP: | ||
Line 232: | Line 236: | ||
* how to login to the testarea site | * how to login to the testarea site | ||
* how to submit a new development task | * how to submit a new development task | ||
− | ** Form definitions should have a description of the | + | ** 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): add the name of the submitter in the list of tasks | ||
* (AP enrico) -> mailing list watching some pages (feedback, developments) | * (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 | 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; | + | * 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 |
− | + | ||
− | Certification process: | + | * 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 | * the author asks for review | ||
− | ** notifications: | + | ** notifications(beginning of march): |
− | *** to the mailing list | + | *** to the EB mailing list |
*** to the author | *** to the author | ||
− | ** | + | ** Reviewer assignment (1 Week, will be checked if this amount of time is reasonable): |
− | *** AP (valentina) write an e-mail template | + | *** 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 |
− | ** If | + | ** Review task (3 Weeks – 1 month) |
− | ** | + | *** EB member will supervise |
− | + | *** Three review scores: | |
− | ** Eva | + | **** (--) : 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): |
− | * AP - | + | *** If (-): author correct and asks for a new review (the same reviewers will be assigned) |
− | * AP - Eva will review the | + | *** If (+) |
− | * AP - | + | *** 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 | * Overview of the Content OP pattern proposal Page and Form | ||
* Francois ask how to inherit annotation of a pattern from an owl file. | * 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 | + | ** 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 | + | * Valentina propose to discuss the Correspondence form via the mailing list. |
* Discussion on the Annotation schema of the CP | * Discussion on the Annotation schema of the CP | ||
− | ** Aldo propose to start from the Content Patterns schema, | + | ** 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, |
− | ** Francois, Valentina found overlapping between actual CP schema and the | + | ** 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, |
− | ** AP - | + | ** 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: | ** 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 | + | *** diagram is labelled as ''diagram of the pattern'' and not '' diagram of the OWL formalization''. He proposes to put the second. |
− | *** Valentina agrees to | + | *** 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...); | *** 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; | *** Eva also noticed that the description of the objects are independents from the OWL language; | ||
Line 292: | Line 319: | ||
Discussion about lexical issues on ODP taxonomy: | Discussion about lexical issues on ODP taxonomy: | ||
− | * (Valentina, | + | * (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 | + | ** Valentina: we should be careful is to add elements in the ODP conceptualization by adding relations with other patterns |
− | + | Responsibilities: | |
* Alignment patterns -> Francois | * Alignment patterns -> Francois | ||
− | * Change managemenet patterns -> | + | * Change managemenet patterns -> Rim |
* Content OP -> Eva | * Content OP -> Eva | ||
− | * Process modeling patterns (re- | + | * Process modeling patterns (re-engineering, modeling/content) -> Violeta, Gerd |
** Content OP in the domain of business process management (BPM) | ** Content OP in the domain of business process management (BPM) | ||
− | * Re- | + | * Re-engineering patterns -> ? |
* Linguistic patterns -> Wim Peters | * Linguistic patterns -> Wim Peters | ||
− | + | Deadlines: | |
− | * half of march for external user(s) | + | * 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 | + | * Valentina summarize things done until now to disseminate ODP portal, and proposes |
− | ** A | + | ** 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 | + | ** Event: competition or Vocamp about the portal |
** An Open source project | ** An Open source project | ||
** AP (enrico,all) setup a page readable only by editorial member where everybody can put mailing lists | ** 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. |
The meeting will be held at the Institute for Cognitive Science and Technology, Piaget room (first floor).
Via San Martino della Battaglia 44, Rome
Hotel Villa delle Rose
Hotel S. Marco
Hotel Montecarlo
Hotel Artemide
Hotel Cosmopolita
Web site: http://www.leonardihotels.com/Pace-Elvezia/index2.jsp
Hotel Pace Elvetia
Valentina introduce: EB members (responsibilities on):
Things todo:
Review/certification process:
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):
We need responsibles for:
Things to do next three months: - Definition of new area - Contribute in taking dissemination actions
AP:
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:
Description of the reviewing process by the evaluation
Review-Certification process:
(lunch)
Valentina illustrates the patterns' different types
Discussion about lexical issues on ODP taxonomy:
Responsibilities:
Deadlines:
Dissemination: