Submissions:Complaint Design Pattern

From Odp

This article is waiting for review
Jump to: navigation, search


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 13488

Graphical representation

Diagram (this article has no graphical representation)

General description

Name: Complaint Ontology Pattern - COP
Submitted by: CristianaSantos, VictorRodriguezDoncel, Marcos da Silveira, Cedric Prusky, AldoGangemi, Pompeu Casanovas, Leon Van der Torre
Also Known As: Complaint Ontology Pattern
Intent: To represent core constituents found commonly in complaints across domains.
Domains:

General, Law

Competency Questions:
  • 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?
Solution description: The solution is implemented as an OWL file [1]
Reusable OWL Building Block: http://ontoology.linkeddata.es/publish/cop/index-en.html (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 a 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:

basedOn page
expressedIn page
hasComplaintMotivation page
justifiedBy page
madeBy page
supportedBy page
hasSpace page
hasStampTime page
hasTimeOccurrence page
Agent page
Complainant page
Complaint page
Complaint_Recipient page
Evidence page
Fact page
Medium page
Motivation page
Request page
ThirdParty page
partOf page
addressedTo page

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 13488) 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

Add a reference


Submission to event

WOP 2016 at ISWC


Submission to event


Personal tools
Quality Committee
Content OP publishers