VOSpace WSDL Locators Paul Harrison ESO Euro VO

VOSpace WSDL+ Locators Paul Harrison (ESO, Euro. VO) Matthew J. Graham (Caltech, NVO) Dave Morris (Io. A, Astrogrid) Guy Rixon (Io. A, Astrogrid)

Design considerations • Wanted to make the WSDL more document styled • Wanted to have some of the objects easily reusable in implementing a service. • Needed to see how to incorporate different levels of service compliance (>1. 0) • Correct for the perceived deficiencies in the VOStore WSDL. – Include faults – Make some operation names clearer 9/15/2021 2

WSDL Upgrade Path • Initial plan was to try to make VOSpace 2. 0 WSDL upwardly compatible with VOSpace 1. 0 WSDL - so that a 1. 0 client could call 2. 0 service. • Dropped this because it put too many constraints on the schema. – Implies that clients will have to be able to talk 1. 0 and 2. 0 – 1. 0 services are envisaged to be “leaves” in the VOSpace tree. 9/15/2021 3

VOSpace Locators • Want URI syntax • Follow recommendations of RFC 3986 and RFC 2718 • In fact we want the subset of URIs that form hierarchical URLs – //…. . / is the signature – Query part resolved by service – Fragment part resolved by client foo: //example. com: 8042/over/there? name=ferret#nose scheme authority path query 9/15/2021 fragment 4

Standard URL behaviour • We propose VOSpace locators as a new URI scheme vos: – We want to have standard relative URL syntax to work, as VOSpace will have links. – We want to be able to use the “Query” part to be able to specify functionality such as “return this data object as VOTable” – We want to be able to use the “Fragment” part to be able to specify functionality such as “the 2 nd image in the FITS file” 9/15/2021 5

Problems with IVOA Identifiers • IVOA Identifiers unfortunately follow the hierarchical URL form, but they are identifiers there is no hierarchy - i. e. for – ivo: //net. ivoa/set/myresource – ivo: //net. ivoa/set/ has no meaning • In vos: scheme the IVO identifier of the VOSpace logically plays the role of the authority, but syntactically cannot be used directly, because the parsing rules for URLs say that the authority lies between “//” and the next “/”. 9/15/2021 6

VOSpace URL • Suppose IVOA ID for the VOSpace is ivo: //org. vo/vospace • Data object in the VOSpace /path/to/my. Data • Full URL of the data object vos: //org. vo!vospace/path/to/my. Data 9/15/2021 7