<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 3, 2019 at 6:09 AM Markus Demleitner <<a href="mailto:msdemlei@ari.uni-heidelberg.de">msdemlei@ari.uni-heidelberg.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Laurent,<br>
<br>
On Tue, Sep 03, 2019 at 10:36:18AM +0200, Laurent MICHEL wrote:<br>
> Connection with Semantic<br>
> ========================<br>
> No doubt that connecting models and semantic is a good thing, but the way to<br>
> do it is not clear to me.<br>
> An attribute with a limited set of possible values must be typed as an Enum.<br>
> The Enum is a UML (and VO-DML) dataType which has to be defined in the<br>
> model.<br>
<br>
VO-DML as it stands already has a link to vocabularies through<br>
SemanticConcept, which, however, requires SKOS vocabularies. These<br>
are not really what I'd consider ideal for these little word lists<br>
for various reasons (cf. the current internal draft for the<br>
future Vocabularies spec, <a href="http://docs.g-vo.org/vocinvo2.pdf" rel="noreferrer" target="_blank">http://docs.g-vo.org/vocinvo2.pdf</a>). <br>
<br>
So, while we could use SKOS and it would probably the quickest<br>
"formal" solution, let's look at alternatives:<br>
<br></blockquote><div><br><br></div><div>The Coords model uses <br> + vocabularies for reference frame, reference position, and time scale.<br></div><div> which are fairly dynamic, likely to need changes. For these, it was decided to <br></div><div> scale down the rather set of values from the earlier draft Enums, into a small<br></div><div> set of most commonly used, and let the vocabulary grow as needed.<br></div><div> This also let the Planetary folks work their needs in as well.<br></div><div> + but would still have Enums for things with a fairly short list of options which<br></div><div> which are not likely to change. For example, we still have a Handedness enum.<br></div><div><br></div><div>and Simulation uses them (right?)<br><br></div><div>I'm not sure which category the ones in Provenance fall under. I know that <br></div><div>during the work to get here, there was effort made to distinguish items which<br></div><div>are 'free form', but should use a 'term from a recommended list', and things<br></div><div>which must have particular values (Enums).<br><br></div><div>Mark<br><br></div></div></div>