 |
Page History
| Scrollbar |
|---|
| Children Display |
|---|
| Page info | ||||
|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
| ||||
|
Summary
...
Description of the profile
...
Policy and Rules Management allow non-developer secondary users to create policies and rules and apply them to services. The scope of policies includes, but is not limited to, definition and configuration of quality of service policies. Some key functional requirements for managing policies include capabilities to author policies and store policies, and to approve and validate policies and execute policies at runtime.
...
- decision procedures which must be able to measure and render decisions on constraints;
- enforcement of decisions;
- measurement and notification of obligation constraints;
- auditability of decisions, enforcement, and obligation measurements;
- administration of policy and contract language artifacts;
- storage of policies and contracts;
- distribution of policies/contracts;
- conflict resolution or elevation of conflicts in policy rules;
- delegation of policy authority to agents acting on behalf of a client;
- decision procedures capable of incorporating roles and/or attributes for rendered decisions.
While policy and contract descriptions have much of the same architectural implications as Service Descriptions, languages supporting policies and contracts also have the following architectural implications: - expression of assertion and commitment policy constraints;
- expression of positive and negative policy constraints;
- expression of permission and obligation policy constraints;
- nesting of policy constraints allowing for abstractions and refinements of a policy constraint;
- definition of alternative policy constraints to allow for the selection of compatible policy constraints for a consumer and provider;
- composition of policies to combine one or more policies.
...
Capabilities
...
- assembly
- binding
- complianceDiscovery
- componentAcquisition
- compositionArchive
- compositionChange
- configurationManagement
- discovery
- identity
- interactionLog
- interactionResults
- interoperabilityDiscovery
- logging
- mediation
- metadata
- metrics
- metricsDiscovery
- monitor
- monitoring
- policyAdministration
- policyAlternative
- policyAssertion
- policyAudit
- policyAuthorityDelegation
- policyComposition
- policyConflictResolution
- policyConstraint
- policyDecision
- policyDecisionProcedures
- policyDistribution
- policyEnforcement
- policyMetrics
- policyObligation
- policyRefinement
- policyStore
- provenance
- qualityOfServicePolicyModel
- security
- serviceChangeNotification
- store
- transition
- versioning
Requirements traceability
Requirement | Source | Capability | ||||||
|---|---|---|---|---|---|---|---|---|
 | Semantic Profile::OASIS SOA::
| monitor from inherited abstract profile Metrics, metrics from inherited abstract profile Metrics, discovery from inherited abstract profile Artifact, identity from inherited abstract profile Artifact, metadata from inherited abstract profile Artifact, store from inherited abstract profile Artifact, | ||||||
 | Semantic Profile::OASIS SOA::
| interactionLog from inherited abstract profile Interaction, interactionResults from inherited abstract profile Interaction, mediation from inherited abstract profile Interaction, binding from inherited abstract profile Interaction, logging from inherited abstract profile Interaction, security from inherited abstract profile Interaction, monitoring from inherited abstract profile Interaction, | ||||||
 | Semantic Profile::OASIS SOA::
| policyAssertion from inherited abstract profile PolicyAndContractLanguage, policyObligation from inherited abstract profile PolicyAndContractLanguage, policyConstraint from inherited abstract profile PolicyAndContractLanguage, policyRefinement from inherited abstract profile PolicyAndContractLanguage, policyAlternative from inherited abstract profile PolicyAndContractLanguage, policyComposition from inherited abstract profile PolicyAndContractLanguage, policyEnforcement from inherited abstract profile PolicyAndContract, policyAdministration from inherited abstract profile PolicyAndContract, policyAudit from inherited abstract profile PolicyAndContract, policyStore from inherited abstract profile PolicyAndContract, policyDecision from inherited abstract profile PolicyAndContract, policyMetrics from inherited abstract profile PolicyAndContract, policyDistribution from inherited abstract profile PolicyAndContract, policyConflictResolution from inherited abstract profile PolicyAndContract, policyAuthorityDelegation from inherited abstract profile PolicyAndContract, policyDecisionProcedures from inherited abstract profile PolicyAndContract, | ||||||
Policy and Rules Management allow non-developer secondary users to create policies and rules and apply them to services. The scope of policies includes, but is not limited to, definition and configuration of business processing policy and related rules, compliance policies, quality of service policies, and security policies. Some key functional requirements for managing policies include capabilities to author policies and store policies, and to approve and validate policies and execute policies at runtime. The Semantic Infrastructure will provide a mechanism to specify policies, including business processing policies and related rules, compliance policies, and quality of service policies. Tools and services for creating security specific policies will be provided by the caGRID 2.0 platform and will be used by the semantic infrastructure. All other policies specified in the Semantic Infrastructure will be enforced by the platform at runtime. Link to use case satisfied from caGRID 2.0 Roadmap: Each institution has different data sharing needs, access control needs, and business rules for processing that are defined and customized. For example, policy at the pathologist's institution may state that the patient is scheduled for a visit when the review is complete. | Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::
| |||||||
 | Semantic Profile::OASIS SOA::
