EnricoDaga (Talk | contribs) m |
|||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
| − | {{ | + | {{Graphical representation header}} |
| + | {{Graphical representation | ||
|ImageName=Imagen3.jpg | |ImageName=Imagen3.jpg | ||
}} | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
| − | |SubmittedBy= | + | |SubmittedBy=Sandra Kohler |
|Name=PharmaInnova | |Name=PharmaInnova | ||
| − | |Intent=To describe invoices with the PharmaInnova Model. | + | |Intent=To describe invoices with the PharmaInnova Model. This schema can be applied to other invoice models. |
|Domain=Business | |Domain=Business | ||
| + | |ContentODPDescription=-- | ||
|ReusableOWLBuildingBlock=http://www.isoco.com/ontologies/neon/PharmaInnovaODP.owl | |ReusableOWLBuildingBlock=http://www.isoco.com/ontologies/neon/PharmaInnovaODP.owl | ||
|Consequences=Especific models for invoices can be aligned to this pattern, which then acts as a semantic facade to different invoice management applications. This pattern is concreter and simplier, but less flexible than the invoice ODP. | |Consequences=Especific models for invoices can be aligned to this pattern, which then acts as a semantic facade to different invoice management applications. This pattern is concreter and simplier, but less flexible than the invoice ODP. | ||
|CPInstantiationExample=http://www.isoco.com/ontologies/neon/PharmaInnovaInvoiceOntology.owl | |CPInstantiationExample=http://www.isoco.com/ontologies/neon/PharmaInnovaInvoiceOntology.owl | ||
| − | |RelatedCP= | + | |RelatedCP=Invoice |
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
| Line 35: | Line 37: | ||
|HasElement=has_body | |HasElement=has_body | ||
}} | }} | ||
| + | {{Additional information header}} | ||
(type): http://www.w3.org/2002/07/owl#Ontology | (type): http://www.w3.org/2002/07/owl#Ontology | ||
| Line 40: | Line 43: | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
| + | {{Modeling issues about me}} | ||
| + | {{My references}} | ||
|
Last modified date is: 2010-03-08 |
Diagram
| Name: | PharmaInnova |
|---|---|
| Submitted by: | Sandra Kohler |
| Also Known As: | |
| Intent: | To describe invoices with the PharmaInnova Model. This schema can be applied to other invoice models. |
| Domains: | |
| Competency Questions: | |
| Solution description: | -- |
| Reusable OWL Building Block: | 1 (513) |
| Consequences: | Especific models for invoices can be aligned to this pattern, which then acts as a semantic facade to different invoice management applications. This pattern is concreter and simplier, but less flexible than the invoice ODP. |
| Scenarios: | |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The PharmaInnova Content OP locally defines the following ontology elements:
Header (owl:Class) The header usually contains important information to identify the invoice like for example the complete address and the company-identification-code.
Header page Body (owl:Class) The body contains all relevant invoice information like the amount of products, their net price etc.
Body page Summary (owl:Class) Contains a summary of the most relevant invoice information like the payment terms and the total amount.
Summary page(type): http://www.w3.org/2002/07/owl#Ontology
(imports): http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl
No scenario is added to this Content OP.
This revision (revision ID 9111) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
