UtypesTigerTeamMinTel16 < IVOA

IVOA Web>WebPreferences>UtypesTigerTeamMinTel16 (2013-04-23, JesusSalgado) (raw view)

Minutes UTYPEs tiger team telecon 2013-04-16<br />absent: Mireille (ML), Pierre (PF)

MD Clarification of the tasks we are charge to produce<br />OL There is an email from Severin<br />GL reads the email description<br />OL Regarding VO/DML, the final solution propoased is very close to Sebastian approach on catalogs<br />MD we are doing something a little bit different<br />GL simdm was accepted<br />MG solution not accepted by all the institutions<br />GL not clear that it is not acceptable<br />MG PF says no ML is more balanced<br />GL A particular VOTable can still be done as before<br />OL We actually tried to minimize the transition from one model to the other. <br />GL We do not say current use cannot be used<br />MD Solid foundation in the presentation to Exec<br />GL ML wants to have the semantics in the utype itself and not into the FIELFRef<br />OL Parsing the utypes with support for collections and references could be also used<br />GL It would be harder to do it that groups (in case all the support for collections & references is fullfilled)<br />MG As as summary, the problem is that we are missing the semantics meaning in the utypes<br />MD We should put more about SED and SpectralDM in the usages section. I volunteer myself<br />OL We should probably divide the work as we are charge to solve the utypes syntax<br />MG We are trying to do that with the division in two documents<br />MD These two documents are correlated and we cannot write one without reference to the other<br />OL One objection, we did not have the mandate to create the DM framework<br />GL We cannot disantagle utypes and the expresion in VOTable. If utypes are not xpath expressions but pointers. We are asuming the Data modeling framework<br />GL We are not sure if path expressions can be valid in other use cases<br />JS in favour of a backwards compatible approach<br />GL we do not say it is not still valid the old utypes use

GL not semantics associated to path expressions<br />JS described approach (using path utypes as aliases into VOTable fields). Alias table is not a simple table but path utypes associated to groups <br />OL there is not a uniform standard for utypes syntax (eg. aladin brackets)<br />JS sebastien proposal is more like the approach I propose (vo/dml with path utypes)<br />OL not really that. Not real VO/DML. He stopped at first group level<br />MD we should concentrate on the documents skeleton<br />GL VO/DML first version is on volute (two different versions) and ML/OL on charge of second review of utypes doc<br />MG Usage document will contain also the analysis<br />MD IRIS has already part of this analysis<br />OL if the starting point is you can use

GL DM translation into VO/DML

Global discussion on the edition of utypes mapping document.

Parallel teleconf proposed with GL, OL, ML and JS

Topic revision: r1 - 2013-04-23 - JesusSalgado

IVOA

Log in or Register

IVOA.net
Wiki Home
WebChanges
WebTopicList
WebStatistics

Twiki Meta & Help
IVOA
Know
Main
Sandbox
TWiki

TWiki intro
TWiki tutorial
User registration
Notify me

Working Groups

Interest Groups

Time Domain

Committees

Stds&Procs

www.ivoa.net
Documents
Events
Members
XML Schema