m (Article is waiting for review.) |
m |
||
Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
{{Graphical representation header}} | {{Graphical representation header}} | ||
− | {{Graphical representation | + | {{Graphical representation}} |
− | + | ||
− | }} | + | |
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
− | |SubmittedBy=CristianaSantos | + | |SubmittedBy=CristianaSantos, VictorRodriguezDoncel, Marcos da Silveira, Cedric Prusky, AldoGangemi, Pompeu Casanovas, Leon Van der Torre |
− | |Name=COP | + | |Name=Complaint Ontology Pattern - COP |
− | |Intent=To represent | + | |ContentODPAlsoKnownAs=COP |
+ | |Intent=To represent core constituents found commonly in complaints across domains. | ||
+ | |Domain=General | ||
|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? | |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 | |ContentODPDescription=The solution is implemented as an OWL file | ||
− | |ReusableOWLBuildingBlock=https:// | + | |ReusableOWLBuildingBlock=https://w3id.org/vocabulary/cop |
|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 a motive and a request, through a specific medium (used to generate the complaint document), where evidence may support the facts. |
+ | |ExtractedFrom=Ontological resources and non ontological resources | ||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
Line 79: | Line 80: | ||
}} | }} | ||
{{Additional information header}} | {{Additional information header}} | ||
− | + | [[Category:Waiting for review]] | |
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
{{Modeling issues about me}} | {{Modeling issues about me}} | ||
{{My references}} | {{My references}} | ||
− |
Diagram (this article has no graphical representation)
The Complaint Design Pattern Content OP locally defines the following ontology elements:
No scenario is added to this Content OP.
This revision (revision ID 12612) takes in account the reviews: none
Other info at evaluation tab