VOTable agenda Current VOTable status News from Applications Referring STC (as a data model example) Relations between s Questions about VOTable schema.

Slides:

Advertisements

Similar presentations

VOTable 2005 Discussion Summary and Roadmap. Agenda Description of some applications dealing.

Advertisements

IVOA, Pune India September Data Access Layer Working Group Pune Workshop Summary Doug Tody National Radio Astronomy Observatory International.

VOFilter & VOTable2XHTML Chenzhou CUI, Yanxia ZHANG China-VO Project National Astronomical Observatory of China.

VOTable 2005 Applications. Agenda Description of some applications Description of some applications Nilesh UrunkarAbout C++ Parser and CONVOT Nilesh UrunkarAbout.

SLAP: Simple Line Access Protocol v0.5

SimDB as a TAP service various TIG members (IVOA.IVOATheorySimDB)IVOA.IVOATheorySimDB.

NVOSS 2008 Santa Fe1 Space Time Coordinates Gretchen Greene (many thanks to Arnold Rots) T HE US N ATIONAL V IRTUAL O BSERVATORY Sept 2008.

Metadata in the TAP context (1) The Problem: learn about which tables, tablesets,... are available from a TAP server for each of the tables / tablesets,

CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.

Relational Database. Relational database: a set of relations Relation: made up of 2 parts: − Schema : specifies the name of relations, plus name and type.

Analyzing Systems Using Data Dictionaries Systems Analysis and Design, 7e Kendall & Kendall 8 © 2008 Pearson Prentice Hall.

ILDG File Format Chip Watson, for Middleware & MetaData Working Groups.

Introduction to XLink Transparency No. 1 XML Information Set W3C Recommendation 24 October 2001 (1stEdition) 4 February 2004 (2ndEdition) Cheng-Chia Chen.

McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 6 Developing Data Models for Business Databases.

1 Relational Model. 2 Relational Database: Definitions  Relational database: a set of relations  Relation: made up of 2 parts: – Instance : a table,

Introduction to XML This material is based heavily on the tutorial by the same name at

XP New Perspectives on Microsoft Access 2002 Tutorial 71 Microsoft Access 2002 Tutorial 7 – Integrating Access With the Web and With Other Programs.

Microsoft Office Word 2013 Expert Microsoft Office Word 2013 Expert Courseware # 3251 Lesson 4: Working with Forms.

MS Access: Database Concepts Instructor: Vicki Weidler.

Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

European Space Astronomy Centre (ESAC) Villafranca del Castillo, MADRID (SPAIN) Aurélien Stébé Homogeneous Access to Tabular Data Beijing, China - May.

VOTable: Tabular Data for Virtual Observatory François Ochsenbein Roy Williams Clive Davenhall, Daniel Durand, Pierre Fernique, Robert Hanisch, David Giaretta,

Mapping Data Models to VOTable The specification Published version dml/doc/MappingDMtoVOTable-v pdf.

Contracts & the Semantic Web John McClure Hypergrove Engineering Port Townsend, Washington.

Introduction to XML. XML - Connectivity is Key Need for customized page layout – e.g. filter to display only recent data Downloadable product comparisons.

Chapter 27 The World Wide Web and XML. Copyright © 2004 Pearson Addison-Wesley. All rights reserved.27-2 Topics in this Chapter The Web and the Internet.

Processing of structured documents Spring 2002, Part 2 Helena Ahonen-Myka.

European Space Astronomy Centre (ESAC) Villafranca del Castillo, MADRID (SPAIN) Jesús Salgado SLAP Implementations May 2007, Beijing, China Simple Line.

© 2007 by Prentice Hall 1 Introduction to databases.

Ad Hoc Constraints Objectives of the Lecture : To consider Ad Hoc Constraints in principle; To consider Ad Hoc Constraints in SQL; To consider other aspects.

Software Project Planning Defining the Project Writing the Software Specification Planning the Development Stages Testing the Software.

FALL 2004CENG 351 File Structures and Data Management1 Relational Model Chapter 3.

The european ITM Task Force data structure F. Imbeaux.

Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.

“This presentation is for informational purposes only and may not be incorporated into a contract or agreement.”

A Simple Guide to Using SPSS ( Statistical Package for the Social Sciences) for Windows.

