[rus-wg] Next iteration (v11) of RUS specification
Steven Newhouse
sjn5 at doc.ic.ac.uk
Sat Jul 23 14:40:58 CDT 2005
Next change tracked revision attached.
Major Change Log:
1. Added 'new' GGF copyright and IP statement at the end of the main
text. Deleted the previous text at start.
2. Deleted second half of section 3.1.1. I think some role definition
text needs to stay there. We define a model, we don't specify how it is
implemented.
3. Section 3.2. Mandatory Usage Record elements. I belive the RUS needs
to define a mandatory set of UR elements. However we provide no
mechanism as to how a client can obtain this information so specifying
how it is held is currently redundant.
*** ISSUE: So... cut 3.2 or add in an operation to provide the information?
3. Conversion of all RUSIds & RecordIds etc to RUSRecordIds
4. Conversion of several 'List of RUSIds' to RUSRecordIdList types
5. Altering operation names to match returned types, i.e. extractRUSIds
to extractRUSRecordIds
6. Sections 5.6.1 & 5.6.2: The RUSResult element is not defined not sure
what this is!
*** ISSUE: What is a RUSResult? [John Ainsworth?]
7. Conversion of a 'List of RUSRecordIds' to 'RUSRecordIdList' types.
--
----------------------------------------------------------------
Dr Steven Newhouse Tel:+44 (0)2380 598789
Deputy Director, Open Middleware Infrastructure Institute (OMII)
Suite 6005, Faraday Building (B21), Highfield Campus,
Southampton University, Highfield, Southampton, SO17 1BJ, UK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: draft-ggf-wsi-rus-11.doc
Type: application/msword
Size: 349184 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/rus-wg/attachments/20050723/57a9de54/attachment.doc
More information about the rus-wg
mailing list