<div dir="ltr"><div><div><div><div><div><div><div><div>All,<br><br></div>How about 'label'? Though I have no strong opinion one way or the other.<br></div><br></div>I think the idea would be to present a 'real-world' equivalent to the token<br></div>which would be used for user interaction (eg: display). <br><br>In the DatasetMetadata instances <br></div> SpectralBandType<br></div></div> + "X-ray"<br></div> + "Gamma-ray"<br><br><div><div><div><div><div><div><div><div>can move to <br> SpectralBandType<br> + name="xray" [title|label]="X-ray"<br> + name="gammaray" [title|label]="Gamma-ray"<br><br></div><div>so the name can conform to a pattern, but still define a familiar translation.<br></div><div>A similar thing could be done with the CreationType tokens.<br><br></div><div>>>Mark, Arnold, any problems simply making the 'name' of the enumliterals conform to these rules?<br><br>I do think having the free-form option is important. The values of these enums are rooted in <br></div><div>the various standards (ObsCore, ResourceMetadata, VODataService). I think there is some<br></div><div>flexibility for making viable tokens, but would like to keep the full spec.<br></div><div><br></div><div>Mark<br><br></div><div><br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 11, 2016 at 4:33 AM, Markus Demleitner <span dir="ltr"><<a href="mailto:msdemlei@ari.uni-heidelberg.de" target="_blank">msdemlei@ari.uni-heidelberg.de</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 DM,<br>
<span class=""><br>
On Sun, Jan 10, 2016 at 01:14:46PM +0000, Gerard Lemson wrote:<br>
> I think one obvious solution might be to add a 'fullName' attribute<br>
> (or 'title'? I'd be open to alternative name) to EnumLiteral that<br>
<br>
</span>I guess it'd be "title" for me if I had to choose. But what use<br>
would it be (i.e., how is Software expected to use this title)?<br>
<span class=""><br>
> The other, more straightforward solution is to restrict<br>
> enumliterals to the pattern for VODMLName.<br>
> I actually slightly prefer this solution and not only because it is<br>
> simpler. Enumerations are primitive types with a discrete set of<br>
<br>
</span>With the caveat that I have no implementation experience here (and<br>
the judge on gut feeling and conjecture), I'm fairly sure this is far<br>
preferable; if those enums are going to be mapped to enums in<br>
languages that have them, the literals must follow these languages'<br>
identifier rules. Since neither LISP nor FORTH are the mainstream<br>
languages we target, we had better have a restrictive pattern that<br>
actually works with identifiers in C, Java and Python. Which happens<br>
to be what this alternative does.<br>
<br>
Perfect with me.<br>
<br>
Cheers,<br>
<br>
Markus<br>
</blockquote></div><br></div></div></div></div></div></div></div></div></div></div></div>