EvaBlomqvist (Talk | contribs) (Imported from OWL file.) |
EvaBlomqvist (Talk | contribs) |
||
| 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 | ||
| − | | | + | |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= | + | |HasComponent=ParticipantRole, TimeInterval |
| − | + | ||
| − | + | ||
|SpecializationOf=ParticipantRole | |SpecializationOf=ParticipantRole | ||
| − | |||
| − | |||
| − | |||
}} | }} | ||
{{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}} | ||
|
Last modified date is: 2010-03-24 |
Diagram
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 (owl:Class) The purpose or goal of the communciation event.
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 pageNo scenario is added to this Content OP.
This revision (revision ID 9440) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