SIP working group IETF#70 Essential corrections Keith Drage.

Starlink VOTable software Author: Mark Taylor Open source Java software for table manipulation STIL:

Working with XML Schemas ©NIITeXtensible Markup Language/Lesson 3/Slide 1 of 36 Objectives In this lesson, you will learn to: * Declare attributes in an.

Slide #1 Boston, Jan 5 – 6, 2005XCON WG Interim draft-levin-xcon-cccp-01.txt By Orit Levin

CLARIN Concept Registry: the new semantic registry Ineke Schuurman, Menzo Windhouwer, Oddrun Ohren, Daniel Zeman

A brief introduction to javadoc and doxygen. What’s in a program file? 1. Comments 2. Code.

Lecture 10 Page 1 CS 111 Summer 2013 File Systems Control Structures A file is a named collection of information Primary roles of file system: – To store.

Discussed in Kyoto Schema changes for the next version (Gerard Lemson)  will be included in VOTable1.2 Schema changes for the next version (Gerard Lemson)

Java Doc Guideline R.SANTHANA GOPALAN. Java Doc Guideline Audience Internal Developers PQA - who write test plans PPT – who write the documentation Customers.

Simple Footprint Previewing Specification and Prototype Requirements Francesco Pierfederici.

VOTable agenda Current VOTable status Current VOTable status News from Applications News from Applications Questions about VOTable schema Questions about.

Starting with Oracle SQL Plus. Today in the lab… Connect to SQL Plus – your schema. Set up two tables. Find the tables in the catalog. Insert four rows.

©2009 HP Confidential1 Proposal to OASIS KMIP TC Stan Feather and Indra Fitzgerald Hewlett-Packard Co. 26 October, 2010 Encoding Options for Key Wrap of.

Project Planning Defining the project Software specification Development stages Software testing.

Virtual Observatory India VOStat Statistical Analysis for the Virtual Observatory By Deoyani and Mohasin.

Level 1-2 Trigger Data Base development Current status and overview Myron Campbell, Alexei Varganov, Stephen Miller University of Michigan August 17, 2000.

Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 The Relational Model Chapter 3.

1 The Relational Data Model David J. Stucki. Relational Model Concepts 2 Fundamental concept: the relation  The Relational Model represents an entire.

1 CS122A: Introduction to Data Management Lecture #4 (E-R  Relational Translation) Instructor: Chen Li.

CENG 351 File Structures and Data Management1 Relational Model Chapter 3.

IT 5433 LM3 Relational Data Model. Learning Objectives: List the 5 properties of relations List the properties of a candidate key, primary key and foreign.

CITA 330 Section 2 DTD. Defining XML Dialects “Well-formedness” is the minimal requirement for an XML document; all XML parsers can check it Any useful.

Accomplishments RSM v0.7 First draft XML Schema completed: VOResource.xsd NVO: Working prototype resource using VOResource as format for metadata exchange.

What is FITS? FITS = Flexible Image Transport System

Introduction to javadoc

Developing a Data Model

Introduction to javadoc

Utypes for Model Referencing

UTYPES Jonathan McDowell.

VOTable Meetings: Conclusions

Presentation transcript:

VOTable agenda Current VOTable status News from Applications Referring STC (as a data model example) Relations between s Questions about VOTable schema Late topics Actions & Future

Where are we ? VOTable1.1 is almost 3 years old (quite stable!) quite generally used, many tools What’s missing:  general referencing to external data models, especially STC  Final schema which satisfies the applications... and some (bogus?) tools

News from Applications VOConvert v1.0 (successor of ConVOT) VOStat (beta version) (on Friday) VOMegaPlot (many rows, density plots), VOPlot v1.4 TOPCAT v2.3 (supports all formats: TABLEDATA / FITS / BINARY). Problem of GROUP not solved ?

Referencing Models in VOTable The tabular material may contain in its fields (columns) any kind of data it is impossible to add into a VOTable document all the various XML codes related to all data models developed by the VO a VOTable document therefore refers to data models without including them

