Submissions:CommunicationEvent

From Odp

(Difference between revisions)
Jump to: navigation, search
(Imported from OWL file.)
Line 2: Line 2:
{{Graphical representation header}}
{{Graphical representation header}}
{{Graphical representation
{{Graphical representation
-
|ImageName=
+
|ImageName=CommunicationEvent.jpg
}}
}}
{{Content OP Proposal Template
{{Content OP Proposal Template
-
|CompetencyQuestion=What is the status of this event?, What is the purpose of this communication?, What are the valid contact mechanisms for this communication?, What roles did the different parties have in this communication event?, What are the roles of the parties involved in this relationship?, What was the contact mechanism used for this comunication?, When did this communication event take place?, In what reltionship context did this communication take place?
+
|SubmittedBy=EvaBlomqvist
 +
|Name=CommunicationEvent
|Intent=To model communication events, such as phone calls, e-mails and meetings, their involved parties and the roles and relations of the parties in the context of the communication events.
|Intent=To model communication events, such as phone calls, e-mails and meetings, their involved parties and the roles and relations of the parties in the context of the communication events.
 +
|Domain=Organization, Business, Planning, Participation, Product development
 +
|CompetencyQuestion=What is the status of this event?, What is the purpose of this communication?, What are the valid contact mechanisms for this communication?, What roles did the different parties have in this communication event?, What are the roles of the parties involved in this relationship?, What was the contact mechanism used for this comunication?, When did this communication event take place?, In what reltionship context did this communication take place?
 +
|ContentODPDescription=The pattern introduces a specialization of the participation pattern, where parties hold different roles when participating in communication events.
 +
|ReusableOWLBuildingBlock=http://www.ontology.se/odp/content/owl/CommunicationEvent.owl
 +
|Consequences=Pattern includes a set of standard communication mechanisms, but can be extended., The pattern does not take into account time-indexed participation in relationships, nor time-indexed participation in communication events. All parties are assumed to participate during the whole duration of relationships and events.
 +
|Scenario=A sales call between John at company x and Mary at company y took place on January 7 2009. In the call John had the role of seller and Mary the role of buyer. The call was made in the context of the long-term relation between comanies x and y, where x is the subcontractor of y. The purpose of the call was to agree on a price for a particular order item. , In todays boardmeeting John was elected chairman of the meeting, and Michael was appointed to take the minutes. The meeting involved 6 people, where 5 were elected members of the board and one was an invited external party. The purpose of the meeting was to decide on the price of a new product. However, the participants did not agree so the meeting had to be suspended and will continue tomorrow.
|ReengineeredFrom=Data model pattern called "communication events".
|ReengineeredFrom=Data model pattern called "communication events".
-
|HasComponent=participantrole, timeinterval
+
|HasComponent=ParticipantRole, TimeInterval
-
|Scenario=A sales call between John at company x and Mary at company y took place on January 7 2009. In the call John had the role of seller and Mary the role of buyer. The call was made in the context of the long-term relation between comanies x and y, where x is the subcontractor of y. The purpose of the call was to agree on a price for a particular order item. , In todays boardmeeting John was elected chairman of the meeting, and Michael was appointed to take the minutes. The meeting involved 6 people, where 5 were elected members of the board and one was an invited external party. The purpose of the meeting was to decide on the price of a new product. However, the participants did not agree so the meeting had to be suspended and will continue tomorrow. 
+
-
|Consequences=Pattern includes a set of standard communication mechanisms, but can be extended., The pattern does not take into account time-indexed participation in relationships, nor time-indexed participation in communciation events. All parties are assumed to participate during the whole duration of relationships and events.
+
|SpecializationOf=ParticipantRole
|SpecializationOf=ParticipantRole
-
|SubmittedBy=EvaBlomqvist
 
-
|ReusableOWLBuildingBlock=http://www.ontology.se/odp/content/owl/CommunicationEvent.owl
 
-
|Name=CommunicationEvent
 
}}
}}
{{Element list header}}
{{Element list header}}
Line 179: Line 181:
|HasElement=eventEndTime
|HasElement=eventEndTime
}}
}}
-
 
