![]() |
Page History
...
Children Display |
---|
Page info | ||||
---|---|---|---|---|
|
Logging Policy Functional Profile
Dynamic retrieval and enforcement of the policies that are in effect for a service interaction in the areas of logging. This information can be used either during the design of the orchestration or during the execution of the defined flow.
...
- definition and configuration of Logging policy
- author policy
- store policies
- approve policies
- validate policies
- execute policies at runtime
From inherited abstract Artifact Functional Profile
An artifact is a managed resource within the Semantic Infrastructure.
An artifact is associated with the following capabilities:
- descriptions to enable the policy modules artifact to be visible, where the description includes a unique identifier for the policy and the metamodel artifact and a sufficient, and preferably a machine processible, representation of the meaning of terms used to describe the policyartifact, its functions, and its effects;
- one or more discovery mechanisms that enable searching for policies artifacts that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual policy artifact descriptions, possibly through some repository mechanism;
- accessible storage of policies artifacts and policy artifact descriptions, so service participants can access, examine, and use the policies artifacts as defined..
From inherited abstract Change Functional Profile
Artifact descriptions change over time and their contents will reflect changing needs and context.
Architectural implications of change on the Semantic Infrastructure are reflected in the following capabilities:
- 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;
- 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;
- 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.
From inherited abstract Composition Functional Profile
Artifact Descriptions may capture very focused information subsets or can be an aggregate of numerous component descriptions. Service description is an example of a likely aggregate for which manual maintenance of all aspects would not be feasible.
Architectural implications of composition on the Semantic Infrastructure are reflected in the following capabilities:
- tools to facilitate identifying description elements that are to be aggregated to assemble the composite description;
- tools to facilitate identifying the sources of information to associate with the description elements;
- tools to collect the identified description elements and their associated sources into a standard, referenceable format that can support general access and understanding;
- 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.
From inherited abstract Interaction Functional Profile
Descriptions of interactions are important for enabling auditability and repeatability, thereby establishing a context for results and support for understanding observed change in performance or results.
Architectural implications of interactions on the Semantic Infrastructure are reflected in the following capabilities:
- one or more mechanisms to capture, describe, store, discover, and retrieve interaction logs, execution contexts, and the combined interaction descriptions;
- one or more mechanisms for attaching to any results the means to identify and retrieve the interaction description under which the results were generated.
From inherited abstract Interoperability Functional Profile
Descriptions provide up-to-date information on what a resource is, the conditions for interacting with the resource, and the results of such interactions. As such, the description is the source of vital information in establishing willingness to interact with a resource, reachability to make interaction possible, and compliance with relevant conditions of use.
Architectural implications of interoperability on the Semantic Infrastructure are reflected in the following capabilities:
- 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;
- tools to appropriately track users of the descriptions and notify them when a new version of the description is available.
From inherited abstract Metrics Functional Profile
Artifact Descriptions include references to metrics which describe the operational characteristics of the subjects being described
Architectural implications of metrics on the Semantic Infrastructure are reflected in the following capabilities:
- access to platform infrastructure monitoring and reporting capabilities
- access to metrics information generated or accessible by related services
- mechanisms to catalog and enable discovery of which metrics are available for a described artifact and information on how these metrics can be accessed;
- mechanisms to catalog and enable discovery of compliance records associated with policies, contracts, and constraints that are based on these metrics.
From inherited abstract Policy Functional Profile
Artifact Descriptions include references to policies defining conditions of use and optionally contracts representing agreement on policies and other conditions.
Architectural implications of policy on the Semantic Infrastructure are reflected in the following capabilities:
- descriptions to enable the policy modules to be visible, where the description includes a unique identifier for the policy and a sufficient, and preferably a machine processible, representation of the meaning of terms used to describe the policy, its functions, and its effects;
- one or more discovery mechanisms that enable searching for policies that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual policy descriptions, possibly through some repository mechanism;
- accessible storage of policies and policy descriptions, so service participants can access, examine, and use the policies as defined.
Policy capabilities are specialization of Artifact capabilities.
From inherited abstract PolicyAndContract Functional Profile
While policy and contract descriptions have much of the same architectural implications as Service Descriptions, mechanisms 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.
- 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.
From inherited abstract PolicyAndContractLanguage Functional Profile
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.
Capability Elaborations
This Functional Profile includes, but is not limited to, the following capability elaborations:
- assembly
- complianceDiscovery
- componentAcquisition
- compositionArchive
- compositionChange
- configurationManagement
- discovery
- identity
- interactionLog
- interactionResults
- interoperabilityDiscovery
- loggingPolicyModel
- metadata
- metrics
- metricsDiscovery
- monitor
- policyAdministration
- policyAlternative
- policyAssertion
- policyAudit
- policyAuthorityDelegation
- policyComposition
- policyConflictResolution
- policyConstraint
- policyDecision
- policyDecisionProcedures
- policyDistribution
- policyEnforcement
- policyMetrics
- policyObligation
- policyRefinement
- policyStore
- serviceChangeNotification
- store
- transition
- versioning
Derived From Requirements
- Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::Service Orchestration and Choreography Service orchestration and choreography allows both application developers and non-developers to discover service "building blocks" that can be composed dynamically to provide business capabilities. Special cases include the orchestration of multiple services for a distributed query, or for a transactional workflow. Service orchestration and choreography will leverage static and behavioral semantics from the Semantic Infrastructure 2.0. The Semantic Infrastructure provides the behavioral semantics required for dynamic composibility of services or generation of distributed queries. This includes runtime contract discovery and negotiation to determine composibility of services based on service capabilities and constraints. Another use case is dynamic retrieval and enforcement of the policies that are in effect for a service interaction in the areas of logging, validations, data transformation, or routing. This information can be used either during the design of the orchestration or during the execution of the defined flow. Link to use case satisfied from caGRID 2.0 Roadmap: Federated query over the TCGA data and other data sets is performed using a service orchestration.
Anchor | ||||
---|---|---|---|---|
|
Tools to facilitate identifying description elements that are to be aggregated to assemble the composite description.
Anchor | ||||
---|---|---|---|---|
|
Mechanisms to catalog and enable discovery of compliance records associated with policies, contracts, and constraints that are based on these metrics.
Anchor | ||||
---|---|---|---|---|
|
Tools to facilitate identifying the sources of information to associate with the description elements.
Anchor | ||||
---|---|---|---|---|
|
Tools to collect the identified description elements and their associated sources into a standard, referenceable format that can support general access and understanding.
Anchor | ||||
---|---|---|---|---|
|
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.
Anchor | ||||
---|---|---|---|---|
|
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.
Anchor | ||||
---|---|---|---|---|
|
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.
Anchor | ||||
---|---|---|---|---|
|
Descriptions which include a unique identifier for the artifact.
Anchor | ||||
---|---|---|---|---|
|
One or more mechanisms to capture, describe, store, discover, and retrieve interaction logs, execution contexts, and the combined interaction descriptions.
Anchor | ||||
---|---|---|---|---|
|
One or more mechanisms for attaching to any results the means to identify and retrieve the interaction description under which the results were generated.
Anchor | ||||
---|---|---|---|---|
|
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.
Anchor | ||||
---|---|---|---|---|
|
Logging Policy Model with capabilities to create, destroy, edit, maintain service descriptions.
...
- definition and configuration of Logging policy
- author policy
- store policies
- approve policies
- validate policies
- execute policies at runtimedescriptions to enable the policy modules to be visible, where the description includes a unique identifier for the policy and the metamodel
Anchor | ||||
---|---|---|---|---|
|
A representation of the meaning of terms used to describe the
...
artifact, its functions, and its effects
...
.
Anchor | ||||
---|---|---|---|---|
|
Access to metrics information generated or accessible by related services
Anchor | ||||
---|---|---|---|---|
|
Mechanisms to catalog and enable discovery of which metrics are available for a described artifact and information on how these metrics can be accessed.
Anchor | ||||
---|---|---|---|---|
|
Access to platform infrastructure monitoring and reporting capabilities.
Anchor | ||||
---|---|---|---|---|
|
Administration of policy and contract language artifacts.
Anchor | ||||
---|---|---|---|---|
|
Definition
...
of alternative policy constraints to allow for the selection of compatible policy constraints for a consumer and provider
...
.
Anchor | ||||
---|---|---|---|---|
|
Expression of assertion and commitment policy constraints.
Anchor | ||||
---|---|---|---|---|
|
Auditability of decisions, enforcement, and obligation measurements.
Anchor | ||||
---|---|---|---|---|
|
Delegation of policy authority to agents acting on behalf of a client.
Anchor | ||||
---|---|---|---|---|
|
Composition
...
of policies to combine one or more policies
...
.
Anchor | ||||
---|---|---|---|---|
|
Conflict resolution or elevation of conflicts in policy rules.
Anchor | ||||
---|---|---|---|---|
|
Expression of positive and negative policy constraints.
Anchor | ||||
---|---|---|---|---|
|
Decision procedures which must be able to measure and render decisions on constraints
...
.
Anchor | ||||
---|---|---|---|---|
|
Decision procedures capable of incorporating roles and/or attributes for rendered decisions.
Anchor | ||||
---|---|---|---|---|
|
Distribution of policies/contracts.
Anchor | ||||
---|---|---|---|---|
|
Enforcement of decisions.
Anchor | ||||
---|---|---|---|---|
|
Measurement and notification of obligation constraints.
Anchor | ||||
---|---|---|---|---|
|
Expression of permission and obligation policy constraints.
Anchor | ||||
---|---|---|---|---|
|
Nesting of policy constraints allowing for abstractions and refinements of a policy constraint.
Anchor | ||||
---|---|---|---|---|
|
Storage of policies and contracts.
Anchor | ||||
---|---|---|---|---|
|
Tools to appropriately track users of the descriptions and notify them when a new version of the description is available.
Anchor | ||||
---|---|---|---|---|
|
Accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.
Anchor | ||||
---|---|---|---|---|
|
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.
Anchor | ||||
---|---|---|---|---|
|
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
...
.
Scrollbar |
---|