Utypes: what is it ? in VOTable schema: utype is a non-mandatory attribute of any RESOURCE TABLE FIELD PARAM GROUP  originally created for DAL needs  is an acceptable attribute wherever the ucd accepted  contrary to the ucd, gives a fully detailed meaning of the field, parameter or group ucd = broad semantics, typically used for data mining utype = detailed semantics, refers to a data model

Utype: its usage in VOTable can supply an exact description of the column contents immediate application for referencing quantities (parameters and/or fields) which exact meaning is crucial  systems of coordinates: celestial, terrestrial, solar,... (connection with STC)  time definitions (connection with STC)  photometric systems & filters  more generally any parameter part of a model, simulation...

STC Connection STC is an essential component to precise the conventions of dates, locations, coordinate systems (WhenWhere in VOEvent) used in most VO components should replace (and deprecate) the COOSYS ad-hoc convention

Scenarios for STC 5 scenarios are proposed on an example of a table having 5 columns: ObservingTime, RightAscension, Declination, ErrorRA, ErrorDec examples proposed on the VOTable forum. Very few answers up to now – but we have to take a decision this week !

ObservingTime RightAscension Declination RA_Err Dec_Err (ICRS, deg) (ICRS, deg) (arcsec) (arcsec) T23:00: T23:00: T23:00: T23:00: A very simple example

<PARAM name="CooFrame" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.CoordRefFrame.Type" value="ICRS" /> <PARAM name="CooFrameOrigin" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.ReferencePosition.Type" value="TOPOCENTER" /> <PARAM name="CooType" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.CoordFlavor.Type" value="SPHERICAL" /> Double referencing

<FIELD ID="OT" name="ObservingTime" datatype="char" arraysize="19" utype="stc:AstroCoords.Time.TimeInstant.ISOTime" ucd="time.start;obs.exposure" /> <FIELD ID="RA" name="Right Ascension" datatype="double" utype="stc:AstroCoords.Position2D.Value.C1" ref="ICRS_TOPO_SPH" unit="deg" ucd="pos.eq.ra" /> <FIELD ID="DEC" name="DEClination" datatype="double" utype="stc:AstroCoords.Position2D.Value.C2" ref="ICRS_TOPO_SPH" unit="deg" ucd="pos.eq.dec" /> <FIELD ID= "Err1" name="RA_Error" datatype="float" utype="stc:AstroCoords.Position2D.Error.Value.C1" ref="ICRS_TOPO_SPH" unit="arcsec" ucd="error;pos.eq.ra" /> <FIELD ID= "Err2" name="DEC_Error" datatype="float" utype="stc:AstroCoords.Position2D.Error.Value.C2" ref="ICRS_TOPO_SPH" unit="arcsec" ucd=”error;pos.eq.dec" /> Default UTC Time

<PARAM name="TimeScale" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.TimeFrame.TimeScale" value="TT" /> <PARAM name="TimePos" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.TimeFrame.ReferencePosition.Type" value="TOPOCENTER" /> <PARAM name="CooFrame" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.CoordRefFrame.Type" value="ICRS" /> <PARAM name="CooFrameOrigin" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.ReferencePosition.Type" value="TOPOCENTER" /> <PARAM name="CooType" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.CoordFlavor.Type" value="SPHERICAL" /> Time defined No double referencing

<FIELD ID="OT" name="ObservingTime" datatype="char" arraysize="19" ucd="time.start;obs.exposure" utype="stc:AstroCoords.Time.TimeInstant.ISOTime" ref="TT_TOPO"/> <FIELD ID="RA" name="Right Ascension" datatype="double" ucd="pos.eq.ra" unit="deg" utype="stc:AstroCoords.Coord.Value.C1" ref="ICRS_TOPO_SPH"/> <FIELD ID="DEC" name="DEClination" datatype="double" ucd="pos.eq.dec" unit="deg" utype="stc:AstroCoords.Coord.Value.C2" ref="ICRS_TOPO_SPH"/> <FIELD ID= "Err1" name="RA_Error" datatype="float" ucd="error;pos.eq.ra" unit="arcsec" utype="stc:AstroCoords.Coord.Error.Value.C1" ref="ICRS_TOPO_SPH"/> <FIELD ID= "Err2" name="DEC_Error" datatype="float" ucd="error;pos.eq.dec" unit="arcsec" utype="stc:AstroCoords.Coord.Error.Value.C2" ref="ICRS_TOPO_SPH"/>

