15th May

VoSpace

Guy has made a start on the IVOA document. Wanted VoSpace active or generated containers from query results Things that we need to discuss

• V1.0 scope
  • Trade off between simplicity and functionality

• Identifier syntaxWanted VoSpace active or generated containers from query results
  • Encoding the registry identifier
  • URI encoding for node paths

• WSDL
  • Document based, but avoid excluding extensions for further capabilities

As suggested in pleniary session, we should concentrate on

• mandatory
• desirable
• optional

UCD/Semantics are working on IVOA Standrad Vocabulary

• Could this be used for registering protocols and formats ?
• Can UCDs be represented as URIs ?

• Several groups are struggling with defining common vocabularies of things
• VoEvent classification of event types and content
• Theory group also mentioned that they need to describe new types of things
• No common method for doing it - Ideas from MetaGrid ?

UWS

• Work on the initial UWS within the GWS group.
• Concentrate on the parameterized app as the first example

V1.0 interface pages (recover later).

• CreateNode

• ImportInit
• ImportData

• ExportInit
• ExportData

• DeleteNode

• MoveNode
• CopyNode

• ListNodes

• GetNodeProperties
• SetNodeProperties

UCD group renamed to Symantics group Check with them for registering protocols and formats ?

IVOA meetings

Prague Aug 17-18, 21-22

Interop Moscow 18-22 SEPT (need pre-registration)

ADASS USA 15-18 Oct

Interop May 21-25 China

• DougTody
  • Wanted VoSpace active or generated containers from query results
  • Complex data aggregates
  • SIAP 2.0 - data staging via VoStore

• Guy
  • SSO auth mechanism is stable working draft