[BYTEIO-WG] Document process / FLE's slate on the Experience document

[Michel Drescher]

Folks,

firstly, here's FLE's fist take on the Experience document.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ByteIO_Experience_Doc_FLE.doc
Type: application/octet-stream
Size: 108032 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/byteio-wg/attachments/20071015/a4d2358c/attachment-0001.obj 
-------------- next part --------------

Secondly, and that's what this mail is mainly all about, I had a chat  
with Greg Newby about the documents process regarding ByteIO.

As a summary, our situation is kind of special, because during the  
Interop test, we found issues that made us change the XML renderings  
for the specification to ensure interoperability. No doubt there are  
groups in OGF and elsewhere that may be in th the same situation when  
they do interoperability, but the point is that the current OGF  
documents process has a definition hole for this situation.

After a longer discussion with Greg we agreed that this needs fixing  
in the revision of GFD.1 which is currently in public comment, and  
that Greg will address that.

The consequences for us are hence as follows.

1) We still need to return the Interoperbility document t GFSG with  
changes coming from the PC period. I will take care of that.

2) The Experience document we are writing at the moment will go  
through its own PC period as normal. How ever, this document will  
explicitly mention and document that as a result of the interop  
tests, we had to change the XML rendering for the Specification,  
hence obsoleting the relevant appendices of the Functional Spec and  
the WSRF rendering, where appropriate, The document then will also  
explicitly mention that the online version of the XML and WSDL will  
reflect the latest version of the XML and WSDL.

2.1) We therefore need to add a chapter to the Experience document  
that describes the changes to the XML and WSDL as outlined above.  
THat way, we update the spec without having to go through the fairly  
heavyweight process of a new set of requirements documents.

Cheers,
Michel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.ogf.org/pipermail/byteio-wg/attachments/20071015/a4d2358c/attachment-0001.bin