<PARAM name="TimeScale" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.TimeFrame.TimeScale" value="TT" /> <PARAM name="TimePos" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.TimeFrame.TOPOCENTER" value="" /> <PARAM name="CooFrame" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.ICRS" value="" /> <PARAM name="CooFrameOrigin" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.TOPOCENTER" value="" /> <GROUP name="CooType" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.SPHERICAL" > <PARAM utype="stc:AstroCoordSystem.SpaceFrame.SPHERICAL.coord_naxes" value="2" /> <PARAM name="SpectralPos" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpectralFrame.TOPOCENTER" value="" />

<FIELD ID="OT" name="ObservingTime" datatype="char" arraysize="19" ucd="time.start;obs.exposure" utype="stc:AstroCoords.Time.TimeInstant.ISOTime" ref="TT-ICRS-WAVELENGTH-TOPO" /> <FIELD ID="RA" name="Right Ascension" datatype="double" ucd="pos.eq.ra" unit="deg" utype="stc:AstroCoords.Position2D.Value2.C1" ref="TT-ICRS-WAVELENGTH-TOPO" /> <FIELD ID="DEC" name="DEClination" datatype="double" ucd="pos.eq.dec" unit="deg" utype="stc:AstroCoords.Position2D.Value2.C2" ref="TT-ICRS-WAVELENGTH-TOPO" /> <FIELD ID= "Err1" name="RA_Error" datatype="float" ucd="error;pos.eq.ra" unit="arcsec" utype="stc:AstroCoords.Position2D.Error2.C1" ref="TT-ICRS-WAVELENGTH-TOPO" /> <FIELD ID= "Err2" name="DEC_Error" datatype="float" ucd="error;pos.eq.dec" unit="arcsec" utype="stc:AstroCoords.Position2D.Error2.C2" ref="TT-ICRS-WAVELENGTH-TOPO" />

<PARAM name="STC_ID" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.id" value="TT_ICRS_TOPO"/> <PARAM name="TimeScale" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.TimeFrame.TimeScale" value="TT" /> <PARAM name="TimePos" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.TimeFrame.ReferencePosition.Type" value="TOPOCENTER" /> <PARAM name="CooFrame" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.CoordRefFrame.Type" value="ICRS" /> <PARAM name="CooFrameOrigin" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.ReferencePosition.Type" value="TOPOCENTER" /> <PARAM name="CooType" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.CoordFlavor.Type" value="SPHERICAL" /> <PARAM name="AstroCoo" datatype="char" arraysize="*" utype="stc:AstroCoords.coord_sys_id" value="TT_ICRS_TOPO"/> duplication of the meaning of TT_ICRS _TOPO

<FIELD ID="OT" name="ObservingTime" datatype="char" arraysize="19" utype="stc:AstroCoords.Time.TimeInstant.ISOTime" ucd="time.start;obs.exposure" ref="Coords1" /> <FIELD ID="RA" name="Right Ascension" datatype="double" unit="deg" utype="stc:AstroCoords.Position2D.Value2.C1" ucd="pos.eq.ra" ref="Coords1" /> <FIELD ID="DEC" name="DEClination" unit="deg" datatype="double" utype="stc:AstroCoords.Coord.Value2.C2" ucd="pos.eq.dec" ref="Coords1" /> <FIELD ID= "Err1" name="RA_Error" datatype="float" unit="arcsec" utype="stc:AstroCoords.Coord.Error.Value.C1" ucd="error;pos.eq.ra" ref="Coords1" /> <FIELD ID= "Err2" name="DEC_Error" datatype="float" unit="arcsec" utype="stc:AstroCoords.Coord.Error.Value.C2" ucd="error;pos.eq.dec" ref="Coords1" />

<PARAM name="STC_ID" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.id" value="TT_ICRS_TOPO"/> <PARAM name="TimeScale" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.TimeFrame.TimeScale" value="TT" /> <PARAM name="TimePos" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.TimeFrame.ReferencePosition.Type" value="TOPOCENTER" /> <PARAM name="CooFrame" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.CoordRefFrame.Type" value="ICRS" /> <PARAM name="CooFrameOrigin" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.ReferencePosition.Type" value="TOPOCENTER" /> <PARAM name="CooType" datatype="char" arraysize="*" utype="stc:AstroCoordSystem.SpaceFrame.CoordFlavor.Type" value="SPHERICAL" />

