Summary
Description of the profile
Service policies help establish constraints on the service specifications and mandate an approach. Policies can be specified around runtime constraints.
Runtime Constraint Policies include the following capabilities:
- creation, deletion, edit, maintenance of runtime constraint policy models
An artifact is a managed resource within the Semantic Infrastructure.
An artifact is associated with the following capabilities:
- descriptions to enable the artifact to be visible, where the description includes a unique identifier for the artifact and a sufficient, and preferably a machine processible, representation of the meaning of terms used to describe the artifact, its functions, and its effects;
- 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;
- accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.
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.
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.
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. Infrastructure services provide mechanisms to support service interaction.
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.
- 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;
- binding services that support translation and transformation of multiple application-level protocols to standard network transport protocols;
- 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
- 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;
- 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.
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.
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.
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.
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:
- 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
- runtimeConstraintPolicyModel
- security
- serviceChangeNotification
- store
- transition
- versioning
Requirements traceability
- requirement statement
- source Semantic Profile::OASIS SOA::Governance Model
- capability monitor
- from inherited abstract profile Metrics
- capability metrics
- from inherited abstract profile Metrics
- capability discovery
- from inherited abstract profile Artifact
- capability identity
- from inherited abstract profile Artifact
- capability metadata
- from inherited abstract profile Artifact
- capability store
- from inherited abstract profile Artifact
- requirement statement
- source Semantic Profile::OASIS SOA::Interacting with Services Model
- capability interactionLog
- from inherited abstract profile Interaction
- capability interactionResults
- from inherited abstract profile Interaction
- capability mediation
- from inherited abstract profile Interaction
- capability binding
- from inherited abstract profile Interaction
- capability logging
- from inherited abstract profile Interaction
- capability security
- from inherited abstract profile Interaction
- capability monitoring
- from inherited abstract profile Interaction
- requirement statement
- source Semantic Profile::OASIS SOA::Policies and Contracts Model
- capability policyAssertion
- from inherited abstract profile PolicyAndContractLanguage
- capability policyObligation
- from inherited abstract profile PolicyAndContractLanguage
- capability policyConstraint
- from inherited abstract profile PolicyAndContractLanguage
- capability policyRefinement
- from inherited abstract profile PolicyAndContractLanguage
- capability policyAlternative
- from inherited abstract profile PolicyAndContractLanguage
- capability policyComposition
- from inherited abstract profile PolicyAndContractLanguage
- capability policyEnforcement
- from inherited abstract profile PolicyAndContract
- capability policyAdministration
- from inherited abstract profile PolicyAndContract
- capability policyAudit
- from inherited abstract profile PolicyAndContract
- capability policyStore
- from inherited abstract profile PolicyAndContract
- capability policyDecision
- from inherited abstract profile PolicyAndContract
- capability policyMetrics
- from inherited abstract profile PolicyAndContract
- capability policyDistribution
- from inherited abstract profile PolicyAndContract
- capability policyConflictResolution
- from inherited abstract profile PolicyAndContract
- capability policyAuthorityDelegation
- from inherited abstract profile PolicyAndContract
- capability policyDecisionProcedures
- from inherited abstract profile PolicyAndContract
- requirement statement
- source Semantic Profile::OASIS SOA::Service Description Model
- capability versioning
- from inherited abstract profile Change
- capability configurationManagement
- from inherited abstract profile Change
- capability transition
- from inherited abstract profile Change
- capability discovery
- from inherited abstract profile Artifact
- capability identity
- from inherited abstract profile Artifact
- capability metadata
- from inherited abstract profile Artifact
- capability store
- from inherited abstract profile Artifact
- capability monitor
- from inherited abstract profile Metrics
- capability metrics
- from inherited abstract profile Metrics
- capability metricsDiscovery
- from inherited abstract profile Metrics
- capability complianceDiscovery
- from inherited abstract profile Metrics
- capability interactionLog
- from inherited abstract profile Interaction
- capability interactionResults
- from inherited abstract profile Interaction
- capability compositionArchive
- from inherited abstract profile Composition
- capability assembly
- from inherited abstract profile Composition
- capability compositionChange
- from inherited abstract profile Composition
- capability componentAcquisition
- from inherited abstract profile Composition
- capability interoperabilityDiscovery
- from inherited abstract profile Interoperability
- capability serviceChangeNotification
- from inherited abstract profile Interoperability
- requirement statement Service policies help establish constraints on the service specifications and mandate an approach. Policies can be specified around governance, access control and other design and runtime constraints.
- source Semantic Infrastructure Requirements::Service Discovery and Governance::Service Policies
- capability runtimeConstraintPolicyModel
assembly
Description
Tools to facilitate identifying description elements that are to be aggregated to assemble the composite description.
Requirements addressed
Overview of possible operations
binding
Description
binding services that support translation and transformation of multiple application-level protocols to standard network transport protocols;
Requirements addressed
Overview of possible operations
complianceDiscovery
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
componentAcquisition
Description
Tools to facilitate identifying the sources of information to associate with the description elements.
Requirements addressed
Overview of possible operations
compositionArchive
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
compositionChange
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
configurationManagement
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
discovery
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
identity
Description
Descriptions which include a unique identifier for the artifact.
Requirements addressed
Overview of possible operations
interactionLog
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
interactionResults
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
interoperabilityDiscovery
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
logging
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
mediation
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
metadata
Description
A representation of the meaning of terms used to describe the artifact, its functions, and its effects.
Requirements addressed
Overview of possible operations
metrics
Description
Access to metrics information generated or accessible by related services
Requirements addressed
Overview of possible operations
metricsDiscovery
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
monitor
Description
Access to platform infrastructure monitoring and reporting capabilities.
Requirements addressed
Overview of possible operations
monitoring
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
policyAdministration
Description
Administration of policy and contract language artifacts.
Requirements addressed
Overview of possible operations
policyAlternative
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
policyAssertion
Description
Expression of assertion and commitment policy constraints.
Requirements addressed
Overview of possible operations
policyAudit
Description
Auditability of decisions, enforcement, and obligation measurements.
Requirements addressed
Overview of possible operations
policyAuthorityDelegation
Description
Delegation of policy authority to agents acting on behalf of a client.
Requirements addressed
Overview of possible operations
policyComposition
Description
Composition of policies to combine one or more policies.
Requirements addressed
Overview of possible operations
policyConflictResolution
Description
Conflict resolution or elevation of conflicts in policy rules.
Requirements addressed
Overview of possible operations
policyConstraint
Description
Expression of positive and negative policy constraints.
Requirements addressed
Overview of possible operations
policyDecision
Description
Decision procedures which must be able to measure and render decisions on constraints.
Requirements addressed
Overview of possible operations
policyDecisionProcedures
Description
Decision procedures capable of incorporating roles and/or attributes for rendered decisions.
Requirements addressed
Overview of possible operations
policyDistribution
Description
Distribution of policies/contracts.
Requirements addressed
Overview of possible operations
policyEnforcement
Description
Enforcement of decisions.
Requirements addressed
Overview of possible operations
policyMetrics
Description
Measurement and notification of obligation constraints.
Requirements addressed
Overview of possible operations
policyObligation
Description
Expression of permission and obligation policy constraints.
Requirements addressed
Overview of possible operations
policyRefinement
Description
Nesting of policy constraints allowing for abstractions and refinements of a policy constraint.
Requirements addressed
Overview of possible operations
policyStore
Description
Storage of policies and contracts.
Requirements addressed
Overview of possible operations
runtimeConstraintPolicyModel
Description
Runtime Constraint Policy Model with capabilities to create, destroy, edit, maintain runtime constraint policy descriptions.
Requirements addressed
Overview of possible operations
security
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
serviceChangeNotification
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
store
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
transition
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
versioning
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.