| versioning from inherited abstract profile Change, configurationManagement from inherited abstract profile Change, transition from inherited abstract profile Change, discovery from inherited abstract profile Artifact, identity from inherited abstract profile Artifact, metadata from inherited abstract profile Artifact, store from inherited abstract profile Artifact, monitor from inherited abstract profile Metrics, metrics from inherited abstract profile Metrics, metricsDiscovery from inherited abstract profile Metrics, complianceDiscovery from inherited abstract profile Metrics, interactionLog from inherited abstract profile Interaction, interactionResults from inherited abstract profile Interaction, compositionArchive from inherited abstract profile Composition, assembly from inherited abstract profile Composition, compositionChange from inherited abstract profile Composition, componentAcquisition from inherited abstract profile Composition, interoperabilityDiscovery from inherited abstract profile Interoperability, serviceChangeNotification from inherited abstract profile Interoperability, |
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Tools to facilitate identifying description elements that are to be aggregated to assemble the composite description.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
binding services that support translation and transformation of multiple application-level protocols to standard network transport protocols;
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Mechanisms to catalog and enable discovery of compliance records associated with policies, contracts, and constraints that are based on these metrics.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Tools to facilitate identifying the sources of information to associate with the description elements.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Tools to collect the identified description elements and their associated sources into a standard, referenceable format that can support general access and understanding.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Tools to automatically update the composite description as the component sources change, and to consistently apply versioning schemes to identify the new description contents and the type and significance of change that occurred.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Mechanisms to support the storage, referencing, and access to normative definitions of one or more versioning schemes that may be applied to identify different aggregations of descriptive information, where the different schemes may be versions of a versioning scheme itself.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
One or more discovery mechanisms that enable searching for artifacts that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual artifact descriptions, possibly through some repository mechanism.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Descriptions which include a unique identifier for the artifact.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
One or more mechanisms to capture, describe, store, discover, and retrieve interaction logs, execution contexts, and the combined interaction descriptions.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
One or more mechanisms for attaching to any results the means to identify and retrieve the interaction description under which the results were generated.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
One or more discovery mechanisms that enable searching for described resources that best meet the criteria specified by a service participant, where the discovery mechanism will have access to individual descriptions, possibly through some repository mechanism.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
auditing and logging services that provide a data store and mechanism to record information related to service interaction activity such as message traffic patterns, security violations, and service contract and policy violations
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
mediation services such as message and event brokers, providers, and/or buses that provide message translation/transformation, gateway capability, message persistence, reliable message delivery, and/or intelligent routing semantics;
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
A representation of the meaning of terms used to describe the artifact, its functions, and its effects.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Access to metrics information generated or accessible by related services
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Mechanisms to catalog and enable discovery of which metrics are available for a described artifact and information on how these metrics can be accessed.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Access to platform infrastructure monitoring and reporting capabilities.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
monitoring services such as hardware and software mechanisms that both monitor the performance of systems that host services and network traffic during service interaction, and are capable of generating regular monitoring reports.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Administration of policy and contract language artifacts.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Definition of alternative policy constraints to allow for the selection of compatible policy constraints for a consumer and provider.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Expression of assertion and commitment policy constraints.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Auditability of decisions, enforcement, and obligation measurements.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Delegation of policy authority to agents acting on behalf of a client.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Composition of policies to combine one or more policies.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Conflict resolution or elevation of conflicts in policy rules.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Expression of positive and negative policy constraints.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Decision procedures which must be able to measure and render decisions on constraints.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Decision procedures capable of incorporating roles and/or attributes for rendered decisions.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Distribution of policies/contracts.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Enforcement of decisions.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Measurement and notification of obligation constraints.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Expression of permission and obligation policy constraints.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Nesting of policy constraints allowing for abstractions and refinements of a policy constraint.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Storage of policies and contracts.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
While the Resource identity provides the means to know which subject and subject description are being considered, Provenance as related to the Description class provides information that reflects on the quality or usability of the subject. Provenance specifically identifies the entity (human, defined role, organization, ...) that assumes responsibility for the resource being described and tracks historic information that establishes a context for understanding what the resource provides and how it has changed over time. Responsibilities may be directly assumed by the Stakeholder who owns a Resource or the Owner may designate Responsible Parties for the various aspects of maintaining the resource and provisioning it for use by others. There may be more than one entity identified under Responsible Parties; for example, one entity may be responsible for code maintenance while another is responsible for provisioning of the executable code. The historical aspects may also have multiple entries, such as when and how data was collected and when and how it was subsequently processed, and as with other elements of description, may provide links to other assets maintained by the Resource owner.
Requirements addressed
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Quality of Service Policy Model with capabilities to create, destroy, edit, maintain service descriptions.
...
- definition and configuration of Quality of Service policy and related rule
- apply policies to services
- author policy
- store policies
- approve policies
- validate policies
- execute policies at runtime
Requirements addressed
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
security services that abstract techniques such as public key cryptography, secure networks, virus protection, etc., which provide protection against common security threats in a SOA ecosystem;
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Tools to appropriately track users of the descriptions and notify them when a new version of the description is available.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
One or more mechanisms to support the storage, referencing, and access to conversion relationships between versioning schemes, and the mechanisms to carry out such conversions.
...
Requirements addressed
...
...
Overview of possible operations
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
...
Configuration management mechanisms to capture the contents of the each aggregation and apply a unique identifier in a manner consistent with an identified versioning scheme.
...
Requirements addressed
...
...
Overview of possible operations
...
| Scrollbar |
|---|
