[RUS-WG] tracker updates

[Xiaoyu Chen]

Hello, everyone:

It's great to get your comments finally. I got some problems when composing OGF-RUS specification version 1.9. There are some points:

1). Rosario said, we should concentrate on some changes agreed based on version 1.7 with agreed comments, such as removing RUS-UR wrapper. But the 
main difference for version 1.9 is targeted removing RUS-UR. Do you mean leaving the RUS operations as what they are? If it is the case, then i will 
update the version 1.7. 

2). Regarding RUS operations, the reason i got stucked somehow is an important signal from stakeholders about query operation. 
"The RUS specificaiton is hard to be conformed only if the query operations providing reliable extraction of usage records based on following contexts
:
first of all, as a specification, it should gives implementation guides to solve potential problems and makes reliable recommendataions. Which means, 
the specification should protect the RUS server from being crashed when returning large amount of data."
We agree to propose a "RUSTooComplexFault". However this never really solves returning huge-data to the client. Some implementation strongly requires 
a "steam" type return for stateful connection to the database. They request the complex queries always return what user asked even taking longer time.
 However, this would not work through Web service, which is stateless essentially and will throw session out error if taking too long time to get SOAP
 response message back. 

So i reviewed OSGA-DAI, WS-DAI, WS-Enumeration, WS-Context and other relevant specification and implementations. There is still no satisfiable 
solutions for this issue from the perspective of service interface definitions. OSGA-DAI provides an implementation-specific service interface, which 
is more or less like the operation defined in the WS-Enumeration specification:

GetFully Operation
Inputs: 
The name of a session known to a data service resource. 
The name of an open output stream known to the session. 
The session name and stream name are expected to be conjoined with a colon (:). 
Outputs: 
Data - a string, a chunk of valid XML or a byte array. 

GetNBlocks Operation
Inputs: 
The name of a session known to a data service resource. 
The name of an open output stream known to the session. 
The session name and stream name are expected to be conjoined with a colon (:). 
The number of blocks of data to be retrieved. 
Outputs: 
A block of data - a string, a chunk of valid XML or a byte array. 

Gilbert proposed the WS-Enumeration, and define a new operation for returning "wsen:EnumreationContext" type. That could be a solution. However, how 
to integrate the WS-Enumeration datatype and operations into RUS operations is another issue. 
* import WS-Enumeration WSDL within the RUS WSDL?
* define a new context data type for enumeration context within the RUS WSDL?
 
 
School of Engineering and Design
Mobile: Mobile: ++44(0)7871876894
X. Chen