Submissions:CommunicationEvent - Revision history

EvaBlomqvist: Review has been assigned.

2010-09-06T07:52:37Z

Review has been assigned.

EvaBlomqvist at 22:51, 24 March 2010

2010-03-24T22:51:32Z

EvaBlomqvist: Imported from OWL file.

2010-03-24T22:47:41Z

Imported from OWL file.

New page

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=
}}
{{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?
|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.
|ReengineeredFrom=Data model pattern called "communication events".
|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
|SubmittedBy=EvaBlomqvist
|ReusableOWLBuildingBlock=http://www.ontology.se/odp/content/owl/CommunicationEvent.owl
|Name=CommunicationEvent
}}
{{Element list header}}
{{Has Element Template
|HasElement=ContactMechanism
}}
{{Has Element Template
|HasElement=isValidContactMechanismFor
}}
{{Has Element Template
|HasElement=CommunicationEventRole
}}
{{Has Element Template
|HasElement=mediumOf
}}
{{Has Element Template
|HasElement=CommunicationEvent
}}
{{Has Element Template
|HasElement=EventDuration
}}
{{Has Element Template
|HasElement=eventStartTime
}}
{{Has Element Template
|HasElement=RelationshipDuration
}}
{{Has Element Template
|HasElement=relationshipStartTime
}}
{{Has Element Template
|HasElement=PartyRole
}}
{{Has Element Template
|HasElement=RelationshipPartyRole
}}
{{Has Element Template
|HasElement=roleInRelationship
}}
{{Has Element Template
|HasElement=PartyRelationship
}}
{{Has Element Template
|HasElement=includesCommunication
}}
{{Has Element Template
|HasElement=relationshipIncludes
}}
{{Has Element Template
|HasElement=relationshipHasDuration
}}
{{Has Element Template
|HasElement=EmailCommunication
}}
{{Has Element Template
|HasElement=throughMedium
}}
{{Has Element Template
|HasElement=e-mail
}}
{{Has Element Template
|HasElement=PhoneCommunication
}}
{{Has Element Template
|HasElement=phone
}}
{{Has Element Template
|HasElement=CommunicationPurpose
}}
{{Has Element Template
|HasElement=purposeOfEvent
}}
{{Has Element Template
|HasElement=WebSiteCommunication
}}
{{Has Element Template
|HasElement=web-site
}}
{{Has Element Template
|HasElement=FaceToFaceCommunication
}}
{{Has Element Template
|HasElement=face-to-face
}}
{{Has Element Template
|HasElement=roleOfParty
}}
{{Has Element Template
|HasElement=partyParticipating
}}
{{Has Element Template
|HasElement=inRelationship
}}
{{Has Element Template
|HasElement=Party
}}
{{Has Element Template
|HasElement=partyInvolvedIn
}}
{{Has Element Template
|HasElement=CommunicationEventPartyRole
}}
{{Has Element Template
|HasElement=partyInRelationship
}}
{{Has Element Template
|HasElement=hasValidContactMechanism
}}
{{Has Element Template
|HasElement=eventRoleIncludedIn
}}
{{Has Element Template
|HasElement=LetterCorrespondence
}}
{{Has Element Template
|HasElement=letter
}}
{{Has Element Template
|HasElement=FaxCommunication
}}
{{Has Element Template
|HasElement=fax
}}
{{Has Element Template
|HasElement=roleOfEvent
}}
{{Has Element Template
|HasElement=partyInEvent
}}
{{Has Element Template
|HasElement=inCommunicationEvent
}}
{{Has Element Template
|HasElement=eventIncludes
}}
{{Has Element Template
|HasElement=communicationHasSetting
}}
{{Has Element Template
|HasElement=eventHasPurpose
}}
{{Has Element Template
|HasElement=eventHasDuration
}}
{{Has Element Template
|HasElement=hasEventStatus
}}
{{Has Element Template
|HasElement=CommunicationEventStatus
}}
{{Has Element Template
|HasElement=statusOfEvent
}}
{{Has Element Template
|HasElement=isDurationOfEvent
}}
{{Has Element Template
|HasElement=isDurationOfRelationship
}}
{{Has Element Template
|HasElement=relationshipEndTime
}}
{{Has Element Template
|HasElement=eventEndTime
}}

{{Additional information header}}

{{Scenarios about me}}
{{Reviews about me}}{{Modeling issues about me}}{{My references}}

← Older revision		Revision as of 07:52, 6 September 2010
Line 187:		Line 187:
	{{Modeling issues about me}}		{{Modeling issues about me}}
	{{My references}}		{{My references}}
		+	[[Category:Review assigned]]

@@ Line 2: / Line 2: @@
 {{Graphical representation header}}
 {{Graphical representation
-|ImageName=
+|ImageName=CommunicationEvent.jpg
 }}
 {{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
 |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.
 |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
 }}
 {{Element list header}}
@@ Line 179: / Line 181: @@
 |HasElement=eventEndTime
 }}
 {{Additional information header}}
 {{Scenarios about me}}
-{{Reviews about me}}{{Modeling issues about me}}{{My references}}
+{{Reviews about me}}