{{Additional information header}}
{{Additional information header}}
{{Scenarios about me}}
{{Scenarios about me}}
-
{{Reviews about me}}{{Modeling issues about me}}{{My references}}
+
{{Reviews about me}}
 +
{{Modeling issues about me}}
 +
{{My references}}

Revision as of 22:51, 24 March 2010


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 9440

Graphical representation

Diagram

Image:CommunicationEvent.jpg

General description

Name: CommunicationEvent
Submitted by: EvaBlomqvist
Also Known As:
Intent: To model communication events, such as phone calls, e-mails and meetings, their involved parties and the roles and relations of the parties in the context of the communication events.
Domains:

Organization, Business, Planning, Participation, Product development

Competency Questions:
  • What is the status of this event?
  • What is the purpose of this communication?
  • What are the valid contact mechanisms for this communication?
  • What roles did the different parties have in this communication event?
  • What are the roles of the parties involved in this relationship?
  • What was the contact mechanism used for this comunication?
  • When did this communication event take place?
  • In what reltionship context did this communication take place?
Solution description: The pattern introduces a specialization of the participation pattern, where parties hold different roles when participating in communication events.
Reusable OWL Building Block: http://www.ontology.se/odp/content/owl/CommunicationEvent.owl (1019)
Consequences: Pattern includes a set of standard communication mechanisms, but can be extended., The pattern does not take into account time-indexed participation in relationships, nor time-indexed participation in communication events. All parties are assumed to participate during the whole duration of relationships and events.
Scenarios: A sales call between John at company x and Mary at company y took place on January 7 2009. In the call John had the role of seller and Mary the role of buyer. The call was made in the context of the long-term relation between comanies x and y, where x is the subcontractor of y. The purpose of the call was to agree on a price for a particular order item., In todays boardmeeting John was elected chairman of the meeting, and Michael was appointed to take the minutes. The meeting involved 6 people, where 5 were elected members of the board and one was an invited external party. The purpose of the meeting was to decide on the price of a new product. However, the participants did not agree so the meeting had to be suspended and will continue tomorrow.
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
  • Data model pattern called "communication events".
Has Components:
Specialization Of:
Related CPs:


Elements

The CommunicationEvent Content OP locally defines the following ontology elements:

