Comments on 0.5 Draft

["Martin Chapman" <martin.chapman@oracle.com>]

1. Section 2.3, Figure 1 and paragraph following:

To be consistent with ws-rm, the reference-scheme attribute should be optional, not required.

2. section 3 after figure 4, 4th bullet.
Currently reads:

	An OPTIONAL service to get data associated with a context-identifier that resolves to a
	reference to a Context Manager Web service.

Should this be
	An OPTIONAL service reference
?

3. section 3.1 3rd para.

Currently reads:

	A context is associated with one and only one activity; "compound" activity contexts do not
	exist.

Even though nesting in mention 2 paras after, should we state here that nested activities are ok? e.g 

 	A context is associated with one and only one activity; "compound" activity contexts do not
	exist, although nested activities are permitted.

(the problem here is that nesting is a vlid compounding mechanism, and it’s the others that are not allowed)

4. general: always use the terminology "referencing specifications" as opposed to specifications using ws-context (for e.g.)  I have an action to beef up 1.2 to make it clear that applications can be refernecinf specs c.f. the shopping cart.


_________________________________________________________________
Martin Chapman                                 
Consulting Member of Technical Staff           
Oracle                                        
P: +353 87 687 6654                           
e: martin.chapman@oracle.com