perfsonar-dev - Re: [pS-dev] treating the time right in the schema
Subject: perfsonar development work
List archive
- From: "Jeff W. Boote" <>
- To: maxim <>
- Cc: ,
- Subject: Re: [pS-dev] treating the time right in the schema
- Date: Thu, 06 Dec 2007 16:51:44 -0700
maxim wrote:
-----Original Message-----protocols "Black Book" ?...its just about MOU as I understand for now.
From: Jason Zurawski [mailto:] Sent: Thursday, December 06, 2007 5:17 PM
To: Jeff W. Boote
Cc: maxim;
Subject: Re: [pS-dev] treating the time right in the schema
Maxim and Jeff;
For clarification, could one (or perhaps both) of you propose a new way forward. Something small and simple is good enough to kick this discussion off.
--Maxim
Fair enough. We do know we need protocol documents. (And we need to unify the protocols some. Currently they are defined on a service by service basis. That is not good - similar MA's should use the same 'protocol', with only minor differences for different 'profiles' or data types for example.)
Work is underway on this for a few things now. Would you like to help work on
one?
jeff
- RE: [pS-dev] treating the time right in the schema, (continued)
- RE: [pS-dev] treating the time right in the schema, maxim, 12/07/2007
- Re: [pS-dev] treating the time right in the schema, Roman Lapacz, 12/10/2007
- Re: [pS-dev] treating the time right in the schema, Jason Zurawski, 12/10/2007
- Re: [pS-dev] treating the time right in the schema, Roman Lapacz, 12/10/2007
- RE: [pS-dev] treating the time right in the schema, maxim, 12/07/2007
- Re: [pS-dev] treating the time right in the schema, Jeff W. Boote, 12/07/2007
- Re: [pS-dev] treating the time right in the schema, Jeff W. Boote, 12/07/2007
- Re: [pS-dev] treating the time right in the schema, Roman Lapacz, 12/10/2007
- Re: [pS-dev] treating the time right in the schema, Jeff W. Boote, 12/06/2007
- RE: [pS-dev] treating the time right in the schema, maxim, 12/06/2007
- Re: [pS-dev] treating the time right in the schema, Jason Zurawski, 12/06/2007
Archive powered by MHonArc 2.6.16.