perfsonar development work

[Nicolas Simar <>]

Nicolas Simar wrote:
> Jeff W. Boote wrote:
>
> > Hi Nicolas,
> >
> > I think this is a good step forward. All the pieces are there. My 
> > major concern is with some of the organization. I think too much is 
> > devoted to schema (rnc) concerns, and not enough to protocol. 
>
>
> It wasn't intentional if it appear as it is.
> Suggestion/proposal is welcome to modify it.
>
> I foresaw two roles for that document:
> 1) catch the information requirements from the developers
> 2) get a global overview of the document that are needed and what 
> already exist.
>
> The next step is to match those requirement against Jason's protocol 
> document proposal.
>
> > And, the lines between base/extension/service information is not so 
> > clear in many cases. I think it will take some real work to make this 
> > clear.
> >
> > This would probably be a good topic for the next full pS developers 
> > meeting (whenever that will be).
> >
> > [I apologize for not having time to give more substantive suggestions 
> > right now. Jason and I were just talking. Perhaps we can make a more 
> > substantial contribution to defining this after our MDM releases are 
> > ready?]
>
>
> I think getting a pointer to a protocol document from Jason would be a 
> good starting point.

I just saw the pointer sent by Jason. (it was in a different folder).
Thanks.

Nicolas

> Cheers,
> Nicolas
>
> > Thanks,
> > jeff
> >
> > Nicolas Simar wrote:
> >
> > > Hi,
> > >
> > > you can find in attachment a document which identifies the different 
> > > documents that one can need.
> > >
> > > The goal of this document is to provide a “framework” of documents 
> > > (specifications, documentation) for perfSONAR and to identify the 
> > > information required so that we can have a stable 
> > > documentation/specification documentation structure.
> > >
> > > The document aims at identifying
> > > 1.    the different technical documents (specifications) that the 
> > > developers needs to have to implement inter-actions between the 
> > > services.
> > > 2.    the documentation that are provided for each service (e.g. for 
> > > the GUI developers to inter-act with a particular implementation of a 
> > > message or protocol).
> > > 3.    the process involved (e.g. to extend a schema, etc)
> > >
> > > For each type of documents, a high level description of the document 
> > > content or the multiple document that need to be produced is provided.
> > >
> > >
> > > I do strongly encourage you to read the document and
> > > - comment it
> > > - add the information you think is necessary to be in a document
> > > - raise question and points regarding the content of the document or 
> > > their structuration of the documents.
> > >
> > > The document and your comment will be used for a dedicated session in 
> > > Rome.
> > >
> > > Thank you very much in advance.
> > >
> > > Best regards,

--
Nicolas
______________________________________________________________________

Nicolas Simar
Network Engineer

DANTE - www.dante.net

Tel - BE: +32 (0) 4 366 93 49
Tel - UK: +44 (0)1223 371 300
Mobile: +44 (0) 7740 176 883

City House, 126-130 Hills Road
Cambridge CB2 1PQ
UK
_____________________________________________________________________