<PARAM name="AstroCoo" datatype="char" arraysize="*" utype="stc:AstroCoords.coord_sys_id" value="TT_ICRS_TOPO"/> Double referencing

<FIELD ID="OT" name="ObservingTime" datatype="char" arraysize="19" utype="stc:AstroCoords.Time.TimeInstant.ISOTime" ucd="time.start;obs.exposure" ref="Coords1" /> <FIELD ID="RA" name="Right Ascension" datatype="double" unit="deg" utype="stc:AstroCoords.Position2D.Value2.C1" ucd="pos.eq.ra" ref="Coords1" /> <FIELD ID="DEC" name="DEClination" unit="deg" datatype="double" utype="stc:AstroCoords.Coord.Value2.C2" ucd="pos.eq.dec" ref="Coords1" /> <FIELD ID= "Err1" name="RA_Error" datatype="float" unit="arcsec" utype="stc:AstroCoords.Coord.Error.Value.C1" ucd="error;pos.eq.ra" ref="Coords1" /> <FIELD ID= "Err2" name="DEC_Error" datatype="float" unit="arcsec" utype="stc:AstroCoords.Coord.Error.Value.C2" ucd="error;pos.eq.dec" ref="Coords1" />

…conclusion ? definition of AstroCoordSystem – necessary or just reference some component of STClib (not yet fully described in STC) ? Wouldn't it be better to have distinct references for time and coordinates ? (most frequently time specification is completely disconnected from coordinate system) double referencing (from GROUP and from FIELD) – useful or bad ? GROUP hierarchy – can it be problematic ?

Why not choose Simplicity? AstroCoordSystem definition only for non- standard system – use otherwise a reference if agreed with other groups, have separate Space, time, wavelength, etc... axes “double referencing” optional

Relations between tables (1) One VOTable document may contain several tables, meaning tables logically grouped. In the relational model, relations between tables are specified via the concept of keys basic key definitions: primary key (non-null, unique) and foreign key (must exist as primary in the related table) A simple solution: GROUPs

Relations between tables (2)...

Relations between tables (3)...

Relations between tables (4) Other possible interesting details: order of the data, e.g. with

Relations between tables (5) What is better:  just a with a specific name ?  prefer the definition of some “relational” data model and refer to these groups with utypes ?

ref attribute to TABLE (1) Current definition: A TABLE may have a ref attribute referencing the ID of another table previously described, which is interpreted as defining a table having a structure identical to the one referenced: this facility avoids a repetition of the definition of tables which may be present many times in a VOTable document.

ref attribute to TABLE (2) the ref attribute refers to the table structure, what about the following:

ref attribute to TABLE (3) from Moscow meeting: allow a reference to an empty table only (i.e. a table without part) is useful for many chunks of the same data structure (e.g. excerpts around a set of positions)  but would it better to allow several in a ?  prefer a supplementary column ?

VOTable schema changes (1) Problem of code generators (xsd) where the class generated by TABLEDATA consists of TD [][] instead of a class TR [] where TR consists in TD []  Easy to solve if an attribute is added to, e.g.  discussed in Moscow – strong opposition !  could be in the schema without being allowed

VOTable schema changes (2) problem – again a bug from code generator  has just 3 attributes: name value ID, plus simple content (i.e. any non-tagged text between and ). This content generates a conflict with the “value” attribute  would be wise to make similar to where datatype is a string (character string of any length), which means: accept utype ucd ID ref unit attributes accept sub- elements

VOTable schema changes (3) Streaming processing delivering VOTable output: there must be a possibility of providing a diagnostic about possible failure in the output stream allow to insert and tags after a ?

VOTable schema changes (4) discussed in Moscow: RESOURCE recursivity can be a problem, accept ? Deprecate, replaced by with its parameters and utypes to the STC model. Accept several in a ?  VOTable1.2 : volunteers to test the new schema ?

VOTable document changes Write down how to reference the STC with actual examples Explain the table relations (primary / foreign key conventions) with examples; other conventions ? Detail the null/NaN conventions