Class ContactMechanism (owl:Class) The medium for the communication.
ContactMechanism page
ObjectProperty isValidContactMechanismFor (owl:ObjectProperty)
isValidContactMechanismFor page
Class CommunicationEventRole (owl:Class) The role that this event plays for a specific party, e.g. a conference has the role of transmitting research results for a presenter while it has the role of generating income and connections for the organizers, and generating knowledge for the participants.
CommunicationEventRole page
ObjectProperty mediumOf (owl:ObjectProperty)
mediumOf page
Class CommunicationEvent (owl:Class) An instance of communication, e.g. a phone call, a meeting or a conference.
CommunicationEvent page
Class EventDuration (owl:Class) The time duration of a communication event.
EventDuration page
DatatypeProperty eventStartTime (owl:DatatypeProperty)
eventStartTime page
Class RelationshipDuration (owl:Class) The time duration of a relationship.
RelationshipDuration page
DatatypeProperty relationshipStartTime (owl:DatatypeProperty)
relationshipStartTime page
Class PartyRole (owl:Class) The role of a party in a relationship, e.g. in a sales relationship one party has the customer role and the other party the provider role.
PartyRole page
Class RelationshipPartyRole (owl:Class) The role of a specific party in a relationship, e.g. in this particular buyer-seller relationship company x is the seller.
RelationshipPartyRole page
ObjectProperty roleInRelationship (owl:ObjectProperty)
roleInRelationship page
Class PartyRelationship (owl:Class) An event in the sense of a state of things, where two or more parties are involved through different roles, e.g. a buyer-seller relation.
PartyRelationship page
ObjectProperty includesCommunication (owl:ObjectProperty)
includesCommunication page
ObjectProperty relationshipIncludes (owl:ObjectProperty)
relationshipIncludes page
ObjectProperty relationshipHasDuration (owl:ObjectProperty)
relationshipHasDuration page
Class EmailCommunication (owl:Class)
EmailCommunication page
ObjectProperty throughMedium (owl:ObjectProperty)
throughMedium page
e-mail page
Class PhoneCommunication (owl:Class)
PhoneCommunication page
phone page
Class CommunicationPurpose (owl:Class) The purpose or goal of the communciation event.
CommunicationPurpose page
ObjectProperty purposeOfEvent (owl:ObjectProperty)
purposeOfEvent page
Class WebSiteCommunication (owl:Class)
WebSiteCommunication page
web-site page
Class FaceToFaceCommunication (owl:Class)
FaceToFaceCommunication page
face-to-face page
ObjectProperty roleOfParty (owl:ObjectProperty)
roleOfParty page
ObjectProperty partyParticipating (owl:ObjectProperty)
partyParticipating page
ObjectProperty inRelationship (owl:ObjectProperty)
inRelationship page
Class Party (owl:Class) A physical or juridical party, e.g. person or organization.
Party page
ObjectProperty partyInvolvedIn (owl:ObjectProperty)
partyInvolvedIn page
Class CommunicationEventPartyRole (owl:Class) The role of a specific party for a specific communciation event, e.g. in this particular meeting John is the chairman.
CommunicationEventPartyRole page
ObjectProperty partyInRelationship (owl:ObjectProperty)
partyInRelationship page
ObjectProperty hasValidContactMechanism (owl:ObjectProperty) Relates roles of communication events to their valid mediums, e.g. it may only be allowed to send contracts by letter or fax but not e-mail.
hasValidContactMechanism page
ObjectProperty eventRoleIncludedIn (owl:ObjectProperty)
eventRoleIncludedIn page
Class LetterCorrespondence (owl:Class)
LetterCorrespondence page
letter page
Class FaxCommunication (owl:Class)
FaxCommunication page
fax page
ObjectProperty roleOfEvent (owl:ObjectProperty)
roleOfEvent page
ObjectProperty partyInEvent (owl:ObjectProperty)
partyInEvent page
ObjectProperty inCommunicationEvent (owl:ObjectProperty)
inCommunicationEvent page
ObjectProperty eventIncludes (owl:ObjectProperty)
eventIncludes page
ObjectProperty communicationHasSetting (owl:ObjectProperty) All communications take place within some relationship between parties, e.g. a sales call takes place within the relationship with a prospective customer.
communicationHasSetting page
ObjectProperty eventHasPurpose (owl:ObjectProperty)
eventHasPurpose page
ObjectProperty eventHasDuration (owl:ObjectProperty)
eventHasDuration page
ObjectProperty hasEventStatus (owl:ObjectProperty)
hasEventStatus page
Class CommunicationEventStatus (owl:Class) The status of an event, e.g. suspended, started, ongoing, planned, proposed.
CommunicationEventStatus page
ObjectProperty statusOfEvent (owl:ObjectProperty)
statusOfEvent page
ObjectProperty isDurationOfEvent (owl:ObjectProperty)
isDurationOfEvent page
ObjectProperty isDurationOfRelationship (owl:ObjectProperty)
isDurationOfRelationship page
DatatypeProperty relationshipEndTime (owl:DatatypeProperty)
relationshipEndTime page
DatatypeProperty eventEndTime (owl:DatatypeProperty)
eventEndTime page

Additional information

Scenarios

Scenarios about CommunicationEvent

No scenario is added to this Content OP.

Reviews

Reviews about CommunicationEvent
Review article Posted on About revision (current is 9440)
EvaBlomqvist about CommunicationEvent 24554466 September 2010 1003610,036

This revision (revision ID 9440) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about CommunicationEvent

There is no Modeling issue related to this proposal.


References

Add a reference


Retrieved from "http://ontologydesignpatterns.org/wiki/Submissions:CommunicationEvent"
Personal tools
Quality Committee
Content OP publishers