users computers user layer resource layer using sharing vo core providers 20100525 ivoa architecture...

3
USERS COMPUTERS USER LAYER RESOURCE LAYER USING SHARING VO CORE PROVIDERS 20100525 IVOA Architecture VOSpec

Upload: sophia-sparks

Post on 27-Mar-2015

214 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: USERS COMPUTERS USER LAYER RESOURCE LAYER USING SHARING VO CORE PROVIDERS 20100525 IVOA Architecture VOSpec

USERS

COMPUTERS

USER LAYER

RESOURCE LAYER

USING

SHARING

VOCORE

PROVIDERS20100525

IVOA Architecture

VOSpec

Page 2: USERS COMPUTERS USER LAYER RESOURCE LAYER USING SHARING VO CORE PROVIDERS 20100525 IVOA Architecture VOSpec

USERS

COMPUTERS

USER LAYER

RESOURCE LAYER

USING

SHARING

VOCORE

PROVIDERS20100525

IVOA Architecture

DataModelsSemantics

Browser BasedApps

Script BasedAppsDesktop Apps

Data and Metadata Collection

DATA

ACCESS

PROTOCOLS

REGISTRY

Resource Metadata

Registry Interface

VOResource

ApplicationsRegExt

StandardsRegExt

VODataService

SimpleDALRegExt

VOSI

SSAP

SIAP

SCS

TAP

SEAP

SimDAP

SLAP

VOSpace VOPipe

SAMPSSO UWS

CDP WS BP

VO QueryLanguages

Formats

ADQL

PQL

UCD

Vocabularies

Resource Identifier VOTable

SpectrumDM

SSLDM

VOEvent

SimDM

ObsCoreDM

ObsProvDM

CharDM

PhotDM

Utypes

Units

STC

VOSpec

FAP

Storage Computation

REC

InProgress

REC used

Std to beupdated or

created

Page 3: USERS COMPUTERS USER LAYER RESOURCE LAYER USING SHARING VO CORE PROVIDERS 20100525 IVOA Architecture VOSpec

USERS

COMPUTERS

USER LAYER

RESOURCE LAYER

USING

SHARING

VOCORE

PROVIDERS20100525

IVOA Architecture

Notes

• Protocols VOSpec is using (SSAP and SLAP) are UTYPE-based, so the use of UCDs is secondary

• UNITS DM draft is partially based in the Unit object used in VOSpec

• VODataService is used in the Registry query• Resource identifier is internally used to distinguish the

Registry records • CharDM is indirectly used in two ways: when reading

SSAP responses, and using the SED library, that has Characterization objects

• (There is an implementation of  a connection between VOSpace and VOSpec, but currently disabled)