This document is
the specification for the Business Service Level Agreement for (bSLA) for
End-to-End Resource Planning (EERP), an XML vocabulary for information exchange by which a business application can manage
and evaluate services with agreed business quality of service, obligations and terms.
According to OASIS
Reference Model for Service Oriented Architecture [SOA-RM], the Service
Oriented Architecture (SOA) is a paradigm for organizing and utilizing
distributed capabilities that may be under the control of different ownership
domains. The service within SOA is a mechanism to enable access to one or more
capabilities, where the access is provided using a prescribed interface and is
exercised consistent with constraints and policies as specified by the service
description. This specification further defines the bSLA between the service
requester and the service provider for the service which is defined in SOA-RM,
within the EERP technology. The
applications of this specification are any kind of business services, and they
are not limited to only Web Services.
EERP applies the
well-known technique for service discovery and optimization in a novel way to improve business results. It
models the business process and the range of potential services, and then
guides the selection and deployment of services based on the end-to-end
business value.
Modeling the business service-level agreements to
manage and evaluate services and establishing
agreements about the business service is essential to long-term value chain
improvement. The details of the
business service level agreement defined in this bSLA specification will enable
EERP to determine the varieties of optimization to be supported, and to
manage the end-to-end business process.
The bSLA defined in this specification is the
agreement between the service requestor and the service provider, and primary
address the bQoS content defined in “SOA-EERP
Business Quality of Service Version 1.0” [EERP-bQoS],
and bRating defined in the “SOA-EERP Business Rating of Service Version
1.0” [EERP-bRating]. These contents are all business
related.
The bSLA is
different than the SLA (Service Level Agreement) in the software/IT world. The
bSLA in this specification is the contact between the service requester and the
service provider, and the SLA is the contract between the service provider and
the network/system provider. The SLA is network/system oriented agreement that
deals with network performance and system availability. The bSLA is a business oriented agreement
that deals with price, time to deliver, and the quality/rating of the service.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”,
“SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in
this document are to be interpreted as described in [RFC2119].
This specification uses the
following syntax to define outlines for detailed elements:
- The
syntax appears as an XML instance, but values in italics indicate data
types instead of literal values.
- Characters
are appended to elements and attributes to indicate cardinality:
- "?"
(0 or 1)
- "*"
(0 or more)
- "+"
(1 or more)
- The
character "|" is used to indicate a choice between alternatives.
- The
characters "(" and ")" are used to indicate that
contained items are to be treated as a group with respect to cardinality
or choice.
- The
characters "[" and "]" are used to call out references
and property names.
- Ellipses
(i.e., "...") indicate points of extensibility. Additional
children and/or attributes MAY be added at the indicated extension points
but MUST NOT contradict the semantics of the parent and/or owner,
respectively. By default, if a receiver does not recognize an extension,
the receiver SHOULD ignore the extension; exceptions to this processing
rule, if any, are clearly indicated below.
- XML
namespace prefixes (see Table 1) are used to indicate the namespace of the
element being defined.
Elements and Attributes defined by this specification are
referred to in the text of this document using XPath 1.0 expressions.
Extensibility points are referred to using an extended version of this syntax:
·
An element extensibility point is referred to using {any}
in place of the element name. This indicates that any element name can be used,
from any namespace other than the namespace of this specification.
·
An attribute extensibility point is referred to using
@{any} in place of the attribute name. This indicates that any attribute name
can be used, from any namespace other than the namespace of this specification.
Extensibility points in the exemplar may not be described in
the corresponding text.
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate
Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt,
IETF RFC 2119, March 1997.
[SOAP] W3C Note, "SOAP: Simple
Object Access Protocol 1.1", 08 May 2000.
http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
[SOAP12] W3C Recommendation, "SOAP 1.2
Part 1: Messaging Framework", 24 June 2003.
http://www.w3.org/TR/2003/REC-soap12-part1-20030624/
[URI] T. Berners-Lee, R.
Fielding, L. Masinter, "Uniform Resource Identifiers (URI): Generic
Syntax", RFC 3986, MIT/LCS, Day Software, Adobe Systems, January 2005.
http://www.ietf.org/rfc/rfc3986.txt
[UBL-20] OASIS Standard,
“Universal Business Language (UBL) v2.0”, 12 December 2006
http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.pdf
[UBL-20-cbc] Universal
Business Language (UBL) v2.0, Common Basic Components. October 2006.
http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UBL-CommonBasicComponents-2.0.xsd
[UBL-20-udt] Universal
Business Language (UBL) v2.0. Unqualified Data Type, February 2005.
http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UnqualifiedDataTypeSchemaModule-2.0.xsd
[XML-Schema1] W3C Recommendation, "XML Schema Part
1: Structures Second Edition", 28 October 2004.
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/
[XML-Schema2] W3C Recommendation, "XML Schema Part
2: Datatypes Second Edition", 28 October 2004.
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/
[EERP-bQoS] OASIS Committee Draft 04,
“SOA-EERP Business Quality of Service Version 1.0”, 12 September 2010.
http://docs.oasis-open.org/soa-eerp/bqos/v1.0/SOA-EERP-bQoS-Spec-cd04.pdf
[EERP-bRating] OASIS Committee Draft 04, “SOA-EERP
Business Rating of Service Version 1.0”, 12 September 2010.
http://docs.oasis-open.org/soa-eerp/rt/v1.0/SOA-EERP-bRating-Spec-cd04.pdf
[ISO8601] ISO Standard 8601:2004(E),
"Data elements and interchange formats – Information interchange -
Representation of dates and times", Third edition, December 2004.
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=40874
[CEFACT] CEFACT – Core
components specifications, Recommendation 9 January
1996.
http://www.unece.org/cefact/recommendations/rec09/rec09_ecetrd203.pdf
In this document reference is made to some basic elements and
data types in UBL 2.0, in the following schema:
·
UBL 2.0 Common Basic Components [UBL-20-cbc], UBL-CommonBasicComponents-2.0.xsd
·
UBL 2.0 Unqualified Data Type [UBL-20-udt],
UnqualifiedDataTypeSchemaModule-2.0.xsd
In addition, this document also reference to some elements
defined in SOA-EERP Business Quality of Service Version 1.0.
This specification is designed to work with the general Web
Services framework including WSDL service descriptions, and SOAP
message structure and message processing model. The XML vocabulary defined in bSLA should be applicable to any
version of SOAP.
1.3 Non-Normative References
None.
2
Business Services Level Agreement Contents
The Business Service Level Agreement (bSLA) of the XML
vocabulary is defined in XML Schema format that has information on both
requester and service provider and their agreement on the service level.
The
XML namespace URI that MUST be used by implementations of this specification
is:
http://docs.oasis-open.org/ns/soa-eerp/sla/200903
Table 1 lists XML namespaces that
are used in this specification. The choice of any namespace prefix is arbitrary
and not semantically significant.
Table 1:
Prefixes and XML Namespaces used in this specification.
|
Prefix
|
Namespace
|
Specification(s)
|
|
S
|
http://schemas.xmlsoap.org/soap/envelope/
|
[SOAP]
|
|
S12
|
http://www.w3.org/2003/05/soap-envelope
|
[SOAP12]
|
|
xsd
|
http://www.w3.org/2001/XMLSchema
|
[XML-Schema1], [XML-Schema2]
|
|
cbc
|
urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2
|
[UBL-20-cbc]
|
|
udt
|
urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2
|
[UBL-20-udt]
|
|
ccts
|
urn:un:unece:uncefact:documentation:2
|
[UBL-20]
|
|
bqos
|
http://docs.oasis-open.org/ns/soa-eerp/bqos/200903
|
[EERP-bQoS]
|
|
sla
|
http://docs.oasis-open.org/ns/soa-eerp/sla/200903
|
This specification
|
A normative copy of the XML Schema [XML-Schema1,
XML-Schema2] description for this specification can
be retrieved from the following address:
http://docs.oasis-open.org/soa-eerp/sla/v1.0/EERP-bSLA-cd04.xsd
The
BSLA is the root element for EERP- Business Service-level agreement (bSLA). The
bSLA is a formal contract between a service provider and a client guaranteeing
quantifiable business quality of service (bQoS) at defined levels. It can have
one or more of the following elements:
·
SLAParties describes the parties
invoked in the bSLA for the service
·
SLAParameters describes the parameters
for the service, which are defined ways of monitoring of bQoS metrics.
·
SLAObligations describes the agreed
bSLA obligations for the service.
·
SLATerms describes the agreed bSLA
Terms for the service.
·
Any additional elements for the
agreement of the service
Syntax
<sla:BSLA
xmlns:sla="..."
xmlns:bqos="..." ...>
<sla:SLAParties ...>sla:SLAPartiesTypeType</sla:SLAParties>
<sla:SLAParameters ...>sla:SLAParametersType</sla:SLAParameters>
<sla:SLAObligations ...>sla:SLAObligationsType</sla:SLAObligations>
?
<sla:SLATerms ...>sla:SLATermsType</sla:SLATerms>
?
...
</sla:BSLA>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:BSLA
Root element of Business Service-level
agreement (bSLA) for EERP
/sla:BSLA/sla:SLAParties
SLAParties is a required element in
bSLA that defines parties invoked in this bSLA for the service. SLAParties
element has both the service provider and services requester elements, see
Section 3 for more details.
/sla:BSLA/sla:SLAParties/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the SLAParties element in the future. Unrecognized attributes
MAY cause a fault or be silently ignored.
/sla:BSLA/sla:SLAParameters
SLAParameters element, bSLA parameters aspect of the
service, is defined monitoring of bQoS metrics, including service profile uri,
operations and other optional elements. It is a required element that uses
sla:SLAParametersType, see Section 4 for more details.
/sla:BSLA/sla:SLAParameters/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the SLAParameters
element in the future. Unrecognized attributes MAY cause a fault or be silently
ignored.
/sla:BSLA/sla:SLAObligations
Agreed bSLA obligations aspect of the
service, including obligations, action guarantees. It is a optional element
that uses sla:SLAObligationsType, see Section 5 for more details.
/sla:BSLA/sla:SLAObligations/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the SLAObligations
element in the future. Unrecognized attributes MAY cause a fault or be silently
ignored.
/sla:BSLA/sla:SLATerms
Agreed bSLA terms aspect of the service, including bSLA
term elements. It is optional, see Section 6 for more details.
/sla:BSLA/sla:SLATerms/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the SLATerms
element in the future. Unrecognized attributes MAY cause a fault or be silently
ignored.
/sla:BSLA/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the root BSLA element in the future. Unrecognized attributes MAY
cause a fault or be silently ignored.
/sla:BSLA/sla:BSLAExtension
BSLAExtension
element is an optional element that keeps different (extensible) elements to be
specified in the future.
/sla:BSLA/sla:BSLAExtension/{any}
This is an
extensibility mechanism to allow different (extensible) elements to be
specified in the future. Unrecognized elements MAY cause a fault or be silently
ignored.
The
SLAParties describes the
list of parties invoked in the bSLA for the service.
There SHOULD be one SLAParties element
present in the bSLA of service.
Syntax
<sla:SLAParties xmlns:sla="..."
...>
<sla:ServiceProvider ...>sla:ServiceProviderType
<sla:ServiceUri ...>sla:SlaUriType</sla:ServiceUri>
<sla:ServiceProviderName languageID="...">sla:ServiceProviderNameType</sla:ServiceProviderName>
</sla:ServiceProvider>
<sla:ServiceRequester ... >sla:ServiceRequesterType
<sla:ServiceRequesterUri ... >sla:SlaUriType</sla:ServiceRequesterUri>
<sla:ServiceRequesterName
languageID="...">sla:ServiceRequesterNameType</sla:ServiceRequesterName>
</sla:ServiceRequester>
...
</sla:SLAParties>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLAParties
SLAParties element, bSLA Parties aspect
of the service, is for parties invoked in the bSLA for the service, including
both service provider and service requester elements.
/sla:SLAParties/sla:ServiceProvider
Service Provider element
represents the provider for parties. It is a required element for bSLA Parties.
/sla:SLAParties/sla:ServiceProvider/sla:ServiceUri
Service identifier in URI format, such
as a service URL, is a required element for Service Provider.
/sla:SLAParties/sla:ServiceProvider/sla:ServiceProviderName
Service Provider Name is the name of
the service provider. It is also a required element for Service Provider.
/sla:SLAParties/sla:ServiceProvider/sla:ServiceProviderName/@languageID
Language ID is an optional attribute in
the ServiceProviderName element, using xsd:language type. The value can be those
defined in urn:un:unece:uncefact:codelist:specification:5639:1988.
/sla:SLAParties/sla:ServiceProvider/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the ServiceProvider element in the future. Unrecognized
attributes MAY cause a fault or be silently ignored.
/sla:SLAParties/sla:ServiceRequester
ServiceRequester element
represents requester for the service, including requester’s name and the URI
that represents the requester. It is a required element for bSLA Parties.
/sla:SLAParties/sla:ServiceRequester/sla:ServiceRequesterUri
ServiceRequesterUri element
represents the requester’s identifier in URI format for the service requester.
It is a required element for Service Requester.
/sla:SLAParties/sla:ServiceRequester/sla:ServiceRequesterName
Requester’s name for the service
requester. It is a required element for Service Requester.
/sla:SLAParties/sla:ServiceRequester/sla:ServiceRequesterName/@languageID
Language ID is an optional attribute in
the ServiceRequesterName element, using xsd:language type. The value can be those
defined in urn:un:unece:uncefact:codelist:specification:5639:1988.
/sla:SLAParties/sla:ServiceRequester/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the ServiceRequester element in the future. Unrecognized
attributes MAY cause a fault or be silently ignored.
/sla:SLAParties/{any}
This is an
extensibility mechanism to allow different (extensible) elements to be
specified in the future. Unrecognized elements MAY cause a fault or be silently
ignored.
Example
The following non-normative example
illustrates the use of the bSLA Parties element. The Service Provider is a
fictitious Hangzhou Innover Co. Ltd. in China; the Service Requester is a
fictitious Mianyang Gas Corp. in China.
(001) <?xml
version="1.0" encoding="utf-8"?>
(002) <SLAParties xmlns="..." ...>
(003)
<ServiceProvider>
(004)
<ServiceUri>http://www.innover.com.cn</ServiceUri>
(005)
<ServiceProviderName>Hangzhou Innover Co.
Ltd</ServiceProviderName>
(006)
</ServiceProvider>
(007)
<ServiceRequester>
(008)
<ServiceRequesterUri>http://www.scmyng.com</ServiceRequesterUri>
(009)
<ServiceRequesterName>Mianyang Gas
Corp.</ServiceRequesterName>
(010)
</ServiceRequester>
(011) </SLAParties>
The
SLAParameters element for
EERP-bSLA describes the
parameters of
the service used to define monitoring of bQoS metrics, including the service
profile URI, operations and other optional elements.
There SHOULD be one SLAParameters element
present in the bSLA of service.
Syntax
<sla:SLAParameters
xmlns:sla="..."
...>
<sla:ServiceProfileUri ...>sla:SlaUriType</sla:ServiceProfileUri>
<sla:ServiceOperations ...>sla:ServiceOperationsType
<sla:hasCommittedCost>xsd:boolean</sla:hasCommittedCost>
<sla:hasCommittedTime>xsd:boolean</sla:hasCommittedTime>
<sla:hasAvailabilities>xsd:boolean</sla:hasAvailabilities>
<sla:hasCommittedTroughput>xsd:boolean</sla:hasCommittedTroughput>
<sla:hasOtherTerms>xsd:boolean</sla:hasOtherTerms>
...
</sla:ServiceOperations> ?
...
</sla:SLAParameters>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLAParameters
bSLA
parameters element defines aspect of the service which are defined monitoring
of bQoS metrics, including service uri, operations and other optional elements.
/sla:SLAParameters/sla:ServiceProfileUri
ServiceProfileUri
element represents web page URL or other URI for the service profile that
defines the details of the services. Different service providers will share the
same profile. It is a required element for bSLA Parameters.
/sla:SLAParameters/sla:ServiceProfileUri/@{any}
This is an extensibility mechanism to allow
additional attributes, based on schemas, to be added to the ServiceProfileUri
element in the future. Unrecognized attributes MAY cause a fault or be silently
ignored.
/sla:SLAParameters/sla:ServiceOperations
Describes
available operations and bQoS. It is an optional element for bSLA Parameters.
/sla:SLAParameters/sla:ServiceOperations/sla:hasCommittedCost
Describes
if there is committed cost or not. It is a required element for bSLA
Parameters.
/sla:SLAParameters/sla:ServiceOperations/sla:hasCommittedTime
Describes
if there is committed time or not. It is a required element for bSLA
Parameters.
/sla:SLAParameters/sla:ServiceOperations/sla:hasAvailabilities
Describes
if there is availability or not. It is a required element for bSLA Parameters.
/sla:SLAParameters/sla:ServiceOperations/sla:hasCommittedThroughput
Describes
if there is committed throughput or not. It is a required element for bSLA
Parameters.
/sla:SLAParameters/sla:ServiceOperations/sla:hasOtherTerms
Describes
if there are other terms or not. It is a required element for bSLA Parameters.
/sla:SLAParameters/sla:ServiceOperations/{any}
This
is an extensibility mechanism to allow different (extensible) property or
attribute elements to be specified in the future. Unrecognized elements MAY
cause a fault or be silently ignored.
/sla:SLAParameters /sla:ServiceOperations/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the ServiceOperations element in the future. Unrecognized
attributes MAY cause a fault or be silently ignored.
/sla:SLAParameters /{any}
This
is an extensibility mechanism to allow different (extensible) property or
attribute elements to be specified in the future. Unrecognized elements MAY
cause a fault or be silently ignored.
Example
The
following non-normative example illustrates the use of bSLA Parameters element. It
describes the bSLA parameters:
(001) <?xml
version="1.0" encoding="utf-8"?>
(002) <SLAParameters xmlns="..." ...>
(003)
<ServiceProfileUri>http://www.innover.com.cn</ServiceProfileUri>
(004)
<ServiceOperations>
(005)
<hasCommittedCost>true</hasCommittedCost>
(006)
<hasCommittedTime>true</hasCommittedTime>
(007)
<hasAvailabilities>true</hasAvailabilities>
(008)
<hasCommittedTroughput>true</hasCommittedTroughput>
(009) <hasOtherTerms>true</hasOtherTerms>
(010)
</ServiceOperations>
(011) </SLAParameters>
The
SLAObligations element
describes the agreed bSLA obligations of the service, including obligations and
action guarantees.
There MAY be zero or one bSLA Obligations element present in the bSLA of
service.
Note: There is a case for zero Obligation elements on bSLA.
Section 7.2 is an example illustrates the bSLA document without Obligation
element. It has some additional bSLA terms instead.
Syntax
<sla:SLAObligations xmlns:sla="..."
xmlns:bqos="..." ...>
<sla:Obligation ...>sla:ObligationType</sla:Obligation>
+
<sla:ActionGuarantee ...>sla:ActionGuaranteeType</sla:ActionGuarantee>
?
...
</sla:SLAObligations>
The following describes the attributes
and elements listed in the schema outlined above:
/sla:SLAObligations
bSLA obligations aspect of the service,
including obligations, action guarantees.
/sla:SLAObligations/sla:Obligation
Obligation element is agreed bSLA
obligation, including Service Level Objective (SLO) and the Action Guarantee
that associates with that SLO. There MAY be one or more obligation elements in
the SLAObligations element. See Section 5.1 for more details.
/sla:SLAObligations/sla:Obligation/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the Obligation element in the future. Unrecognized attributes
MAY cause a fault or be silently ignored.
/sla:SLAObligations/sla:ActionGuarantee
Specify what happens if the Service
Level Objective (SLO) is met or not met. This guarantee will be associated to
all Obligations within the SLAObligations element. It is an optional element
for the SLAObligations element. See Section 5.2 for more details.
/sla:SLAObligations/sla:ActionGuarantee/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the ActionGuarantee element in the future. Unrecognized
attributes MAY cause a fault or be silently ignored.
/sla:SLAObligations/{any}
This
is an extensibility mechanism to allow different (extensible) property or
attribute elements to be specified in the future. Unrecognized elements MAY
cause a fault or be silently ignored.
The
Obligation, obligation element for
bSLA Obligations in EERP-bSLA, is the agreed bSLA obligation, including Service
Level Objective (SLO) and the Action Guarantee that associates with that SLO.
There MAY be one or more Obligation elements
present in the bSLA
Obligations.
Syntax
<sla:Obligation xmlns:sla="..."
xmlns:bqos="..." ...>
<sla:ServiceLevelObjective ...>sla:ServiceLevelObjectiveType
</sla:ServiceLevelObjective>
<sla:ActionGuarantee ...>sla:ActionGuaranteeType</sla:ActionGuarantee>
?
</sla:Obligation>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLAObligations/sla:Obligation
Obligation element is agreed bSLA
obligation, including Service Level Objective (SLO) and the Action Guarantee
that associates with this Obligation.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective
Service Level Objective (SLO) for QoS
guarantee. It is a required element for Obligation. See Section 5.1.1 for more
details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the ServiceLevelObjective element in the future. Unrecognized
attributes MAY cause a fault or be silently ignored.
/sla:SLAObligations/sla:Obligation/sla:ActionGuarantee
Service Level Objective (SLO) for QoS
guarantee. This guarantee will be associated to all ServiceLevelObjective
within this Obligation element. It is an optional element for Obligation. See
Section 5.1.2 for more details.
/sla:SLAObligations/sla:Obligation/sla:ActionGuarantee/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the ActionGuarantee element in the future. Unrecognized
attributes MAY cause a fault or be silently ignored.
The
Service Level Objective element for Obligation in bSLA
Obligations in EERP-bSLA is the Service Level Objective (SLO) for the QoS
guarantee, including Committed Cost, Committed Time, Availabilities, Committed
Throughput and SLATerm.
There SHOULD be one Service
Level Objective
element present in the Obligation,
and it can have one and more element within this Service Level Objective element.
Syntax
<sla:ServiceLevelObjective xmlns:sla="..."
xmlns:bqos="..." ...>
<sla:CommittedCost>bqos:PriceType</sla:CommittedCost>
?
<sla:CommittedTime ...>sla:CommittedTimeType</sla:CommittedTime>
?
<sla:Availabilities ...>sla:AvailabilitiesType</sla:Availabilities>
?
<sla:CommittedThroughput ...>bqos:ThroughputType</sla:CommittedThroughput>
?
<sla:SLATerm ...>sla:SLATermType</sla:SLATerm>
?
</sla:ServiceLevelObjective>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective
Service Level Objective (SLO) for QoS
guarantee. It is a required element for Obligation.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCost
Cost element in bSLA. It is an optional
element for ServiceLevelObjective. See Section 5.1.1.1 for more details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime
Committed time period element in bSLA
is an optional element for ServiceLevelObjective. see Section 5.1.1.2 for more
details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the CommittedTime element in the future. Unrecognized attributes
MAY cause a fault or be silently ignored.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities
The services availability indicators
element, including a list of availabilities, is an optional element for
ServiceLevelObjective, see Section 5.1.1.3 for more details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the Availabilities element in the future. Unrecognized
attributes MAY cause a fault or be silently ignored.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput
Committed performance throughput is an
optional element for ServiceLevelObjective. See Section 5.1.1.4 for more
details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the CommittedThroughput element in the future. Unrecognized
attributes MAY cause a fault or be silently ignored.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:SLATerm
bSLA Term. It is an optional element
for ServiceLevelObjective, see
/sla:SLATerms/sla:SLATerm in Section 6 for more details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:SLATerm
/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the SLATerm element in the future. Unrecognized attributes MAY
cause a fault or be silently ignored.
The
Committed Cost
element describes the cost element in bSLA, including Unit and Amount.
There
MAY be zero or one Committed Cost element present in the Service Level
Objective.
Syntax
<sla:CommittedCost
xmlns:sla="..." xmlns:bqos="...">
<bqos:Unit unitCode="clm66411:UnitCodeContentType">
cbc:BaseUnitMeasureType
</bqos:Unit> ?
<bqos:Amount currencyID="clm54217:CurrencyCodeContentType">
cbc:AmountType
</bqos:Amount>
</sla:CommittedCost>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCost
CommittedCost element is the cost
element in bSLA. It is an optional element for Service Level Objective.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCost/bqos:Unit
Number of unit is a optional element
that includes a attribute of unit of measurement uses cbc:BaseUnitMeasureType.
See /bqos:BQoSPrice/bqos:Price/bqos:Unit
in Section 3: BQoS Price in EERP-bQoS Specification for more
details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCost/bqos:Amount
Amount element is a required element
for the Committed Cost element. It uses cbc:AmountType from UBL that has a
required currencyID attribute for currency code. See /bqos:BQoSPrice/bqos:Price/bqos:Amount in Section 3: BQoS Price
in EERP-bQoS Specification for more details.
The
Committed Time,
Committed Time
element of Service Level Objective for Obligation in bSLA Obligations in EERP-bSLA, is the committed time
period in bSLA, including Duration, Latency and Committed Completion
Time.
There MAY be zero or one Committed
Time
element present in the Service Level Objective.
Syntax
<sla:CommittedTime
xmlns:sla="..." xmlns:bqos="..." ...>
<bqos:Duration unitCode="clm66411:UnitCodeContentType">
cbc:DurationMeasureType
</bqos:Duration>
<bqos:Latency unitCode="clm66411:UnitCodeContentType">
cbc:DurationMeasureType
</bqos:Latency> ?
<bqos:StartTime>udt:DateTimeType</bqos:StartTime>
?
<sla:CommittedCompletionTime>
udt:DateTimeType</sla:CommittedCompletionTime>
?
</sla:CommittedTime>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime
CommittedTime element is an optional
element for Service Level Objective which is the committed time period element
in bSLA.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/bqos:Duration
Duration element is a required element
in the CommittedTime element which is the duration to complete the service. It
uses cbc:DurationMeasureType from UBL that has a required unitCode attribute for unit of measurement on the
time. See /bqos:BQoSPerformance/bqos:TimePeriod/bqos:Duration in Section 4: bQoS Performance
in EERP-bQoS Specification for more details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/bqos:Latency
Latency is an optional element for the
time delay for starting the service. It uses cbc:DurationMeasureType from UBL
that has a required unitCode attribute for unit of measurement on the time. See
/bqos:BQoSPerformance/bqos:TimePeriod/bqos:Latency
in Section 4: bQoS Performance in EERP-bQoS Specification for more
details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/bqos:StartTime
StartTime is an optional element for
the date and time to start the service. It uses udt:DateTimeType which is in
UTC time format [ISO8601].. See /bqos:BQoSPerformance/bqos:TimePeriod/bqos:StartTime
in Section 4: bQoS Performance in EERP-bQoS Specification for more
details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTime/sla:CommittedCompletionTime
CommittedCompletionTime
is an optional element for the date and time for committed completion time. It
uses udt:DateTimeType which is UTC time
format [ISO8601]..
The
Availabilities,
Availabilities
of Service Level Objective for Obligation in bSLA
Obligations in EERP-bSLA, is services availability indicators including a list
of availabilities, including a list of Availability elements.
There MAY be zero or one Availabilities element
present in the Service Level Objective.
Syntax
<sla:Availabilities
xmlns:sla="..." xmlns:bqos="..." ...>
<sla:Availability
isAvailable="xs:boolean"
...>sla:AvailabilityType
<sla:From>xs:dateTime</sla:From>
<sla:To>xs:dateTime</sla:To>
</sla:Availability> +
</sla:Availabilities>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities
Availabilities is an optional element
for Service Level Objective which is the services availability indicators
including a list of availabilities.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability
Availability
is a required element for the quality aspect of whether the service is present
or ready for immediate use.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability/sla:From
From
is a required element for the date and time for availability starting time. It
uses udt:DateTimeType which is UTC time
format [ISO8601]..
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability/sla:To
To
is a required element for the date and time for availability ending time. It
uses udt:DateTimeType which UTC time
format [ISO8601]..
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability/@isAvailable
isAvailable
is an optional attribute to illustrate whether the Availability is available or
not. It uses xs:boolean type.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:Availabilities/sla:Availability/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the Availability element in the future. Unrecognized attributes
MAY cause a fault or be silently ignored.
The
Committed Throughput, Committed Throughput element of Service Level
Objective
for Obligation in bSLA
Obligations in EERP-bSLA, is the committed performance throughput, including Duration, Quantity and Latency.
There MAY be zero or one Committed
Throughput
element present in the Service Level Objective.
Syntax
<sla:CommittedThroughput
xmlns:sla="..."
xmlns:bqos="..." ...>
<bqos:Duration unitCode="clm66411:UnitCodeContentType">
cbc:DurationMeasureType</bqos:Duration>
<bqos:Quantity unitCode="clm66411:UnitCodeContentType">
cbc:BaseQuantityType</bqos:Quantity>
<bqos:Latency unitCode="clm66411:UnitCodeContentType">
cbc:DurationMeasureType</bqos:Latency>
?
</sla:CommittedThroughput>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput
CommittedThroughput is an optional element for
ServiceLevelObjective element. This is the committed performance throughput.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput/bqos:Duration
Duration element is a required element in
the CommittedThroughput element. This is
the duration to complete the service. It uses cbc:DurationMeasureType from UBL
that has a required unitCode attribute
for unit of measurement on the time. See
/bqos:BQoSPerformance/bqos:Throughput/bqos:Duration
in Section 4: bQoS Performance in EERP-bQoS Specification for more
details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput/bqos:Quantity
Quantity is a required element in the
Throughput element. It is the numbers for
the throughput, with an attribute of unit of measurement, such as EA, pounds,
cubic-feet, etc. See /bqos:BQoSPerformance/bqos:Throughput/bqos:Quantity
in Section 4: bQoS Performance in EERP-bQoS Specification for more
details.
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedThroughput/bqos:Latency
Latency is an optional element for the
time delay for starting the service. It uses cbc:DurationMeasureType from UBL
that has a required unitCode attribute for unit of measurement on the
time. See /bqos:BQoSPerformance/bqos:Throughput/bqos:Latency in Section 4: bQoS Performance
in EERP-bQoS Specification for more details.
The
bSLATerm, bSLA Term element of Service Level Objective for Obligation in bSLA
Obligations in EERP-bSLA, is the bSLA term element in bSLA.
There MAY be zero or one bSLA
Term
element present in the Service Level Objective. See /sla:SLATerms/sla:SLATerm
in Section 6 for more details.
The
Action Guarantee, action
guarantee
element for bSLA Obligations in EERP-bSLA, is to specify what happens if the
SLO is met or not met, including Reserve Fee and Penalty element.
There MAY be zero or one Action
Guarantee element
present in the Obligation
element.
See Section 5.2 for the detail of ActionGuaranteeType.
The
Action Guarantee, action guarantee element for
bSLA Obligations in EERP-bSLA, is to specify what happens if the Service
Level Objective
(SLO) is met or not met, including Reserve Fee and Penalty element.
There MAY be zero or one bSLA Obligations element
present in the bSLA
Obligations.
Syntax
<sla:ActionGuarantee
xmlns:sla="..."
xmlns:bqos="..." ...>
<sla:ReserveFee ...>bqos:PriceType
<bqos:Unit unitCode="clm66411:UnitCodeContentType">
cbc:BaseUnitMeasureType</bqos:Unit>
?
<bqos:Amount currencyID="clm54217:CurrencyCodeContentType">
cbc:AmountType</bqos:Amount>
</sla:ReserveFee> ?
<sla:Penalty ...>bqos:PriceType
<bqos:Unit unitCode="clm66411:UnitCodeContentType">
cbc:BaseUnitMeasureType</bqos:Unit>
?
<bqos:Amount currencyID="clm54217:CurrencyCodeContentType">
cbc:AmountType</bqos:Amount>
</sla:Penalty> ?
</sla:ActionGuarantee
>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLAObligations/sla:ActionGuarantee/sla:ReserveFee
ReserveFee
element is the reservation fee or money amount when Service Level Objective
(SLO) is met. It is an optional element for Action Guarantee.
/sla:SLAObligations/sla:ActionGuarantee/sla:ReserveFee/bqos:Unit
Number of unit is a optional element
that includes a attribute of unit of measurement uses cbc:BaseUnitMeasureType.
See /bqos:BQoSPrice/bqos:Price/bqos:Unit
in Section 3: bQoS Price in EERP-bQoS Specification for more details.
/sla:SLAObligations/sla:ActionGuarantee/sla:ReserveFee/bqos:Amount
Amount element is a required element
for the Reserve Fee element. It uses cbc:AmountType from UBL that has a
required currencyID attribute for currency code. See /bqos:BQoSPrice/bqos:Price/bqos:Amount in Section 3: bQoS Price
in EERP-bQoS Specification for more details.
/sla:SLAObligations/sla:ActionGuarantee/sla:ReserveFee/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the ReserveFee element in the future. Unrecognized attributes
MAY cause a fault or be silently ignored.
/sla:SLAObligations/sla:ActionGuarantee/sla:Penalty
Penalty
element is the money amount when Service Level Objective (SLO) is not met. It
is a required element for Action Guarantee.
/sla:SLAObligations/sla:ActionGuarantee/sla:Penalty/bqos:Unit
Number of unit is a optional element
that includes a attribute of unit of measurement uses cbc:BaseUnitMeasureType.
See /bqos:BQoSPrice/bqos:Price/bqos:Unit
in Section 3: bQoS Price in EERP-bQoS Specification for more
details.
/sla:SLAObligations/sla:ActionGuarantee/sla:Penalty/bqos:Amount
Amount element is a required element
for the Penalty element. It uses cbc:AmountType from UBL that has a required currencyID
attribute for currency code. See /bqos:BQoSPrice/bqos:Price/bqos:Amount
in Section 3: bQoS Price in EERP-bQoS Specification for more
details.
/sla:SLAObligations/sla:ActionGuarantee/sla:Penalty/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the Penalty element in the future. Unrecognized attributes MAY
cause a fault or be silently ignored.
Example
The
following example illustrates the use of Action Guarantee element. It describes
the penalty:
(001) <?xml version="1.0"
encoding="utf-8"?>
(002) <ActionGuarantee xmlns="..."
xmlns:bqos="..." ...>
(003) <Penalty>
(004) <bqos:Unit
unitCode="EA">10</bqos:Unit>
(005)
<bqos:Amount currencyID="USD">17.15</bqos:Amount>
(006) </Penalty>
(007) </ActionGuarantee>
The
SLATerms,
bSLA terms
element for EERP-bSLA, is the agreed
bSLA terms aspect of the service, including bSLA term elements.
There MAY be zero or one bSLA
Terms element
present in the bSLA of service.
Syntax
<sla:SLATerms xmlns:bqos="..." ...>
<sla:SLATerm ...>sla:SLATermType
...
</sla:SLATerm> +
</sla:SLATerms>
The
following describes the attributes and elements listed in the schema outlined
above:
/sla:SLATerms
The agreed bSLA terms aspect of the
service, including bSLA term elements. It has a list of bSLA terms for SLATerms
.
/sla:SLATerms/sla:SLATerm
SLATerm element is an any type element
to describe additional term for this bSLA.
/sla:SLATerms/sla:SLATerm
/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the SLATerm element in the future. Unrecognized attributes MAY
cause a fault or be silently ignored.
/sla:SLATerms/sla:SLATerm/{any}
This
is an extensibility mechanism to allow different (extensible) property or
attribute elements to be specified in the future. Unrecognized elements MAY
cause a fault or be silently ignored.
/sla:SLATerms/@{any}
This
is an extensibility mechanism to allow additional attributes, based on schemas,
to be added to the SLATerms element in the future. Unrecognized attributes MAY
cause a fault or be silently ignored.
Example
The
following non-normative example illustrates the use of bSLA Terms element. It
describes the term of the bSLA:
(001) <?xml version="1.0"
encoding="utf-8"?>
(002) <SLATerms xmlns="..." ...>
(003) <SLATerm xmlns:t="..." >
(004) <t:ServcieLocation>
(005) <t:Lat>37.7749295</t:Lat>
(006)
<t:Lng>-122.4194155</t:Lng>
(007)
</t:ServcieLocation>
(008)
</SLATerm>
(009) </SLATerms>
The examples in this section are
non-normative.
This bSLA example will show the following agreement between
EERP Sample Service and EERP Service Requester:
1. The service is based on the Service
profile defined on http://www.serviceprovider.com/eerp/service/profile
2. It will charge $17.15 per service.
3. Starting from January 1st,
2009, the agreement last for one whole year.
4. The committed throughput is 10 services
per day.
5. If the provider cannot meet the bSLA
for #3 and #4, the penalty will be $17.15 per 10 services.
Example
The
following example illustrates the whole bSLA document for above agreements:
(1)
<?xml version="1.0"
encoding="utf-8"?>
(2)
<BSLA xmlns="..."
xmlns:bqos="..." ... >
(3)
<SLAParties>
(4)
<ServiceProvider>
(5)
<ServiceUri>
(6)
http://www.serviceprovider.com/eerp/service</ServiceUri>
(7)
<ServiceProviderName
languageID="EN">
(8)
EERP Sample
Service</ServiceProviderName>
(9)
</ServiceProvider>
(10) <ServiceRequester>
(11) <ServiceRequesterUri>
(12) http://www.servicerequester.com</ServiceRequesterUri>
(13) <ServiceRequesterName
languageID="EN">
(14) EERP Service
Requester</ServiceRequesterName>
(15) </ServiceRequester>
(16) </SLAParties>
(17) <SLAParameters>
(18) <ServiceProfileUri>
(19) http://www.serviceprovider.com/eerp/service/profile</ServiceProfileUri>
(20) <ServiceOperations>
(21) <hasCommittedCost>true</hasCommittedCost>
(22) <hasCommittedTime>true</hasCommittedTime>
(23) <hasAvailabilities>false</hasAvailabilities>
(24) <hasCommittedTroughput>true</hasCommittedTroughput>
(25) <hasOtherTerms>false</hasOtherTerms>
(26) </ServiceOperations>
(27) </SLAParameters>
(28) <SLAObligations>
(29) <Obligation>
(30) <ServiceLevelObjective>
(31) <CommittedCost>
(32) <bqos:Unit
unitCode="EA">1</bqos:Unit>
(33) <bqos:Amount
currencyID="USD">17.15</bqos:Amount>
(34) </CommittedCost>
(35) </ServiceLevelObjective>
(36) </Obligation>
(37) <Obligation>
(38) <ServiceLevelObjective>
(39) <CommittedTime>
(40)
<bqos:Duration
unitCode="ANN">1</bqos:Duration>
(41)
<bqos:StartTime>2009-01-01T00:00:00Z</bqos:StartTime>
(42) </CommittedTime>
(43) <CommittedThroughput>
(44) <bqos:Duration
unitCode="DAY">1</bqos:Duration>
(45) <bqos:Quantity
unitCode="EA">10</bqos:Quantity>
(46) </CommittedThroughput>
(47) </ServiceLevelObjective>
(48) <ActionGuarantee>
(49) <Penalty>
(50) <bqos:Unit
unitCode="EA">10</bqos:Unit>
(51) <bqos:Amount
currencyID="USD">17.15</bqos:Amount>
(52) </Penalty>
(53) </ActionGuarantee>
(54) </Obligation>
(55) </SLAObligations>
(56) </BSLA>
This bSLA example will show the following agreement between
EERP Sample Service and EERP Service Requester:
1. The service is based on the Service
profile defined on http://www.serviceprovider.com/eerp/service/profile2
2. There is no obligation
3. Additional bSLA terms include service
location and service hours:
a. Service location is near San Francisco,
CA with geocoding of 37.7749295 and
-122.4194155
b. Service hours will be 7 x 24, that is 7
days per week and 24hours per day.
Example
The following example illustrates the whole bSLA document for
above agreements:
(57) <?xml version="1.0" encoding="utf-8"?>
(58) <BSLA xmlns="..." xmlns:bqos="..." ... >
(59) <SLAParties>
(60) <ServiceProvider>
(61) <ServiceUri>
(62) http://www.serviceprovider.com/eerp/service</ServiceUri>
(63) <ServiceProviderName
languageID="EN">
(64) EERP Sample
Service</ServiceProviderName>
(65) </ServiceProvider>
(66) <ServiceRequester>
(67) <ServiceRequesterUri>
(68) http://www.servicerequester.com</ServiceRequesterUri>
(69) <ServiceRequesterName
languageID="EN">
(70) EERP Service
Requester</ServiceRequesterName>
(71) </ServiceRequester>
(72) </SLAParties>
(73) <SLAParameters>
(74) <ServiceProfileUri>
(75) http://www.serviceprovider.com/eerp/service/profile2
(76) </ServiceProfileUri>
(77) </SLAParameters>
(78) <SLATerms
xmlns:t="..." >
(79) <SLATerm>
(80) <t:ServcieLocation>
(81) <t:Lat>37.7749295</t:Lat>
(82) <t:Lng>-122.4194155</t:Lng>
(83) </t:ServcieLocation>
(84) </SLATerm>
(85) <SLATerm
t:serviceHours="7x24" >
(86) </SLATerms>
(87) </BSLA>
An implementation conforms to this specification if it
satisfies all of the MUST or REQUIRED level requirements defined within this
specification. A SOAP Node MUST NOT use the XML namespace identifier for this
specification (listed in Section 1.1) within SOAP Envelopes unless it is
compliant with this specification.
This specification references a number of other
specifications (listed in Section 1.4.2). In order to comply with this
specification, an implementation MUST implement the portions of referenced
specifications necessary to comply with the required provisions of this
specification. Additionally, the implementation of the portions of the
referenced specifications that are specifically cited in this specification
MUST comply with the rules for those portions as established in the referenced
specification.
Normative text within this specification takes
precedence over normative outlines (as described in section 1.4.1), which in
turn take precedence over the XML Schema [XML Schema Part 1, Part 2] and WSDL
[WSDL 1.1] descriptions. That is, the normative text in this specification
further constrains the schemas and/or WSDL that are part of this specification;
and this specification contains further constraints on the elements defined in
referenced schemas.
The minimum set of information
exchange for bSLA that would allow conforming applications to exchange
information and satisfy the conformance should at least to have the following
elements:
·
/sla:SLAParties/sla:ServiceProvider/sla:ServiceUri
·
/sla:SLAParties/sla:ServiceProvider/sla:ServiceProviderName
·
/sla:SLAParties/sla:ServiceRequester/sla:ServiceRequesterUri
·
/sla:SLAParties/sla:ServiceRequester/sla:ServiceRequesterName
·
/sla:SLAParameters/sla:ServiceProfileUri
Example of such minimum set of information could like this:
(001) <?xml version="1.0"
encoding="utf-8"?>
(002) <BSLA
xmlns="http://docs.oasis-open.org/ns/soa-eerp/sla/200903" >
(003)
<SLAParties>
(004)
<ServiceProvider>
(005)
<ServiceUri>http://www.sample-eerp.com/myservice</ServiceUri>
(006)
<ServiceProviderName>My Service
Provider</ServiceProviderName>
(007)
</ServiceProvider>
(008)
<ServiceRequester>
(009)
<ServiceRequesterUri>http://www.u-service.com</ServiceRequesterUri>
(010)
<ServiceRequesterName>Your Service
Requester</ServiceRequesterName>
(011)
</ServiceRequester>
(012)
</SLAParties>
(013)
<SLAParameters>
(014)
<ServiceProfileUri>
http://www.sample-eerp.com/myservice/profile</ServiceProfileUri>
(015)
</SLAParameters>
(016)</BSLA>
The following nearly empty artifact does not conform to
this specification:
(001) <?xml version="1.0"
encoding="utf-8"?>
(002) <BSLA xmlns="http://docs.oasis-open.org/ns/soa-eerp/sla/200903"
>
(003)
<SLAParties>
(004)
<ServiceProvider>
(005)
<ServiceUri/>
(006)
<ServiceProviderName/>
(007)
</ServiceProvider>
(008)
<ServiceRequester>
(009)
<ServiceRequesterUri/>
(010) <ServiceRequesterName/>
(011)
</ServiceRequester>
(012)
</SLAParties>
(013)
<SLAParameters>
(014)
<ServiceProfileUri/>
(015)
</SLAParameters>
(016)</BSLA>
This specification defines a number of extensions;
compliant services are NOT REQUIRED to implement those extensions defined in
this specification. However, if a service implements an aspect of the
specification, it MUST comply with the requirements specified (e.g. related
"MUST" statements). If an implementation silently
ignores unrecognized attributes where any attribute is allowed, or silently
ignores unrecognized elements where any element is allowed, should be
considered as an interoperable implementation.
The following individuals have participated in the creation
of this specification and are gratefully acknowledged:
Participants:
Rex Brooks Individual
Szu Chang Changfeng
Open Standards Platform Software Alliance
William Cox Individual
Andy Lee Changfeng
Open Standards Platform Software Alliance
Carl
Mattocks Individual
Yulin Xu Changfeng Open Standards
Platform Software Alliance
Paul Yang Changfeng Open Standards
Platform Software Alliance
James Zhili Zhang TIBCO
Software Inc.
Hong Zhou Changfeng Open Standards
Platform Software Alliance
Note: The separate machine
readable schema document, listed on Section 2.2, is normative. The text included here is
non-normative.
<?xml version="1.0"
encoding="UTF-8"?>
<!--
Document Type: EERP Business SLA Schema CD04
Create On: 09/12/2010
-->
<!-- ===== xsd:schema Element With Namespaces Declarations ===== -->
<!-- ===== Copyright Notice ===== -->
<!--
OASIS
takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the
implementation or use of the technology described in this
document
or the extent to which any license under such rights
might or
might not be available; neither does it represent that it has
made any
effort to identify any such rights. Information on OASIS's
procedures
with respect to rights in OASIS specifications can be
found at
the OASIS website. Copies of claims of rights made
available
for publication and any assurances of licenses to be made
available,
or the result of an attempt made to obtain a general
license or
permission for the use of such proprietary rights by
implementors or users of this specification, can be obtained from
the OASIS
Executive Director.
OASIS
invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights
which may cover technology that may be required to
implement
this specification. Please address the information to the
OASIS
Executive Director.
Copyright
(C) OASIS Open 2008-2010. All Rights Reserved.
This
document and translations of it may be copied and furnished to
others,
and derivative works that comment on or otherwise explain
it or
assist in its implementation may be prepared, copied,
published
and distributed, in whole or in part, without restriction of
any kind,
provided that the above copyright notice and this
paragraph
are included on all such copies and derivative works.
However,
this document itself may not be modified in any way,
such as by
removing the copyright notice or references to OASIS,
except as
needed for the purpose of developing OASIS
specifications, in which case the procedures for copyrights defined
in the
OASIS Intellectual Property Rights document must be
followed,
or as required to translate it into languages other than
English.
The
limited permissions granted above are perpetual and will not be
revoked by
OASIS or its successors or assigns.
This
document and the information contained herein is provided on
an
"AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES,
EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY
THAT THE USE OF THE INFORMATION HEREIN
WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES
OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR
PURPOSE.
-->
<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://docs.oasis-open.org/ns/soa-eerp/sla/200903" xmlns:bqos="http://docs.oasis-open.org/ns/soa-eerp/bqos/200903" xmlns:eerp="http://docs.oasis-open.org/ns/soa-eerp/eerp/200903" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:udt="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sla="http://docs.oasis-open.org/ns/soa-eerp/sla/200903" targetNamespace="http://docs.oasis-open.org/ns/soa-eerp/sla/200903" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
<!-- ===== Imports ===== -->
<xsd:import
namespace="http://docs.oasis-open.org/ns/soa-eerp/bqos/200903" schemaLocation="EERP-bQoS.xsd"/>
<xsd:import
namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" schemaLocation="http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UBL-CommonBasicComponents-2.0.xsd"/>
<xsd:import
namespace="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2" schemaLocation="http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UnqualifiedDataTypeSchemaModule-2.0.xsd"/>
<!-- ===== Root Element ===== -->
<xsd:element
name="BSLA" type="BSLAType">
<xsd:annotation>
<xsd:documentation>The bSLA is the
root element for EERP- Service-level agreement (bSLA). Business SLA is a formal
contract between a service provider and a client guaranteeing quantifiable
business quality of service (bQoS) at defined levels. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- ===== Element Declarations ===== -->
<xsd:element
name="ActionGuarantee" type="ActionGuaranteeType">
<xsd:annotation>
<xsd:documentation>The Action
Guarantee, action guarantee element for bSLA Obligations in EERP-bSLA, is to
specify what happens if the Service Level Objective (SLO) is met or not met,
including Reserve Fee and Penalty element. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="Availabilities" type="AvailabilitiesType">
<xsd:annotation>
<xsd:documentation>The services
availability indicators</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="Availability" type="AvailabilityType">
<xsd:annotation>
<xsd:documentation>Availability is
the quality aspect of whether the service is present or ready for immediate
use.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="CommittedCompletionTime" type="udt:DateTimeType">
<xsd:annotation>
<xsd:documentation>Committed
completion time</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="CommittedCost" type="bqos:PriceType">
<xsd:annotation>
<xsd:documentation>Cost Element in
bSLA</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="CommittedTime" type="CommittedTimeType">
<xsd:annotation>
<xsd:documentation>Committed time
period</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="CommittedThroughput" type="bqos:ThroughputType">
<xsd:annotation>
<xsd:documentation>Committed
performance throughput</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="From" type="xs:dateTime">
<xsd:annotation>
<xsd:documentation>Availability
starting time</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="Obligation" type="ObligationType">
<xsd:annotation>
<xsd:documentation>Agreed bSLA
obligation, including Service Level Objective (SLO) and the Action Guarantee
that associates with that SLO</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="Penalty">
<xsd:annotation>
<xsd:documentation>Penalty element
is the money amount when Service Level Objective (SLO) is not met. </xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension
base="bqos:PriceType">
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element
name="ReserveFee">
<xsd:annotation>
<xsd:documentation>ReserveFee
element is the reservation fee or money amount when Service Level Objective
(SLO) is met. It is an optional element for Action Guarantee. </xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension
base="bqos:PriceType">
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element
name="ServiceLevelObjective" type="ServiceLevelObjectiveType">
<xsd:annotation>
<xsd:documentation>SLO (Service
Level Objective) for QoS guarantee</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="ServiceName" type="ServiceNameType">
<xsd:annotation>
<xsd:documentation>The service name</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="ServiceOperations" type="ServiceOperationsType">
<xsd:annotation>
<xsd:documentation>Describe
available operations and bQoS</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="ServiceProfileUri" type="SlaUriType">
<xsd:annotation>
<xsd:documentation>Service Profile
Uri element represents web page URL or other URI for the service profile that
defines the details of the services. Different service providers will share the
same profile. It is a required element for bSLA Parameters.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="ServiceProvider" type="ServiceProviderType">
<xsd:annotation>
<xsd:documentation>Service Provider
element represents the provider for parties. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="ServiceProviderName" type="ServiceProviderNameType">
<xsd:annotation>
<xsd:documentation>The name of
service provider</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="ServiceRequester" type="ServiceRequesterType">
<xsd:annotation>
<xsd:documentation>ServiceRequester
element represents requester for the service, including requester’s name and
the URI that represents the requester. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="ServiceRequesterUri" type="SlaUriType">
<xsd:annotation>
<xsd:documentation>Service
Requester Identifier in Uri format</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="ServiceRequesterName" type="ServiceRequesterNameType">
<xsd:annotation>
<xsd:documentation>Name of the
service requester</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="ServiceUri" type="SlaUriType">
<xsd:annotation>
<xsd:documentation>Service Identifier
in URI format </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="SLAParties" type="SLAPartiesType">
<xsd:annotation>
<xsd:documentation>SLAParties
element, bSLA Parties aspect of the service, is for parties invoked in the bSLA
for the service, including both service provider and service requester
elements. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="SLATerm" type="SLATermType">
<xsd:annotation>
<xsd:documentation>bSLA Term
element is an any type element to describe additional term for this bSLA. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="SLATerms" type="SLATermsType">
<xsd:annotation>
<xsd:documentation>The bSLA Terms,
Terms element for EERP-bSLA, is the agreed bSLA terms aspect of the service,
including bSLA term elements.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="SLAParameters" type="SLAParametersType">
<xsd:annotation>
<xsd:documentation>The SLAParameters
element for EERP-bSLA describes the parameters of the service used to define
monitoring of bQoS metrics, including the service profile URI, operations and
other optional elements.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SLAObligations" type="SLAObligationsType">
<xsd:annotation>
<xsd:documentation>The
SLAObligations element describes the agreed bSLA obligations of the service,
including obligations and action guarantees.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="To" type="xs:dateTime">
<xsd:annotation>
<xsd:documentation>Availability
ending time</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- Extension -->
<xsd:element
name="BSLAExtension">
<xsd:annotation>
<xsd:documentation>Additional element</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="true">
<xsd:choice
minOccurs="0" maxOccurs="unbounded">
<xsd:any processContents="skip" minOccurs="0" maxOccurs="unbounded"/>
</xsd:choice>
<xsd:attribute name="optional" type="xsd:boolean" use="optional" default="true"/>
</xsd:complexType>
</xsd:element>
<!-- ===== Type Definitions ===== -->
<xsd:complexType name="ActionGuaranteeType">
<xsd:annotation>
<xsd:documentation>Complex type for
action guarantee</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="ReserveFee" minOccurs="0">
<xsd:annotation>
<xsd:documentation>ReserveFee
element is the reservation fee or money amount when Service Level Objective
(SLO) is met. It is an optional element for Action Guarantee. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="Penalty" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Penalty element
is the money amount when Service Level Objective (SLO) is not met. It is a
required element for Action Guarantee.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="AvailabilitiesType">
<xsd:annotation>
<xsd:documentation>Complex type for
Availabilities of multiple Availability elements</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Availability" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="AvailabilityType">
<xsd:annotation>
<xsd:documentation>Complex type for
the service is available or not available for a given From time To time. The
default is available when the isAvailable element is missing or set to true.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="From">
<xsd:annotation>
<xsd:documentation>Availability
starting time</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="To">
<xsd:annotation>
<xsd:documentation>Availability
ending time</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute
name="isAvailable" type="xs:boolean" use="optional" default="true"/>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="CommittedTimeType">
<xsd:annotation>
<xsd:documentation>Complex type for
committed completion time</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension
base="bqos:TimePeriodType">
<xsd:sequence>
<xsd:element ref="CommittedCompletionTime" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ObligationType">
<xsd:annotation>
<xsd:documentation>Complex type for
obligation</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="ServiceLevelObjective"/>
<xsd:element ref="ActionGuarantee" minOccurs="0"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="ProviderIDType">
<xsd:annotation>
<xsd:documentation>Complex type for
provider ID </xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension
base="cbc:IDType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="ServiceLevelObjectiveType">
<xsd:annotation>
<xsd:documentation>Complex type for
SLO</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="CommittedCost" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Committed cost
element in bSLA</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="CommittedTime" minOccurs="0"/>
<xsd:element ref="Availabilities" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Whether the
service is
present or ready for immediate use</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="CommittedThroughput" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Committed
performance throughput</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="SLATerm" minOccurs="0"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="ServiceNameType">
<xsd:annotation>
<xsd:documentation>Complex type for
the name of the service</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension
base="cbc:NameType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="ServiceOperationsType">
<xsd:annotation>
<xsd:documentation>Complex type for
service operations</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element
name="hasCommittedCost" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>has committed
cost or not</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="hasCommittedTime" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>has committed
time or not</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="hasAvailabilities" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>has availabilities or not</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="hasCommittedThroughput" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>has committed
throughput or not</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element
name="hasOtherTerms" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>has other SLA
terms or not</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="SlaUriType">
<xsd:annotation>
<xsd:documentation>Complex type for
the service URI or service profile URI</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension
base="xsd:anyURI">
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="ServiceProviderType">
<xsd:annotation>
<xsd:documentation>Complex type for
the service provider</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="ServiceUri"/>
<xsd:element ref="ServiceProviderName"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="ServiceProviderNameType">
<xsd:annotation>
<xsd:documentation>Complex type for
the service provider name</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension
base="cbc:NameType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="ServiceRequesterType">
<xsd:annotation>
<xsd:documentation>Complex type for
the service requester</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="ServiceRequesterUri">
<xsd:annotation>
<xsd:documentation>Service
Requester Identifier in URI format</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="ServiceRequesterName"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="ServiceRequesterUriType">
<xsd:annotation>
<xsd:documentation>Complex type for
the service requester ID</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension
base="cbc:IDType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="ServiceRequesterNameType">
<xsd:annotation>
<xsd:documentation>Complex type for
the service request name</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension
base="cbc:NameType"/>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="SLAObligationsType">
<xsd:annotation>
<xsd:documentation>Complex type for
bSLA Obligations</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Obligation" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>The Obligation,
obligation element for bSLA Obligations in EERP-bSLA, is the agreed bSLA
obligation, including Service Level Objective (SLO) and the Action Guarantee
that associates with that SLO.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="ActionGuarantee" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The Action
Guarantee, action guarantee element for bSLA Obligations in EERP-bSLA, is to
specify what happens if the Service Level Objective (SLO) is met or not met,
including Reserve Fee and Penalty element.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="SLAParametersType">
<xsd:annotation>
<xsd:documentation>Complex type for
bSLA parameters </xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="ServiceProfileUri">
<xsd:annotation>
<xsd:documentation>Service Profile
Uri element represents web page URL or other URI for the service profile that
defines the details of the services. Different service providers will share the
same profile. It is a required element for bSLA Parameters.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="ServiceOperations" minOccurs="0"/>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="SLAPartiesType">
<xsd:annotation>
<xsd:documentation>Complex type for
bSLA parties</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="ServiceProvider">
<xsd:annotation>
<xsd:documentation>Service Provider
element represents the provider for parties.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="ServiceRequester">
<xsd:annotation>
<xsd:documentation>ServiceRequester
element represents requester for the service, including requester’s name and
the URI that represents the requester. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="SLATermType">
<xsd:annotation>
<xsd:documentation>Complex type for
one bSLA term</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:any namespace="##any" processContents="skip" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
The definition of the bSLA Terms
</xsd:documentation>
</xsd:annotation>
</xsd:any>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="SLATermsType">
<xsd:annotation>
<xsd:documentation>Complex type for
bSLA Terms </xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="SLATerm" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:complexType name="BSLAType">
<xsd:annotation>
<xsd:documentation>Complex type for
bSLA which is a formal contract between a service provider and a client
guaranteeing quantifiable business quality of service (bQoS) at defined levels.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="SLAParties">
<xsd:annotation>
<xsd:documentation>SLAParties
element, bSLA Parties aspect of the service, is for parties invoked in the bSLA
for the service, including both service provider and service requester
elements. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="SLAParameters">
<xsd:annotation>
<xsd:documentation>The
SLAParameters element for EERP-bSLA describes the parameters of the service
used to define monitoring of bQoS metrics, including the service profile URI,
operations and other optional elements.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="SLAObligations" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The
SLAObligations element describes the agreed bSLA obligations of the service,
including obligations and action guarantees.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="SLATerms" minOccurs="0">
<xsd:annotation>
<xsd:documentation>The bSLA Terms,
Terms element for EERP-bSLA, is the agreed bSLA terms aspect of the service,
including bSLA term elements.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="BSLAExtension" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
</xsd:schema>
None
|
Revision
|
Date
|
Editor
|
Changes Made
|
|
0.9
|
03/10/2009
|
Szu Chang
|
Initial draft
|
|
WD01
|
04/24/2009
|
Szu Chang
|
Renamed draft 0.9 to working
draft 01
|
|
WD02
|
05/12/2009
|
Szu Chang
|
Fixed issue # I011, I012,
and I014
|
|
WD03
|
05/17/2009
|
Szu Chang
|
Added conformance
section
|
|
WD04
|
06/08/2009
|
Szu Chang
|
Fixed issue # I017, I018, and I020
|
|
WD05
|
06/24/2009
|
Szu Chang
|
Fixed issue # I028, I031, and I038, I041, I047, and I056
|
|
WD06
|
07/05/2009
|
Szu Chang
|
Fixed issue # I028, I035, I038, I043, I051, and I055
|
|
CD02
|
07/11/2009
|
Szu Chang
|
Changed WD06 to CD02 after
approved by TC
|
|
CD03
|
01/06/2010
|
Szu Chang
|
Changed NS and fixed URIs
from CD02 to CD03
|
|
WD08
|
05/10/2010
|
Szu Chang
|
Changed after the public
review comments
|
|
WD09
|
06/23/2010
|
Szu Chang
|
Changed after the first
round of review PR comments
|
|
CD04
|
09/12/2010
|
Szu Chang
|
TC approved, changed from
WS09 to CD04
|
