[Volute] r3597 - trunk/projects/dm/vo-dml/mapping/MAST VODML Parser

Volute commit messages volutecommits at g-vo.org
Wed Oct 26 18:05:33 CEST 2016

Author: tdonaldson
Date: Wed Oct  5 13:38:30 2016
New Revision: 3597

Update for vodml-i support

   trunk/projects/dm/vo-dml/mapping/MAST VODML Parser/VODML Parser.html

Modified: trunk/projects/dm/vo-dml/mapping/MAST VODML Parser/VODML Parser.html
--- trunk/projects/dm/vo-dml/mapping/MAST VODML Parser/VODML Parser.html	Wed Oct  5 10:34:07 2016	(r3596)
+++ trunk/projects/dm/vo-dml/mapping/MAST VODML Parser/VODML Parser.html	Wed Oct  5 13:38:30 2016	(r3597)
@@ -119,13 +119,30 @@
 <a href="https://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/sample/Association/Association.votable.xml" target="_blank">Association.votable.xml</a><br>
 <a href="https://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/sample/Composition/Composition.votable.xml" target="_blank">Composition.votable.xml</a><br>
 <a href="https://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/sample/EnumLiteral/EnumLiteral.votable.xml" target="_blank">EnumLiteral.votable.xml</a><br>
+This script runs all the above input files through the parser,
+generating all the output format into the following directories
+(relative to where the script was run).  The links in the
+directories below connect to the committted versions of those output
+directories in SVN.<br>
+<a href="runAll.sh" target="_blank">runAll.sh</a><br>
 <h3>Output Directories</h3>
 <a href="outJson" target="_blank">outJson</a><br>
 <a href="outJsonLite" target="_blank">outJsonLite</a><br>
+<a href="outMast" target="_blank">outMast</a> - A MAST-specific format that contains a variety of additional data to assist the MAST client<br>
+<a href="outVodmli" target="_blank">outVodmli</a> - Vodmli format output<br>
+<a href="outVotable" target="_blank">outVotable</a> - An attempt to recreate a VOTABLE equivalent to the input one.  Possibly useful in round trip regression tests.<br>
 <a href="outVotableAlt" target="_blank">outVotableAlt</a> - These files are in the alternate VODML syntax, and can also be parsed by this same parser.  The schema is <a href="../../xsd/ext/VOTable-1.3_vodmlAlt.xsd" target="_blank">VOTable-1.3_vodmlAlt.xsd</a><br>
 <h2>Output Formats</h2>
 The output formats are based on the likely oversimplified notion that
 the VODML entities represented in the VOTABLE fall into 3 categories:<br>
@@ -144,6 +161,29 @@
 In the alternative mapping VOTABLEs, the templates remain templates, with the table data staying in normal VOTABLE format.<br>
+<h3>VODML-I Notes</h3>
+These are some items that this parser has difficulty with, usually
+because the parser does not read the model itself, and the VOTABLE does
+not contain the desired information:<br>
+    •    I know the vodmlRef (from the
+ROLE), but I don’t know the “name”.  This value if often the tail
+end of the vodmlRef, but doesn’t have to be.<br>
+    •    For each GROUP I see, I don’t
+have any way to know whether to write out an object (object type) or a
+dataObject (value type)<br>
+    ⁃    My transientIDs will be
+internally consistent, but may not match those of others because these
+only count objects and I may have more or less of those than others.<br>
+    ⁃    <br>
+    •    I don’t know whether something belongs in a collection or not.<br>
+    •    I don’t know whether a primitive
+is representing a *Quantity.  I can guess that it is if it has a
+unit attribute.  If it does represent a *Quantity, then which type
+of quantity is it (see next issue)?<br>
+    •    Given a primitive (from a PARAM
+or FIELD), I may only know the primitive VOTABLE type.  How do I
+know the VODML type.<br>

More information about the Volutecommits mailing list