<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, May 26, 2017 at 7:52 AM, Gerard Lemson <span dir="ltr"><<a href="mailto:gerard.lemson@gmail.com" target="_blank">gerard.lemson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">HI Baptiste<br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Fri, May 26, 2017 at 3:50 AM, Baptiste Cecconi <span dir="ltr"><<a href="mailto:baptiste.cecconi@obspm.fr" target="_blank">baptiste.cecconi@<wbr>obspm.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div>Dear Gerard,</div><div><br></div><div>thank you for your answer. </div><div>It is a bit unfortunate that there is no XSD instance of STC2 available. </div><div><br></div><div>We would like to check the new model version by trying out simple XML instantiation for our VOEvent project and compare with the previous STC model version.</div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div>I'm afraid we won't have the time to do through XSLT set up and debugging any time soon in our project (nor Pierre nor other persons) and I don't have the skills to do so. </div><div><br></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><div></div><div>The "entry fee" seems to be quite high just to test if the new version of the model solve the problems we have in the previous one. </div></div><div><br></div></div></blockquote></span><div>Might be very useful for the STC modeling effort as well as for a possible XSD mapping if you could give an indication what those problems were. </div><div><br></div></div></div><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>I hope that we can get a working solution soon! </div></div></blockquote></span><div><div><br></div><div>That will depend on DM chairs and especially availability of people to do the work. </div><div><br></div><div>I am interested to have a look at XML schema generation, but my priorities are elsewhere so I won't have much time either.</div><div><div>And whatever the XSLT would be to generate XSD from VO-DML, for sure the resulting schema would be very different from the previous one. (No susbsitutionGroup-s! No element-refs!) </div><div> </div></div><div>A custom XSD for STC could be created no doubt. </div><div>Seems to me that VOEvent does have its own STC-like definitions already though. Are there plans for incorporating STC in VOEvent? Is what VOEvent offers not sufficient?<br></div></div></div></div></div></blockquote><div><br></div><div>Those are based on the STC-1.33 XSD.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div></div><div><br></div><div>It might be interesting to see if the VOEvent schema could somehow be annotated with VO-DML elements similar to the VOTable mapping spec. To indicate that some of its types have representations in STC/VO-DML. A generic-XSD->VO-DML mapping (as opposed to VO-DML->XSD mapping) is a much bigger topic, but could use that as an example. <br></div><div> <br></div><div><br></div><div>Cheers</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Gerard</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"></div></blockquote></font></span></div><div><div class="h5"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>Cheers</div><div>Baptiste</div><div><br></div><div><br></div><br><div><blockquote type="cite"><div>Le 25 mai 2017 à 19:49, Gerard Lemson <<a href="mailto:gerard.lemson@gmail.com" target="_blank">gerard.lemson@gmail.com</a>> a écrit :</div><br class="m_-3044753198581529241gmail-m_-2305264041042946772Apple-interchange-newline"><div><div dir="ltr">HI Pierre <div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 22, 2017 at 11:12 PM, Pierre Le Sidaner <span dir="ltr"><<a href="mailto:pierre.lesidaner@obspm.fr" target="_blank">pierre.lesidaner@obspm.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi<br>
<br>
I have seen the description of the STC2 DM at <a href="http://volute.g-vo.org/svn/trunk/projects/dm/STC-2.0/doc" rel="noreferrer" target="_blank">http://volute.g-vo.org/svn/tru<wbr>nk/projects/dm/STC-2.0/doc</a><br>
<br>
I have seen also xmi files model directory<br>
<br>
My question is mainly for VO-DML group, is there a possibility to have STC2 express in an xml schema (xsd) ?<br>
<br>
It would be very useful to make usage of it and validate.<br>
<br>
Does VO-DML have tool to transform the serialisation of schema into such a format ?<br>
<br></blockquote><div><br></div><div><div>There is currently no script to translate from VO-DML to XSD.</div><div>But nothing stops one from creating one, the mapping between VO-DMl and XSD is quite straightforward. See appendix B1 of the VO-DML spec for an example. </div><div><br></div><div>In fact there is such an XSLT script for the related VO-URP "spec" at </div><div><a href="https://github.com/glemson/vo-urp/blob/master/res/intermediate2xsd.xsl" target="_blank">https://github.com/glemson/vo-<wbr>urp/blob/master/res/intermedia<wbr>te2xsd.xsl</a> </div><div><br></div><div>This was used to create the XSD representation for the Simulation DM in <a href="http://www.ivoa.net/documents/SimDM/20120503/xsd/" target="_blank">http://www.ivoa.net/documents/<wbr>SimDM/20120503/xsd/</a> </div><div>It's source was what we then called the intermediate representation" of the data model in </div><div><a href="http://www.ivoa.net/documents/SimDM/20120503/uml/SimDM_INTERMEDIATE.xml" target="_blank">http://www.ivoa.net/documents/<wbr>SimDM/20120503/uml/SimDM_INTER<wbr>MEDIATE.xml</a></div><div>See section 4.2 of the simulation data model (<a href="http://www.ivoa.net/documents/SimDM/20120503/index.html" target="_blank">http://www.ivoa.net/documents<wbr>/SimDM/20120503/index.html</a>) for a short description.</div><div><br></div><div>The intermediate XML is closely related to the VO-DML/XML. Hence it should not be hard to modify the XSLT to also work for VO-DML, and I have planned to do that once I found the time. Maybe someone else can use it as inspiration?</div><div><br></div><div>Main difference between VO-DML and VO-URP is that the former can import models and in fact the primitive datatypes are defined in the base ivoa model in VO-DML, but as an enumeration in VO-URP.</div><div><br></div><div>And also note that a particular mapping scheme was used in the XSLT. Laurent Bourges and I used that in a web application that translates between XSD, Java and RDB, but it may not be to everyone's liking. In particular the treatment of references was tricky. We also made the explicit decision to separate the type definitions from the definitions of the root elements. And those were limited to correspond to the non abstract root types only, i.e. those that are not the child in a composition relation. </div></div><div><br></div><div>I am happy to assist in porting the XSLT from VO-URP to VO-DML, but hope others are interested as well.</div><div><br></div><div>Cheers</div><div><br></div><div>Gerard</div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
regards<br>
<br>
Pierre<br>
<br>
-- <br>
------------------------------<wbr>------------------------------<wbr>-------------<br>
Pierre Le Sidaner<br>
Observatoire de Paris<br>
<br>
Direction Informatique de l'Observatoire<br>
Observatoire Virtuel 01 40 51 20 82<br>
61, avenue de l'Observatoire 75014 Paris<br>
<br>
mailto:<a href="mailto:pierre.lesidaner@obspm.fr" target="_blank">pierre.lesidaner@obspm.<wbr>fr</a><br>
<a href="http://padc.obspm.fr/" rel="noreferrer" target="_blank">http://padc.obspm.fr</a><br>
<br>
------------------------------<wbr>------------------------------<wbr>--------------<br>
<br>
</blockquote></div><br></div></div>
</div></blockquote></div><br></div></blockquote></div></div></div><br></div></div>
</blockquote></div><br></div></div>