[ogsa-wg] OGSA Glossary revision 5 uploaded for July 9th call

[Hiro Kishimoto]

Thanks Jem,

 > o        This draft includes several terms from the forthcoming OGSA
 > Data Architecture document, supplied by the OGSA-D WG. The Data
 > section in the OGSA Architecture doc will need to be revised in line
 > with these changes; no firm plan for that at the moment.

The data service teams look ok. Only nits picking from me is definition
of "data access." "Data access" should include "modify the data by the
requesting entity in addition to read-access.

 > o        On Monday’s call we’ll discuss next steps for the document –
 > i.e. when and in what form to propose it for publication, and how to
 > sync with the related documents.

I prefer to synchronize with OGSA architecture document. If OGSA-data-WG
will give us an update of data service section of the OGSA architecture
document. It will be the trigger to publish both OGSA arch v1.6 and
glossary v1.6.

Just my two cents.

Thanks,
----
Hiro Kishimoto

-------- Original Message  --------
Subject: [ogsa-wg] OGSA Glossary revision 5 uploaded for July 9th call
From: Treadwell, Jem <jem.treadwell at hp.com>
To: ogsa-wg <ogsa-wg at ogf.org>
Date: 2007/07/04 7:34

> Hi,
> 
> I’ve uploaded an updated draft (Draft 5) of the OGSA Glossary – you can 
> find it at:
> 
>   https://forge.gridforum.org/sf/go/doc13938?nav=1
> 
> This is for discussion on the July 9^th telecon (next Monday).  Please 
> take a look, and if you’re not going to be on the call please let me 
> have any comments as soon as possible.  Note that:
> 
> o        Once comments have been addressed this draft will wrap up the 
> OGSA/Reference Model glossary convergence activity.
> 
> o        For now, please just review the terms. I haven’t yet fully 
> addressed the changes needed to the front and end sections.
> 
> o        This draft includes several terms from the forthcoming OGSA 
> Data Architecture document, supplied by the OGSA-D WG. The Data section 
> in the OGSA Architecture doc will need to be revised in line with these 
> changes; no firm plan for that at the moment.
> 
> o        On Monday’s call we’ll discuss next steps for the document – 
> i.e. when and in what form to propose it for publication, and how to 
> sync with the related documents.
> 
> Thanks!
> 
> - Jem
> 
> **Jem Treadwell**
> Software Engineer
> 
> *HP ESS Software*
> 856.638.6021 office | 856.638.6190 fax | jem.treadwell at hp.com 
> <mailto:jem.treadwell at hp.com>
> 6000 Irwin Road | Mount Laurel | NJ 08054
> www.hp.com/go/software <http://www.hp.com/go/software>
> 
> hp <http://www.hp.com/go/software>
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> --
>   ogsa-wg mailing list
>   ogsa-wg at ogf.org
>   http://www.ogf.org/mailman/listinfo/ogsa-wg