1 / 7

VOSpace 1.1

T HE US N ATIONAL V IRTUAL O BSERVATORY. VOSpace 1.1. Matthew J. Graham (Caltech, NVO). Data model. Specification - I. Links: extends Node with <target> URI </target> Containers: extends DataNode handles ‘/’ in URIs copy is recursive deep copy move and delete act on children too

gitano
Download Presentation

VOSpace 1.1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. THE US NATIONAL VIRTUAL OBSERVATORY VOSpace 1.1 Matthew J. Graham (Caltech, NVO) IVOA Trieste: Grid & Web Services

  2. Data model IVOA Trieste: Grid & Web Services

  3. Specification - I • Links: • extends Node with <target> URI </target> • Containers: • extends DataNode • handles ‘/’ in URIs • copy is recursive deep copy • move and delete act on children too • list only matches direct children and wildcards only in last step: a/b/c/*.txt • if accepts archive format (tar, zip,etc) will provide access to archive contents as children • inheritable properties IVOA Trieste: Grid & Web Services

  4. Specification - II • Auto-generated names: • .auto is a reserved keyword: vos://service/path/.auto • Find: • regex match on [property][value] • and/or operators:<or> <and> <match uri=“…”> regex </match> <match uri=“…”> regex </match> </and> <match uri=“…”> regex </match></or> • (p1 and p2) or p3 IVOA Trieste: Grid & Web Services

  5. Specification - III • Capabilities to expose 3rd party APIs:<node> <capability uri=“ivo://ivoa.net/srb”> <endpoint> some uri </endpoint> </capability></node> IVOA Trieste: Grid & Web Services

  6. Discussion points - I IVOA Trieste: Grid & Web Services • Data model • Should capabilities only exist on the ContainerNode? • Inheritable properties • If a property is also declared on a child, which value takes priority? • How are properties registered as inheritable? • Container views • What are the names of the children nodes (for a container format that is imported to a container node)? • Are the children nodes Structured_/_UnstructuredDataNodes? • What is the default and is this settable? • How does the service identify what it considers to be archive formats? • Capabilities • What members other than uri and endpoint should a Capability have, e.g. param to specify additional arguments that might be required for access?

  7. Discussion points - II IVOA Trieste: Grid & Web Services • Web service operations • getCapabilities • Do we want this operation (not VOSI)? • createNode • Do we need both a LinkFound and a ContainerNotFound exception or does the latter work for both cases? • findNodes • Are wildcards allowed in the property URIs - find me all nodes where any property matches this regular expression? • pushToVoSpace • If a Node already exists at the target URI and it is a ContainerNode, should it be overwritten by the target Node or should the target Node become a child of the ContainerNode? This also applies to pullToVoSpace.

More Related