---+ Comments on [[VODML][VO-DML specification documents]] This page aims to keep track of comments made about the VO-DML spec on [[VODML][this page]] in the WG discussion phase. Link to first entry in email list that starts the discussion. It also lists some open issues for which a particular choice was made, but where other choices could be preferrable. ---+++ Comments from DM mailing list * [[http://www.ivoa.net/pipermail/dm/2014-April/004972.html][Arnold Rots, 2014-04-24]]: * Rename !ReferencableElement to !RefenceableElement. * [[http://www.ivoa.net/pipermail/dm/2014-April/004975.html][Mark Cresitello-Dittmar, 2014-04-25]] <br />Cmments about the basic [[https://volute.googlecode.com/svn/trunk/projects/dm/vo-dml/models/ivoa/IVOA.vo-dml.xml]['ivoa' model]] that is supposed to be used (imported) by all IVOA models * Add !TimeValue to ivoa model. * Add ivoa:URL as sub-type of ivoa:anyURI. ---+++ Open issues identified by editors/authors * Model inherits from Package. This, with use of <sequence> in XSD causes some model specific features such as _authors_, _version_ etc to end up at the end of a Model definition. Is this cumbersome? Reasons we did this is to inherit common elements like vodml-id, name,d escription and all the type collections. Also, UML has the same patterns, i.e. Model is-a special kind of Package there. * <em> vodml-id</em>-s should be unique in document for all elements not a <model>. Should we extend this rule to <model> as well? Note that when generating vodml-id using generaiton rules a package with the same name as the vodml-id of the model would end up with same vodml-id, hence no uniqueness. Ofcourse one need not use such rules, or can give package a vodml-id different from its name to resolve this. Alternatively we could insist on using model's vodml-id as prefix for vodml-ids as well. Currently only utypes must have a prefix. * When referreing to a vodml-id using a utype element one always MUST use as prefix the vodml-id of the model, whether an imported model or the model itself. It was a decision of the tiger team to make such prefixes "globally unique", i.e. every usage within the IVOA MUST use the same prefix, which MUST be the vodml-id of the model. This in contrast e.g. to XSD namespace/xmlns where prefixes can be freely declared. Sould we revisit this? * ModelProxy has an element named prefix, which currently MUST be the same as the vodml-id of the imported model it represents. Is this name, prefix, ok? * ... <!-- * Set ALLOWTOPICRENAME = IVOA.TWikiAdminGroup -->
This topic: IVOA
>
WebHome
>
IvoaDataModel
>
VODML
>
VoDmlWGComments
Topic revision: r3 - 2014-05-03 - GerardLemson
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback