Difference between revisions of "Submissions:Policy"

(Imported from OWL file.)
 
m (Article is waiting for review.)
 
(8 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
{{Graphical representation header}}
 
{{Graphical representation header}}
 
{{Graphical representation
 
{{Graphical representation
−
|ImageName=
+
|ImageName=Policies_ODP.png
 
}}
 
}}
 
{{Content OP Proposal Template
 
{{Content OP Proposal Template
−
|CompetencyQuestion=1. What are the main entities associated with a policy? A policy is usually associated with super/sub-policies, processes, agents and other entities.
+
|SubmittedBy=PanagiotisMitzias, FabioCorubolo, EfstratiosKontopoulos, MarinaRiga
−
2. What are the main attributes of a policy? They are version, language, policy type, requirement level, implementation status and automation status.
+
−
3. Where is a policy described? Statements are detailed text (formal or non- formal) definitions of the policy contents.
+
−
|Intent=The pattern intends to model policies, their characteristics and their associated entities, such as processes and agents.
+
−
|Scenario=Some examples of instantiation of the Policy ODP are:
+
−
  1. The policy has two subpolicies
+
−
  2. The policy is implemented by a certain process
+
−
  3. The policy is validated by a certain process
+
−
  4. The policy is assigned to John Smith
+
−
  5. The policy is fully automated
+
−
|Consequences=The Policy ODP is expected to facilitate the representation of the policy notion, which can be exploited in various domains. A well-established, comprehensible pattern will prove to be advantageous.
+
−
|SubmittedBy=PanagiotisMitzias
+
−
|ReusableOWLBuildingBlock=http://pmitzias.com/documents/Policy_ODP.owl
+
 
|Name=Policy
 
|Name=Policy
 +
|Intent=The pattern intends to model policies, their characteristics and their associated entities, such as processes and agents. This pattern has been developed by [http://mklab.iti.gr/ MKLab] at CERTH/ITI and the University of Liverpool for the [http://www.pericles-project.eu/ PERICLES] FP7 project.
 +
|Domain=General
 +
|CompetencyQuestion=<p><i>What are the main entities associated with a policy?</i> A policy is usually associated with:<ul><li>super/sub-policies</li> <li>processes</li> <li>agents</li> <li>other entities</li></ul></p>
 +
<p><ul><li><i>What are the main attributes of a policy?</i> They are:, version, language, policy type, requirement level, implementation status, automation status</li></ul></p>
 +
<p><ul><li><i>Where is a policy described?</i> Statements are detailed text (formal or non- formal) definitions of the policy contents.</li></ul></p>
 +
|ContentODPDescription=The pattern’s main entity is a policy. Appropriate object properties connect the policy with significant attributes and other entities.
 +
|ReusableOWLBuildingBlock=http://mklab.iti.gr/pericles/Policy_ODP.owl
 +
|Consequences=The Policy ODP is expected to facilitate the representation of the policy notion, which can be exploited in various domains. A well-established, comprehensible pattern will prove to be advantageous.
 +
|Scenario=<ul><li>The policy has two subpolicies.</li><li>The policy is implemented by a certain process.</li><li>The policy is validated by a certain process.</li><li>The policy is assigned to John Smith.</li><li>The policy is fully automated.</li></ul>
 
}}
 
}}
 
{{Element list header}}
 
{{Element list header}}
Line 90: Line 87:
 
|HasElement=Version
 
|HasElement=Version
 
}}
 
}}
−
 
 
{{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}}
 +
[[Category:Waiting for review]]

Latest revision as of 14:29, 7 December 2016

Warning.gif

Warning!

This is an old revision. Go to current revision

Certified.png
This pattern has been certified.

Related submission, with evaluation history, can be found here

Working.gif Last modified date is: 2016-12-07

Graphical representation

Diagram

Policies ODP.png

General description

Name: Policy
Submitted by: PanagiotisMitzias, FabioCorubolo, EfstratiosKontopoulos, MarinaRiga
Also Known As:
Intent: The pattern intends to model policies, their characteristics and their associated entities, such as processes and agents. This pattern has been developed by MKLab at CERTH/ITI and the University of Liverpool for the PERICLES FP7 project.
Domains:

General

Competency Questions:

  • What are the main entities associated with a policy? A policy is usually associated with:

    • super/sub-policies
    • processes
    • agents
    • other entities

  • Where is a policy described? Statements are detailed text (formal or non- formal) definitions of the policy contents.

Solution description: The pattern’s main entity is a policy. Appropriate object properties connect the policy with significant attributes and other entities.
Reusable OWL Building Block: 1 (342)
Consequences: The Policy ODP is expected to facilitate the representation of the policy notion, which can be exploited in various domains. A well-established, comprehensible pattern will prove to be advantageous.
Scenarios:
  • The policy has two subpolicies.
  • The policy is implemented by a certain process.
  • The policy is validated by a certain process.
  • The policy is assigned to John Smith.
  • The policy is fully automated.
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:



Elements

The Policy Content OP locally defines the following ontology elements:

ObjectProperty assignedTo (owl:ObjectProperty) Associates a policy to the agent that is responsible for the application of the policy (person or role).
ArrowRight.gif assignedTo page
ObjectProperty hasAutomationStatus (owl:ObjectProperty) Associates a policy with an automation level.
ArrowRight.gif hasAutomationStatus page
ObjectProperty hasImplementationStatus (owl:ObjectProperty) Associates a policy with an implementation level.
ArrowRight.gif hasImplementationStatus page
ObjectProperty hasLanguage (owl:ObjectProperty) Associates a policy with the language used for the policy definition.
ArrowRight.gif hasLanguage page
ObjectProperty hasPolicyType (owl:ObjectProperty) Associates a policy with a policy type.
ArrowRight.gif hasPolicyType page
ObjectProperty hasRequirementLevel (owl:ObjectProperty) Associates a policy with an requirement level.
ArrowRight.gif hasRequirementLevel page
ObjectProperty hasStatement (owl:ObjectProperty) Associates a policy with a statement, which is a detailed definition of the policy contents.
ArrowRight.gif hasStatement page
ObjectProperty hasSubPolicy (owl:ObjectProperty) Associates a policy to another policy that is contained in the initial.
ArrowRight.gif hasSubPolicy page
ObjectProperty hasValidationProcess (owl:ObjectProperty) Associates a policy with a process that is used to validate the policy.
ArrowRight.gif hasValidationProcess page
ObjectProperty hasVersion (owl:ObjectProperty) Defines a policy's version.
ArrowRight.gif hasVersion page
ObjectProperty implementedBy (owl:ObjectProperty) Associates a policy with a process that is used to implement the policy.
ArrowRight.gif implementedBy page
ObjectProperty targetsEntity (owl:ObjectProperty) Associates a policy with an entity that is subject to the policy.
ArrowRight.gif targetsEntity page
ObjectProperty targetsUsers (owl:ObjectProperty) Associates a policy to the user community the policy has been designed for.
ArrowRight.gif targetsUsers page
Class AutomationStatus (owl:Class) The level of automation of a policy. Specifies if a policy implementation requires human intervention. E.g. manual, automated with human intervention, automated with human validation, fully automated, etc.
ArrowRight.gif AutomationStatus page
Class Descriptor (owl:Class) The various elements describing a policy.
ArrowRight.gif Descriptor page
Class ImplementationStatus (owl:Class) The level of implementation of a policy. E.g. implemented, partially implemented, unimplemented, not-implementable, etc.
ArrowRight.gif ImplementationStatus page
Class Language (owl:Class) The language used for the policy definition. E.g. natural language, ReAL, SPIN, etc.
ArrowRight.gif Language page
Class Policy (owl:Class) A deliberate system of principles to guide decisions and achieve rational outcomes. A policy is a statement of intent, and is implemented as a procedure or protocol.
ArrowRight.gif Policy page
Class PolicyType (owl:Class) The type of policy. Not all policies are equal; mandatory ones must be implemented to satisfy law or other requirements, others are aspirational, and most are met with the best possible effort. E.g. mandatory, legal requirement, aspirational, business driven, etc.
ArrowRight.gif PolicyType page
Class Process (owl:Class) A sequence of interdependent and linked procedures which, at every stage, consume one or more resources (time, energy, machines, money) to convert inputs (data, material, parts, etc.) into outputs.
ArrowRight.gif Process page
Class RequirementLevel (owl:Class) The level of a policy's compliance. E.g. must, must not, should, shoud not, may, etc.
ArrowRight.gif RequirementLevel page
Class Statement (owl:Class) Detailed definition of the policy contents.
ArrowRight.gif Statement page
Class Version (owl:Class) A policy's version
ArrowRight.gif Version page

Additional information

Scenarios

Scenarios about Policy

No scenario is added to this Content OP.

Reviews

Reviews about Policy
There is no review about this proposal.
Some subquery has no valid condition.

This revision (revision ID 13090) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about Policy
There is no Modeling issue related to this proposal.
Some subquery has no valid condition.


References

Add a reference

Retrieved from "http://ontologydesignpatterns.org/index.php?title=Submissions:Policy&oldid=13090"
The page [[Bootstrap:Footer]] was not found.