Submissions:Complaint Design Pattern
From Odp
(Difference between revisions)
(Imported from OWL file.) |
|||
Line 2: | Line 2: | ||
{{Graphical representation header}} | {{Graphical representation header}} | ||
{{Graphical representation | {{Graphical representation | ||
- | |ImageName= | + | |ImageName=Cop.png |
}} | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
- | | | + | |SubmittedBy=CristianaSantos |
+ | |Name=COP | ||
|Intent=To represent the core constituents of a complaint | |Intent=To represent the core constituents of a complaint | ||
+ | |CompetencyQuestion=What is the claim of the complainant?, Which facts happened in 'this' date or in 'this' place?, Who is involved in this complaint?, Who is the complaint recipient?, What motivates the complaint?, Which facts describe the complaint?, What evidences are used to prove the narrated fact?, Which medium was used to express the complaint? | ||
+ | |ContentODPDescription=The solution is implemented as an OWL file | ||
+ | |ReusableOWLBuildingBlock=https://raw.githubusercontent.com/Rel-incode/cop/master/cop.owl | ||
|Consequences=Heterogeneous models for complaints can be aligned to this pattern, which then acts as a semantic facade to different complaint management applications (such as complaint handling process, customer complaint management, customer relation management) | |Consequences=Heterogeneous models for complaints can be aligned to this pattern, which then acts as a semantic facade to different complaint management applications (such as complaint handling process, customer complaint management, customer relation management) | ||
|Scenario=A complaint refers to the narrated facts of an agent, grounded with motive and a request, through a specific medium (used to generate the complaint document), where evidence may support the facts. | |Scenario=A complaint refers to the narrated facts of an agent, grounded with motive and a request, through a specific medium (used to generate the complaint document), where evidence may support the facts. | ||
- | |||
- | |||
- | |||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
Line 77: | Line 78: | ||
|HasElement=ThirdParty | |HasElement=ThirdParty | ||
}} | }} | ||
- | |||
{{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 10:59, 3 May 2016
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: 12514 |
Graphical representation
Diagram
General description
Name: | COP |
---|---|
Submitted by: | CristianaSantos |
Also Known As: | |
Intent: | To represent the core constituents of a complaint |
Domains: | |
Competency Questions: |
|
Solution description: | The solution is implemented as an OWL file |
Reusable OWL Building Block: | https://raw.githubusercontent.com/Rel-incode/cop/master/cop.owl (0) |
Consequences: | Heterogeneous models for complaints can be aligned to this pattern, which then acts as a semantic facade to different complaint management applications (such as complaint handling process, customer complaint management, customer relation management) |
Scenarios: | A complaint refers to the narrated facts of an agent, grounded with motive and a request, through a specific medium (used to generate the complaint document), where evidence may support the facts. |
Known Uses: | |
Web References: | |
Other References: | |
Examples (OWL files): | |
Extracted From: | |
Reengineered From: | |
Has Components: | |
Specialization Of: | |
Related CPs: |
Elements
The Complaint Design Pattern Content OP locally defines the following ontology elements:
Additional information
Scenarios
Scenarios about Complaint Design Pattern
No scenario is added to this Content OP.
Reviews
Reviews about Complaint Design Pattern
There is no review about this proposal. This revision (revision ID 12514) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
Modeling issues about Complaint Design Pattern
There is no Modeling issue related to this proposal.
References