| Line 13: | Line 13: | ||
|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 a 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 | ||
| + | |CPInstantiationExample=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 | |ExtractedFrom=Ontological resources and non ontological resources | ||
}} | }} | ||
|
Last modified date is: 2016-07-15 |
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 12631) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
