If this "hack" exist, can we insure that it will resist to an evolution of the model ? If a basic client want to retrieve space or time meta data description from the VODML serialization header, does it can use some simple hacks (based on ref label or similar thing) ? Or there is no alternative and it has to to parse and understand the associated model (or use dedicated libs). Price of the entry ticket for the client ?.Same question for time (time frame, origine, offset, format = the possible TIMESYS that I would like to have) What would be the mapping to describe the same information that I have in COOSYS and associated FIELDs (RA,DEC,PMRA,PMDEC designation + SYSTEM/EPOCH) ? Is it reasonably understandable by reading "manually" the VOTable ? Or does it really require a dedicated tool ? What is the part of the FIELD metadata information duplicated in the model ? datatype ? unit ? UCD ? more ? Same question for client codes, and server codes.įor interpreting a VODML annotation, does the client may have to access/download external information (via registry or other DM repository system ?). Model evolution - clients/server impact.Still usable, or should need to be updated ? Is it easy doable ? If one of these models is extended in the future, what is the impact on the existing VOTables (static stored files). If some IVOA partners prefer to use CAOM model (or another) to annotate their VOTables, what will be the impact on the global interoperability ? How a client based on the IVOA regular model will be able to understand VOTable annotated based on another model ? Is it reasonable to think that we could have a unique IVOA model coherent, ready and adopted now (probably based on the convergence of our various DM efforts (STC1, and now STC2, Image DM, Cube DM.) ? If no, how to start ? I try/have to evaluate what could be the impacts if we are adopting VO-DML serialization principle as it has been presented yesterday (for IVOA Apps, and more pragmatically, for CDS).Īll this effort is based on the pre-existence of a global model defined and adopted by the IVOA. Nonetheless it was a good experience, let's continue having hack-a-thons. Unfortunately, using the latest (3.7) version of Modelio it turned out that the xmi-to-xml xslt transform requires some fixing. Starting from DM knowledge and expertise at level 0, having only followed the Beginner's Guide install steps, I grasped the first notions on how to build my model graphically and then went on trying to generate the VO-DML.xml. How does this relate to the units on the FIELDs? Is it duplication, or does it represent a different flavor of unit, or can/should the VODML unit be left blank in cases where a FIELD specifies it?
0 Comments
Leave a Reply. |