Submissions:CommunicationEvent
From Odp
(Difference between revisions)
Current revision (07:52, 6 September 2010) (view source) m (Review has been assigned.) |
|||
Line 187: | Line 187: | ||
{{Modeling issues about me}} | {{Modeling issues about me}} | ||
{{My references}} | {{My references}} | ||
+ | [[Category:Review assigned]] |
Current revision
If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 10036 |
Graphical representation
Diagram
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: |
|
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: |
|
Has Components: | |
Specialization Of: | |
Related CPs: |
Elements
The CommunicationEvent Content OP locally defines the following ontology elements:
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 CommunicationEvent (owl:Class) An instance of communication, e.g. a phone call, a meeting or a conference.
CommunicationEvent page 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 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 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 CommunicationPurpose page
face-to-face page
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 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 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 CommunicationEventStatus (owl:Class) The status of an event, e.g. suspended, started, ongoing, planned, proposed.
CommunicationEventStatus pageAdditional 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 10036) |
---|---|---|
EvaBlomqvist about CommunicationEvent | 24554466 September 2010 | 1003610,036 |
This revision (revision ID 10036) 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.