http://docs.oasis-open.org/soa-eerp/issues/
SOA-EERP TC Issues List
Date: 2009/6/10
Revision: 8
spec
schema
example
all
interop
New
Active
Pending
Review
Deferred
Closed
Dropped
Should a complete bQoS example be included on the bQoS spec?
This issue was raised during the TC meeting on 4/15/2009. There are small
examples in sections for EERPPrice, EERPPerformance and EERPQuality, but
does not have an example for whole BQoS in the WD01. The whole bQoS example
can be found on the EERP Use Case and Example document.
EERP-bQoS
spec
editorial
Szu Chang
Szu Chang
spec example
New version of bQoS, Working draft 02, has been uploaded at http://www.oasis-open.org/committees/download.php/32306/BusinessQualityOfService-v1.0-spec-wd02.doc and it has the whole example for bQoS on new session 6.
Status changed to Closed on April 29th TC call.
Other quality indicators for bQoS
This issue was raised during the TC meeting on 4/15/2009 by James Zhang.
The current bQoS only has elements Price, time/Performance and name-value
pairs for Quality. Should other web services or software type of QoS
indicators be included for the bQoS spec, such as security, reliability,
etc.?
EERP-bQoS
spec
design
Szu Chang
Szu Chang
N/A
This issue is addressed on WD03 at
http://www.oasis-open.org/committees/download.php/32450/BusinessQualityOfService-v1.0-spec-wd03.doc
Line 146 to Line 152.
Propose to close the issue with above spec changes.
Status changed to "CLOSE pending verification of changes" on May 13th TC call.
Status changed to "CLOSED" on May 27th TC call.
How to reference/use the Unit and Currency code
This issue was raised during the TC meeting on 4/15/2009 by Bill Cox and
Carl. In Use case and example, page 6, embedded - unitCode=each, for
example.
Bill: UnitCode from UBL. Currency code from there as well. Same as (or
derived from) UN-CEFACT. Concerned about pulling in too much of UBL for
just currency code and units. Also as much as the reference is interesting,
easier to resolve to the value "ea" for readability. End resolution is
easier to understand. Agree that supplying a URN is a valuable definition,
but simpler when one reads it to see the end result which would be "ea".
Carl: Same thing, but one is simpler and easier to read than the other.
Need to agree on what put in.
EERP-bQoS
spec
design
Szu Chang
Szu Chang
N/A
In bQoS schema, there are many cases use UBL CommonBasicComponents (CBC)
element or UnqualifiedDataTypesSchemaModule (UDT) now.
This include:
<xsd:element name="Amount" type="cbc:AmountType">
<xsd:element name="Duration" type="cbc:DurationMeasureType">
<xsd:element name="Latency" type="cbc:DurationMeasureType">
<xsd:element name="Quantity" type="cbc:BaseQuantityType">
<xsd:element name="Unit" type="cbc:BaseUnitMeasureType">
<xsd:complexType name="PropertyNameType">
<xsd:complexType name="PropertyValueType">
<xsd:element name="StartTime" type="udt:DateTimeType">
Other two schema files also reference many elements from UBL.
In other words, including UBL is NOT for just currency code and units.
In the feature schema design, more UBL elements will be referenced. This
will leverage the existing components and development on UBL, and reduce
the complexity of our EERP schema.
It is proposed not to change this UBL references.
On May 13th TC call:
Bill: propose to close, open a new item on UBL inclusion in
general.
Per TC meeting notes on 5/13/2009, this issue is closed, and new issue is
open for UBL inclusion in general at #i016
i004
i016
Name Space Names Not Intuitive
This issue was raised during the TC meeting on 4/15/2009 by Bill Cox. In
bQoS schema, it uses namespace like clm66411 and clm54217 which are not
intuitive.
EERP-bQoS
spec
editorial
Szu Chang
Szu Chang
N/A
The name space names, such as clm66411 and clm54217, are come from UBL
2.0's CBC schema:
<xsd:import
namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponent
s-2"
schemaLocation="http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/common/UBL-Com
monBasicComponents-2.0.xsd"/>
This cannot be changed, unless we drop the CommonBasicComponents schema and
write our own schema for currency code and language code, which should be
addressed on Issue # I003.
Propose to close this issue with no action.
Issue 4 is similar to I003.
On May 13th TC call: Issue I004 will leave it open for now.
Status changed to "CLOSED" on May 27th TC call.
i003
Too many units in bQoS schema
This issue was raised during the TC meeting on 4/15/2009 by Bill Cox. In bQoS schema, it has too many units, perhaps, could use simpler model? Or IETF iCalendar (used in Buildings, Energy)?
EERP-bQoS
spec
design
Szu Chang
Bill Cox
N/A
Units used in bQoS schema include the following:
- Unit for Unit of Measurement in Unit element
- Unit in Time Period, such as Duration and Latency
- Unit in Quantity
All those unit are required to describe the amount, time and quantity to
me.
It is proposed:
1. To assign this issue to Bill Cox for coming up an alternative proposal.
Or
2. Close with no action.
Reassign to Bill Cox.
Still open. Bill will respond before next meeting.
Andy:I have reviewed the examples provided in the bQoS Spec. From those
examples, I think all units in the bQoS schema are useful, and we
should keep all units in the schema.
Hong:I agreed with Andy assessment that all units in bQoS are required
and should not be simplified. Looking into the example in Line 393 and
on:
393 (01) <?xml version="1.0" encoding="UTF-8"?>
394 (02) <bqos:BQoS xmlns:bqos="..." ... >
395 (03) <bqos:BQoSPrice>
396 (04) <bqos:Price>
397 (05) <bqos:Unit unitCode="EA">1000</bqos:Unit>
398 (06) <!-- CNY: Chinese Yuan -->
399 (07) <bqos:Amount currencyID="CNY">120000</bqos:Amount>
400 (08) </bqos:Price>
401 (09) </bqos:BQoSPrice>
402 (10) <bqos:BQoSPerformance>
403 (11) <bqos:Throughput>
404 (12) <!-- delivery: 1 week -->
405 (13) <bqos:Duration unitCode="DAY">7</bqos:Duration>
406 (14) <!-- batch production, generally 1000 sets a batch -->
407 (15) <bqos:Quantity>1000</bqos:Quantity>
408 (16) <bqos:Latency unitCode="DAY">0</bqos:Latency>
409 (17) </bqos:Throughput>
410 (18) </bqos:BQoSPerformance>
411 (19) <bqos:BQoSQualities>
. . .
426 (32) </bqos:BQoSQualities>
427 (33) </bqos:BQoS>
The unitCode on Price, Duration and Latency are all required for
describing Price and Time.
Propose to close this issue with no action.
Further review of bQoS schema
This issue was raised during the TC meeting on 4/29/2009. Need to further
review of bQoS schema. Also, need to ensure that EVERY element is fully
defined in the document. It is essential before public review.
The schema needs to be placed on the Specifications / bqos folder.
EERP-bQoS
schema
design
Szu Chang
Szu Chang
N/A
EERP-bQoS schema has posted on
http://www.oasis-open.org/committees/download.php/32422/EERP-bQoS-wd01.xsd
for review.
Proposed to change to action item and close the issue.
Status changed to Closed on May 13th TC call.
Change Rate to Rating
This issue was raised during the spec review at the TC meeting on
4/29/2009. Carl Mattocks suggested that RATE is not same meaning as
RATING.
All references of "Rate" in the spec and schema should be changed to
"Rating". For example, ListOfRate should be changed to ListOfRating.
EERP-Rating
schema
editorial
Szu Chang
Szu Chang
N/A
Spec Working Draft 02 uploaded at
http://www.oasis-open.org/committees/download.php/32470/BusinessRating-v1.0-
spec-wd02.doc and the XML Schema for Working Draft 02 uploaded at
http://www.oasis-open.org/committees/download.php/32471/EERP-Rating-WD02.xsd
have changed all "Rate" to "Rating". This includes the syntax, description,
examples and xml schema.
This issue can be closed
Status changed to Closed on May 13th TC call.
Some editorial comments on draft Rating spec
This issue was raised during the spec review at the TC meeting on
4/29/2009. Carl Mattocks suggested that may be mitigated by stating STATUS
and intended USE of (draft) document in beginning.
Carl Mattocks also commented that the CONFORMANCE section in the WD01
looks bad, but a CONFORMANCE section must be in the document , certainly before
published outside of TC
EERP-Rating
spec
editorial
Szu Chang
Szu Chang
N/A
Insert the following text to all three spec per Rex Brooks:
"This document is a Work in Progress only and has not been extensively
reviewed. Comment on this document is encouraged. This document is one of
three closely related specifications, SOA-EERP Business Quality of Service
(bQoS), SOA-EERP Rating and SOA-EERP Service Level Agreement which need
to be understood in combination as a set."
Szu Chang proposed to remove the Conformance section for now. The section
can be added before public review.
Working Draft 02, uploaded at
http://www.oasis-open.org/committees/download.php/32470/BusinessRating-v1.0-
spec-wd02.doc, has the following changes:
Insert the proposed text per Rex Brooks on Page 1, Related work and Page 2
status.
The Conformance section has been removed.
This issue can be closed.
On May 13th TC call:
change OK, except conformance section must be
there. Leave open.
Issue 008, Conformance section should not been removed.
Working Draft 03, uploaded at
http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/32571/BusinessRating-v1.0-spec-wd03.pdf, has the following changes:
The Conformance section has been inserted.
This issue can be closed.
Status changed to "CLOSED" on May 27th TC call.
i013
i014
Put a complete example into the Rating spec
This issue was raised during the spec review at the TC meeting on
4/29/2009 by Szu Chang. Like the bQoS spec, a complete example of Rating message
example should be included in the Rating spec.
EERP-Rating
spec
editorial
Szu Chang
Szu Chang
Examples
Spec Working Draft 02 uploaded at
http://www.oasis-open.org/committees/download.php/32470/BusinessRating-v1.0-
spec-wd02.doc has inserted two complete examples from Line 430 to 553.
This issue can be closed.
Status changed to Closed on May 13th TC call.
Relationship between ListOfRating and Credentials Elements
This issue was raised during the spec review at the TC meeting on
4/29/2009.
Carl Mattocks agreed schema elements is an issue and suggested that it may
help differentiate between CREDENTIAL and RATING.
James Zhang noted that: By looking at the rating schema, it appears that
the two elements "rating" and "credential" are related. However a chat
with
Szu indicates that they are not related at all. It seems to be very
confused to put them into one schema if they are not related. A suggestion
is to explicitly mention them that they are not related somewhere in the
spec. Another suggestion is to separate them into two schemas
Carl Mattocks suggested that it would be useful to have individual
examples
and collective example showing credential and rating.
EERP-Rating
schema
design
Szu Chang
Szu Chang
N/A
Update of EERP-Rating schema has posted on
http://www.oasis-open.org/committees/download.php/32471/EERP-Rating-WD02.xsd
for further review on this issue, see
http://lists.oasis-open.org/archives/soa-eerp/200905/msg00032.html
On May 13th TC call:
James: annotation in the schema, or
write something on the spec.
I010 James propose to add some annotation and spec to
indicate they are not related.
Working Draft 03, uploaded at
http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/32571/BusinessRating-v1.0-spec-wd03.pdf, Section 2, line 101 to line 119 has detailed write-up for
the relationship between ListOfRating and Credentials elements.
XML Schema has uploaded at
http://www.oasis-open.org/committees/download.php/32575/EERP-Rating-WD03.xsd
, it added annotations to the relationship between ListOfRating and Credentials elements.
This issue can be closed.
Status changed to "CLOSED" on May 27th TC call.
Zero Obligations in SLA
This issue was raised during the SLA spec review at the TC meeting on
4/29/2009.
Carl Mattocks quested on meaning of zero Obligations in SLA
Andy Lee explained that in China there is case for zero SLA Obligations
Carl Mattocks suggested to explain USE CASE for this combination.
EERP-SLA
spec
editorial
Szu Chang
Szu Chang
N/A
Rex Brooks proposed Note: SLAObligations allows for a 0 number of
SLAObligations for conformance to business rules of China.
Carl Mattocks agreed to have explanation to avoid confusion.
New working draft (WD02) has uploaded at
http://www.oasis-open.org/committees/download.php/32560/BusinessServiceLevelAgreement-v1.0-spec-wd02.pdf with the following changes:
1. A note is added on line 315 to 316 to explain that there is case for
zero SLA Obligations.
2. An example of SLA without obligation is added on section 7.2, line 773
to 820.
New version of EERP-SLA schema has posted on
http://www.oasis-open.org/committees/download.php/32500/EERP-SLA-WD02.xsd
It is proposed to close this issue with above changes in place.
On May 13th TC call:
Issue #i011: It was a typo on spec. The old schema has one obligation;also something else. Since there are use cases in China that has zero obligation, both spec and schema have been changed.
Remain open due to the URL in this issues.xml points to wrong place. Szu to update correct URLs.including for the schema, and the issue can be closed.
CLOSE AFTER INSERTION OF CORRECT LINK TO PDF.
Status changed to "CLOSED" on May 27th TC call.
i012
Typo on Line 136, missing "?"
This issue was raised during the SLA spec review at the TC meeting on
4/29/2009.
Line 136 has a typo should be fixed and "?" should be added to the end
James Zhang noted that <SLAObligations> can have zero value as described
in section "SLAObligations". However in schema (line 136), it doesn't
indicate it is optional. We need to fix the schema for this.
EERP-SLA
spec
editorial
Szu Chang
Szu Chang
N/A
New working draft (WD02) has uploaded at
http://www.oasis-open.org/committees/download.php/32560/BusinessServiceLevelAgreement-v1.0-spec-wd02.pdf with the following changes:
The spec has changed on line 124 for:
<la:SLAObligations ...>sla:SLAObligationsType</sla:SLAObligations> ?
Line 147 to 148 for opetional element.
New version of EERP-SLA schema has posted on
http://www.oasis-open.org/committees/download.php/32500/EERP-SLA-WD02.xsd
The schema has changed SLAObligations element from 1 to 0 or 1
It is proposed to close this issue with above changes in place.
On May 13th TC call:
OPEN with the same reason as issue i011: due to the URL in this issues.xml points to wrong place. Szu to update correct URLs.including for the schema, and the issue can be closed.
CLOSE AFTER INSERTION OF CORRECT LINK TO PDF.
Status changed to "CLOSED" on May 27th TC call.
i011
Some editorial comments on draft bQoS spec
Issue #I008 on Some editorial comments on draft Rating spec also apply to
bQoS spec.
Open a new issue for tracking.
EERP-bQoS
spec
editorial
Szu Chang
Szu Chang
N/A
Insert the following text to all three spec per Rex Brooks:
"This document is a Work in Progress only and has not been extensively
reviewed. Comment on this document is encouraged. This document is one of
three closely related specifications, SOA-EERP Business Quality of Service
(bQoS), SOA-EERP Rating and SOA-EERP Service Level Agreement which need to
be understood in combination as a set."
Szu Chang proposed to remove the Conformance section for now. The section
can be added before public review.
Working draft WD03 at
http://www.oasis-open.org/committees/download.php/32450/BusinessQualityOfService-v1.0-spec-wd03.doc
has changed.
Related work on Page 1 and Status on page 2 has inserted the text per Rex
Brooks's sugguestion. The Conformance section has been removed.
Working draft WD03 at
http://www.oasis-open.org/committees/download.php/32450/BusinessQualityOfService-v1.0-spec-wd03.doc
has changed.
Related work on Page 1 and Status on page 2 has inserted the text per Rex
Brooks's sugguestion.
The Conformance section has been removed.
This issue can be closed.
On May 13th TC call:
ok, but conformance section reinserted.
Working Draft 04, uploaded at
http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/32576/BusinessQualityOfService-v1.0-spec-wd04.pdf, has the following changes:
The Conformance section has been inserted.
This issue can be closed.
Status changed to "CLOSED" on May 27th TC call.
i008
i014
Some editorial comments on draft SLA spec
Issue #I008 on Some editorial comments on draft Rating spec also apply to
bSLA spec.
Open a new issue for tracking.
EERP-SLA
spec
editorial
Szu Chang
Szu Chang
N/A
Insert the following text to all three spec per Rex Brooks:
"This document is a Work in Progress only and has not been extensively
reviewed. Comment on this document is encouraged. This document is one of
three closely related specifications, SOA-EERP Business Quality of Service
(bQoS), SOA-EERP Rating and SOA-EERP Service Level Agreement which need to
be understood in combination as a set."
Szu Chang proposed to remove the Conformance section for now. The section
can be added before public review.
Working draft WD02 at
http://www.oasis-open.org/committees/download.php/32560/BusinessServiceLevelAgreement-v1.0-spec-wd02.pdf
has changed.
Related work on Page 1 and Status on page 2 has inserted the text per Rex
Brooks's sugguestion.
The Conformance section has been removed.
This issue can be closed.
On May 13th TC call:
is the same (to i013), applied to a different document. Same
resolution: reinsert conformance section.
Working Draft 03, uploaded at
http://www.oasis-open.org/committees/download.php/32573/BusinessServiceLevelAgreement-v1.0-spec-wd03.pdf, has the following changes:
The Conformance section has been inserted.
This issue can be closed.
Status changed to "CLOSED" on May 27th TC call.
i008
i013
Repeated Text in the SLA obligation section
This issue was raised during the SLA spec review at the TC meeting on
5/13/2009 by
Carl Mattocks: in SBLA CD01, the SLA obligation section at 449-484 seems
to be repeated, in 490-517
Open a new issue for tracking.
EERP-SLA
spec
editorial
Szu Chang
Szu Chang
N/A
Line 449 is refer to CommittedCost, Like this:
447
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCo
st/bqos:Unit
448 Number of unit is a optional element that includes a attribute of unit
of measurement uses
449 cbc:BaseUnitMeasureType. See /bqos:BQoSPrice/bqos:Price/bqos:Unit in
Section 3: BQoS
450 Price in EERP-bQoS Specification for more details.
451
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedCo
st/bqos:Amount
452 Amount element is a required element for the Committed Cost element. It
uses cbc:AmountType
453 from UBL that has a required currencyID attribute for currency code. See
454 /bqos:BQoSPrice/bqos:Price/bqos:Amount in Section 3: BQoS Price in
EERP-bQoS
455 Specification for more details.
Line 490 is refer to CommittedTime, like this:
490
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTi
me/bqos:StartTime
491 StartTime is an optional element for the date and time to start the
service. It uses
492 udt:DateTimeType which is in Zulu time format. See
493 /bqos:BQoSPerformance/bqos:TimePeriod/bqos:StartTime in Section 4: BQoS
Performance in
494 EERP-bQoS Specification for more details.
495
/sla:SLAObligations/sla:Obligation/sla:ServiceLevelObjective/sla:CommittedTi
me/sla:CommittedCompleti
496 onTime
497 CommittedCompletionTime is an optional element for the date and time
for committed completion
498 time. It uses udt:DateTimeType which is in Zulu time format.
There are no repeated text found.
Propose to close the issue with no action.
Status changed to "CLOSED" with no action on May 27th TC call.
Including UBL Components in bQoS Schema
This issue was raised during the TC meeting on 5/13/2009. The issue is
should we poll into UBL or not?
Bill Cox: Concern is too much of UBL, which is huge. Don't understand
comment on URN. Bill proposed to close Issue I003, and open a new item on
UBL inclusion in general.
Issue I004 is similar.
.
EERP-bQoS
spec
design
Szu Chang
Szu Chang
N/A
Bill Cox: Will go from new to active when there's some comment/work done on it. Bill's concern is including large schemas (e.g. UBL) which may be a burden to processing on small devices.
Bill Cox: Proposal: Close. Rememeber we'll review the overall schema and quality characteristics at the next stage for the documents.
Status changed to "CLOSED" on May 27th TC call with the condition of review overall schema design at Action #A09-05-13-1.
i003
i004
SLAType missing anyAttribute
This issue was raised during by Zhili Zhang on 6/05/2009 per e-mail at
http://lists.oasis-open.org/archives/soa-eerp/200906/msg00003.html:
BQoSType and EERPRatingType have attribute "anyAttribute", but not
SLAType. Any reason?
EERP-SLA
schema
editorial
Zhili (James) Zhang
Szu Chang
N/A
"anyAttribute" has been added onto BSLAType.
The new SLA spec WD04 has uploaded at
http://www.oasis-open.org/committees/download.php/32837/BusinessServiceLevelAgreement-v1.0-spec-wd04.pdf.
Line 158 - 160 has the changes.
The new schema EERP-SLA-WD04.xsd has uploaded at
http://www.oasis-open.org/committees/download.php/32839/EERP-SLA-WD04.xsd
This issue can be closed.
EERPRatingType should be RatingType
This issue was raised during by Zhili Zhang on 6/05/2009 per e-mail at
http://lists.oasis-open.org/archives/soa-eerp/200906/msg00003.html:
EERPRatingType has a prefix "EERP", but not the rest. I suggest removing the prefix "EERP" to make it consistent with others
.
EERP-Rating
schema
editorial
Zhili (James) Zhang
Szu Chang
N/A
EERPRatingType cannot be renamed to RatingType, as RatingType is already
used for children of the ListOfRating element. EERPRatingType has been
renamed to BusinessRatingType instead.
The new Rating spec WD04 has uploaded at
http://www.oasis-open.org/committees/download.php/32835/BusinessRating-v1.0-spec-wd04.pdf
The new schema EERP-Rating-WD04.xsd has uploaded at
http://www.oasis-open.org/committees/download.php/32840/EERP-Rating-WD04.xsd
In addition, to make the naming consistence, the EERPSLA, the root element
of BSLA, has also be renamed to BSLA, and EERPSLAType be renamed to
BSLAType.
The new SLA spec WD04 has uploaded at
http://www.oasis-open.org/committees/download.php/32837/BusinessServiceLevelAgreement-v1.0-spec-wd04.pdf
The new schema EERP-SLA-WD04.xsd has uploaded at
http://www.oasis-open.org/committees/download.php/32839/EERP-SLA-WD04.xsd
This issue can be closed.
Namespace for CD02
This issue was raised during by Zhili Zhang on 6/05/2009 per e-mail at
http://lists.oasis-open.org/archives/soa-eerp/200906/msg00003.html:
Declared namespace string has date "200903". Will it be changed to the month whenever the specs become CD? Also the schema locations are currently not accessible. For example http://docs.oasis-open.org/soa-eerp/eerp-bqos/200903/eerp-bqos.xsd. Will the links be accessible when publishing the CD?
.
EERP-bQoS
spec
editorial
Zhili (James) Zhang
Szu Chang
N/A
It is proposed to have the TC to make decision for where the current
namespace of 200903 should be changed or not for CD02.
Most other TCs use submit date in their namespace, instead of the final spec
publish date for their namespace.
Typo on SLA Namespace
This issue was raised during by Zhili Zhang on 6/05/2009 per e-mail at
http://lists.oasis-open.org/archives/soa-eerp/200906/msg00003.html:
Line 8 of spec http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/32573/BusinessServiceLevelAgreement-v1.0-spec-wd03.pdf, namespace string has a typo. It refers to namespace of ".../rt/...". The correct namespace should be ".../sla/...".
.
EERP-SLA
schema
editorial
Zhili (James) Zhang
Szu Chang
N/A
The namespace typo on line 8 has been fixed. The new SLA spec WD04 has
uploaded at
http://www.oasis-open.org/committees/download.php/32837/BusinessServiceLevelAgreement-v1.0-spec-wd04.pdf
This issue can be closed.
Update "Document Type" and "Created On" on xsd
This issue was raised during by Zhili Zhang on 6/05/2009 per e-mail at
http://lists.oasis-open.org/archives/soa-eerp/200906/msg00003.html:
"Document Type" and "Created On" (first few commented lines in EERP-bQoS-wd02.xsd) are not updated
.
EERP-bQoS
schema
editorial
Zhili (James) Zhang
Szu Chang
N/A
The Document Type has changed to "EERP-bQoS Working Draft 04 (WD04)" and
Created On has changed to "06/08/2009" on the new schema
EERP-bQoS-WD04.xsd. It has been uploaded at
http://www.oasis-open.org/committees/download.php/32838/EERP-bQoS-WD04.xsd
There are no spec changes on this issue. The issue can be closed.
TC to review XML Schema for all three standards
This action item is from issue #i006. The following are latest schema locations:
http://www.oasis-open.org/committees/download.php/32422/EERP-bQoS-wd01.xsd
http://www.oasis-open.org/committees/download.php/32575/EERP-Rating-WD03.xsd
http://www.oasis-open.org/committees/download.php/32500/EERP-SLA-WD02.xsd
New pictures for the schema can be found at the following locations:
.
http://www.oasis-open.org/committees/download.php/32676/EERP-bQoS-WD01.png
http://www.oasis-open.org/committees/download.php/32677/EERP-Rating-WD03.png
http://www.oasis-open.org/committees/download.php/32678/EERP-SLA-WD02.png
.
SOA-EERP TC