[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [soa-eerp] Response to Issue 1005
I agreed with Andy’s assessment that all units in bQoS are
required
and shouldn’t 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. 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. Andy
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]