vo-dml for cube
Laurent Michel
laurent.michel at astro.unistra.fr
Mon Dec 14 13:31:16 CET 2015
Dear Omar,
I totally agree with your explanation as long as we are are in a in a context of relational persistence. N-m or even 1-n
relationships must be modelled by collections of ObjectTypes (classes) and not by DataTypes, simply because the relational model
does not allow to join (aggregate) anything but tables (to make simple, tables reflect ObjectTypes with one column per atomic
attribute, see Omar's mail below) .
But the fact is that we are not only working with persistent data. To borrow the Arnold's example, image meta data are (or can
be) persistent but pixels are not. Pixels are entities which are stored within files and which are processed into a
computational context; in a transient context in others words.
Let's suppose that we are using a library issued from such a restrictive model. In this library, ObjectTypes would be
implemented as classes. In consequence and since pixels are ObjectTypes, we'll have to build one object instance for each pixel.
This is obviously not acceptable in term of efficiency.
The question is to know whether variable length arrays have to be banned from the modelling tasks just because they does not
comply with the Object-Relational mapping rules. Is that not giving too much importance to these rules?
Laurent
Le 11/12/2015 18:38, Laurino, Omar a écrit :
> Gerard, all,
>
> I agree that Object-Relational Mapping seems to constraint the multiplicity of attributes, but only in the sense that you can't
> "refer to" a datatype, i.e. an entity in its own database table, and so you can't build 1 to N or N to M relationships as you do
> with entities.
>
> However, this assumes, as Gerard explicitly mentioned, that you are treating each column as a value in the array. So, with an
> array of multiplicity N, you need exactly N columns to represent the datatype. And you cannot have an undefined, or variable,
> number of columns.
>
> However, there are mapping strategies for allowing variable length arrays. For instance, you can indeed map a byte array (e.g. a
> picture) with standard ORM mappings. See for instance the @Lob annotation in JPA (Java Persistence API):
> http://docs.oracle.com/javaee/6/api/javax/persistence/Lob.html
>
> Keeping JPA as an example, one can also map a variable array to a java List using ElementCollection, see for instance:
> https://en.wikibooks.org/wiki/Java_Persistence/ElementCollection#Basic_Collections
>
> However, in the above example order may not be preserved, which might be a show-stopper for some use cases (e.g. the polynomial
> coefficients, unless you store the order as well).
>
> EclipseLink clearly documents Arrays of DataTypes, and they describe them quite explicitly in their documentation in opposition
> to the Object Type Array mapping:
> https://wiki.eclipse.org/Introduction_to_Object-Relational_Data_Type_Mappings_(ELUG)#Object-Relational_Data_Type_Array_Mapping
>
> They also cite the case of nested tables, which do not preserve order, but resemble the way you create 1 to N relationships
> between entities.
>
> I tried to find other examples outside of my Java comfort zone, but in all likelihood there are ways of dealing with arbitrary
> length arrays in ORM outside of the JPA stack, so I'll keep it short.
>
> That being said, I think Gerard is also arguing that when you have a requirement for a variable length array you can probably
> review your design to use object types rather than data types.
>
> The problem is that this becomes, unsurprisingly, bound to the use case. So, I would suggest that we separate the two issues.
>
> I think the constraint on not having variable length arrays of datatypes is somewhat arbitrary and I can't really see this
> constraint in ORM standards and implementations out there.
>
> On the other hand, there may be merit in the objection that STC might not need them, but this objection can only be corroborated
> by an alternative model that fulfills the same requirements with a different approach than what has been suggested so far.
>
> My 2 cents,
>
> Omar.
>
>
> On Fri, Dec 11, 2015 at 7:58 AM, Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>> wrote:
>
> HI (adding dm at ivoa in the Cc)____
>
> __ __
>
> Allowing 0..n, implying EITHER 0 OR exactly n with n a literal is same as discussed before (and below in email trail).____
>
> The current doc does not include this yet, I have had no other opinions about this but yours, but I think it is reasonable.____
>
> I thought I had already updated the doc, but apparently not yet.____
>
> __ __
>
> Allowing n to be an integer attribute with multiplicity 1 I am still strongly against.____
>
> For example, what if, after initializing the 0..n attribute, you change the value of n?____
>
> This possibility implies to me still that the concept represented by the 0..n attribute should not be a datatype, but should
> be represented by a collection of object types.____
>
> __ __
>
> I am also still doubtful of the use cases that would seem to require this.____
>
> The cases where I have seen you use this feature in STC can and imho SHOULD be designed differently. ____
>
> I think the dm group MUST start looking seriously at STC before its presumed requirements are used to influence the
> language.____
>
> __ __
>
> Any comments from the others.____
>
> __ __
>
> Cheers____
>
> Gerard____
>
> __ __
>
> __ __
>
> *From:*Arnold Rots [mailto:arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>]
> *Sent:* Thursday, December 10, 2015 5:23 PM
> *To:* Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>>
> *Cc:* CresitelloDittmar, Mark <mdittmar at cfa.harvard.edu <mailto:mdittmar at cfa.harvard.edu>>; Omar Laurino
> (olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>) <olaurino at head.cfa.harvard.edu
> <mailto:olaurino at head.cfa.harvard.edu>>; msdemlei at ari.uni-heidelberg.de <mailto:msdemlei at ari.uni-heidelberg.de>
>
>
> *Subject:* Re: vo-dml for cube____
>
> __ __
>
> Would it be acceptable extend this slightly:____
>
> Multiplicity must be "[0..]n", meaning that the multiplicity is either 0 (but only if "0.." is present) or n,____
>
> and where n is either a numeric literal or an existing nonnegative integer attribute with multiplicity 1.
>
> ____
>
> Cheers,____
>
> - Arnold____
>
>
> ____
>
> -------------------------------------------------------------------------------------------------------------
> Arnold H. Rots Chandra X-ray Science Center
> Smithsonian Astrophysical Observatory tel: +1 617 496 7701 <tel:%2B1%20617%20496%207701>
> 60 Garden Street, MS 67 fax: +1 617 495 7356 <tel:%2B1%20617%20495%207356>
> Cambridge, MA 02138 arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>
> USA http://hea-www.harvard.edu/~arots/
> --------------------------------------------------------------------------------------------------------------____
>
> __ __
>
> On Sat, Oct 31, 2015 at 9:16 AM, Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>> wrote:____
>
> Hi Arnold____
>
> Thanks, will pass through pipeline.____
>
> ____
>
> To all:____
>
> I think we should allow 0..n for attributes, but with a different interpretation from its counterpart in composition
> relations and references.____
>
> It would imply that the value of the attribute is either *, or an array of length exactly n.____
>
> In relations the interpretation remains that one can have between 0 and n (inclusive) instances in the collection.____
>
> Makes sense?____
>
> Shall I update docs?____
>
> Cheers____
>
> Gerard____
>
> ____
>
> *From:*Arnold Rots [mailto:arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>]
> *Sent:* Saturday, October 31, 2015 8:50 AM
> *To:* Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>>
> *Cc:* Omar Laurino (olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>) <olaurino at head.cfa.harvard.edu
> <mailto:olaurino at head.cfa.harvard.edu>>; Mark Cresitello-Dittmar <mdittmar at cfa.harvard.edu
> <mailto:mdittmar at cfa.harvard.edu>>; msdemlei at ari.uni-heidelberg.de <mailto:msdemlei at ari.uni-heidelberg.de>____
>
>
> *Subject:* Re: vo-dml for cube____
>
> ____
>
> I have checked in my latest version, 2015-10-30.____
>
> - Arnold____
>
>
> ____
>
> -------------------------------------------------------------------------------------------------------------
> Arnold H. Rots Chandra X-ray Science Center
> Smithsonian Astrophysical Observatory tel: +1 617 496 7701 <tel:%2B1%20617%20496%207701>
> 60 Garden Street, MS 67 fax: +1 617 495 7356 <tel:%2B1%20617%20495%207356>
> Cambridge, MA 02138 arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>
> USA http://hea-www.harvard.edu/~arots/
> --------------------------------------------------------------------------------------------------------------____
>
> ____
>
> On Thu, Oct 29, 2015 at 8:46 AM, Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>> wrote:____
>
> Hi Arnold____
>
> (Cc-ing Markus)____
>
> It was an unforeseen advantage that VO-DML makes it so much easier identifying errors.____
>
> Could you check in your latest version of the Umodel file(s) as well?____
>
> In particular because I realize you are still using <<skosconcept>>, whereas my XSLT is now looking for
> <<semanticconcept>>.____
>
> Easy to fix by renaming stereotype. Also rename broadestSKOSConcept to topConcept. I realize I can do the
> transformation in XSLT, but better if the Umodel profile is as close to VO-DML as possible.____
>
> ____
>
> The aspect ratio of the PNG is bit hard to control in GraphViz. ____
>
> It should be seen on a screen where you can zoom in/out and move the diagram. Hard to print especially for unwieldy
> models ;) ____
>
> I find it nice to zoom out a lot to see where what colors reside and which areas have lots of associations.____
>
> ____
>
> Is there a document already describing the model? Are you going to add description elements in the UML so they can
> be picked up by the XSLT?____
>
> In particular, I’d be curious for a description of the contents of the frametransform package. And about how/where
> is it supposed to be used. ____
>
> ____
>
> Cheers____
>
> Gerard____
>
> ____
>
> *From:*Arnold Rots [mailto:arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>]
> *Sent:* Wednesday, October 28, 2015 6:37 PM
> *To:* Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>>____
>
>
> *Cc:* Omar Laurino (olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>)
> <olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>>; Mark Cresitello-Dittmar
> <mdittmar at cfa.harvard.edu <mailto:mdittmar at cfa.harvard.edu>>
> *Subject:* Re: vo-dml for cube____
>
> ____
>
> Thank you.____
>
> I had missed the error in coords - it's pretty hard to find in UModel.____
>
> Yes, four double-l typos____
>
> I replaced the subset on PixelFrame by a constraint.____
>
> I had made an attempt to see whether providing defaults for attributes like npix____
>
> would solve the illegal multiplicities, but that doesn't do the trick. I guess that____
>
> one is for you to figure out.____
>
> The question about the Qualifier was prompted by my wondering whether____
>
> that could/should be the mechanism to split on the basis of dimensionality____
>
> (instead of the naxes=naxes constraints).____
>
> In specialized I wasn't clear on where to use "=" and where "->".____
>
> I know you like those PNGs - I don't, because their ridiculous aspect____
>
> ratio makes them very hard to navigate and impossible to print.____
>
> Cheers,____
>
> - Arnold____
>
>
> ____
>
> -------------------------------------------------------------------------------------------------------------
> Arnold H. Rots Chandra X-ray Science Center
> Smithsonian Astrophysical Observatory tel: +1 617 496 7701 <tel:%2B1%20617%20496%207701>
> 60 Garden Street, MS 67 fax: +1 617 495 7356 <tel:%2B1%20617%20495%207356>
> Cambridge, MA 02138 arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>
> USA http://hea-www.harvard.edu/~arots/
> --------------------------------------------------------------------------------------------------------------____
>
> ____
>
> On Wed, Oct 28, 2015 at 8:42 AM, Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>> wrote:____
>
> Hi Arold____
>
> Pretty similar, you have now and then some typos (pixellType with double l). Attached the error report.____
>
> I had made the coords.SpatialCoord.erroran attribute, you still have it as reference for some reason.____
>
> You used to have a subsetted role on PixelFrame but no longer.____
>
> Thanks for your pointer to qualifier documentation. From description there this seems to be mainly aimed at
> implementations. If one would like to partition collections of associated objects for conceptual (rather than
> speed) reasons, you can (and I think “should”) always do that explicitly.____
>
> Cheers____
>
> Gerard____
>
> ____
>
> ____
>
> *From:*Arnold Rots [mailto:arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>]
> *Sent:* Wednesday, October 28, 2015 7:45 AM
> *To:* Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>>
> *Cc:* Omar Laurino (olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>)
> <olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>>; Mark Cresitello-Dittmar
> <mdittmar at cfa.harvard.edu <mailto:mdittmar at cfa.harvard.edu>>____
>
>
> *Subject:* Re: vo-dml for cube____
>
> ____
>
> Gerard,____
>
> Yes I got it and, for the sake of understanding it, produced my own version.____
>
> Can you check the attached XMI?____
>
> I am not sure I have the constraint syntax right in the Specialized package.____
>
> The qualifier question isn't really relevant anymore, but no, I didn't mean____
>
> ordered. I meant the use of a qualifier on an association, as in
> http://www.uml-diagrams.org/property.html____
>
> Cheers,____
>
> - Arnold____
>
>
> ____
>
> -------------------------------------------------------------------------------------------------------------
> Arnold H. Rots Chandra X-ray Science Center
> Smithsonian Astrophysical Observatory tel: +1 617 496 7701 <tel:%2B1%20617%20496%207701>
> 60 Garden Street, MS 67 fax: +1 617 495 7356 <tel:%2B1%20617%20495%207356>
> Cambridge, MA 02138 arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>
> USA http://hea-www.harvard.edu/~arots/
> --------------------------------------------------------------------------------------------------------------____
>
> ____
>
> On Wed, Oct 28, 2015 at 6:54 AM, Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>> wrote:____
>
> Hi Arnold____
>
> Yes, when looking at the model I understood your question better.____
>
> Have you seen my version with the possible fixes in place?____
>
> Btw, when you asked about qualifiers relations, did you think about things like “ordered”?____
>
> That particular one already exists (isOrdered), were there other ones you were thinking about?____
>
> Btw, In that case the ordering is supposed to be “implicitly” imposed by the order in which elements were
> added to the collection.____
>
> ____
>
> Cheers____
>
> Gerard____
>
> ____
>
> *From:*Arnold Rots [mailto:arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>]
> *Sent:* Tuesday, October 27, 2015 4:27 PM____
>
>
> *To:* Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>>
> *Cc:* Omar Laurino <olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>>; Mark
> Cresitello-Dittmar <mdittmar at cfa.harvard.edu <mailto:mdittmar at cfa.harvard.edu>>
> *Subject:* Re: vo-dml for cube____
>
> ____
>
> Ah, yes. That is what my earlier question was about.____
>
> Will try to fix.____
>
> - Arnold____
>
>
> ____
>
> -------------------------------------------------------------------------------------------------------------
> Arnold H. Rots Chandra X-ray Science Center
> Smithsonian Astrophysical Observatory tel: +1 617 496 7701 <tel:%2B1%20617%20496%207701>
> 60 Garden Street, MS 67 fax: +1 617 495 7356 <tel:%2B1%20617%20495%207356>
> Cambridge, MA 02138 arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>
> USA http://hea-www.harvard.edu/~arots/
> --------------------------------------------------------------------------------------------------------------____
>
> ____
>
> On Tue, Oct 27, 2015 at 9:43 AM, Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>> wrote:____
>
> Hi Arnold____
>
> Getting errors below after transforming to VO-DML and validating.____
>
> Most have to do with your use of an attribute inside a multiplicity constraint. Please create a real
> constraint about that in some way.____
>
> And there is the case where you define a constraint by susetting, in Xform3D for example. Use an
> ordinary constraint there.____
>
> I can make a suggested version and check it in once I’m at workCHeers____
>
> Gerard____
>
> ____
>
> ____
>
> XSD:____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:445:54:
> cvc-pattern-valid: Value '{multiplicity=naxes}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:445:54:
> cvc-type.3.1.3: The value '{multiplicity=naxes}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:772:53:
> cvc-pattern-valid: Value '{multiplicity=npix}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:772:53:
> cvc-type.3.1.3: The value '{multiplicity=npix}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:827:53:
> cvc-pattern-valid: Value '{multiplicity=npix}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:827:53:
> cvc-type.3.1.3: The value '{multiplicity=npix}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:882:53:
> cvc-pattern-valid: Value '{multiplicity=npix}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:882:53:
> cvc-type.3.1.3: The value '{multiplicity=npix}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:937:53:
> cvc-pattern-valid: Value '{multiplicity=npix}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:937:53:
> cvc-type.3.1.3: The value '{multiplicity=npix}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:992:53:
> cvc-pattern-valid: Value '{multiplicity=npix}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:992:53:
> cvc-type.3.1.3: The value '{multiplicity=npix}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1047:52:
> cvc-pattern-valid: Value '{muliplicity=npix}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1047:52:
> cvc-type.3.1.3: The value '{muliplicity=npix}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1102:52:
> cvc-pattern-valid: Value '(multiplicity=npix' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1102:52:
> cvc-type.3.1.3: The value '(multiplicity=npix' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1207:54:
> cvc-pattern-valid: Value '(multiplicity=order}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1207:54:
> cvc-type.3.1.3: The value '(multiplicity=order}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1320:55:
> cvc-pattern-valid: Value '{mulitiplicity=naxes}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1320:55:
> cvc-type.3.1.3: The value '{mulitiplicity=naxes}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1509:49:
> cvc-pattern-valid: Value '{Xform.naxes=1}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1509:49:
> cvc-type.3.1.3: The value '{Xform.naxes=1}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1550:49:
> cvc-pattern-valid: Value '{Xform.naxes=2}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1550:49:
> cvc-type.3.1.3: The value '{Xform.naxes=2}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1616:49:
> cvc-pattern-valid: Value '{Xform.naxes=3}' is not facet-valid with respect to pattern
> '[\w_-]+:[\w_\-/\./*]+' for type 'VODMLREF'.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml:1616:49:
> cvc-type.3.1.3: The value '{Xform.naxes=3}' of element 'vodml-ref' is not valid.____
>
> [_schemavalidate_]
> C:\workspaces\eclipse-luna-4.4.1\vo-urp-etc\vo-dml-g-vo\models\STC2\2015-10-25\STC2.vo-dml.xml is not a
> valid XML document____
>
> ____
>
> Schematron:____
>
> -------____
>
> error:____
>
> -------____
>
> _datatype_stc2:stctypes.MultiStruct of reference coords.SpatialCoord.error is not an object type but a
> 'dataType'____
>
> ____
>
> ____
>
> ____
>
> ____
>
> *From:*Arnold Rots [mailto:arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>]
> *Sent:* Tuesday, October 27, 2015 8:24 AM
> *To:* Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>>
> *Cc:* Omar Laurino <olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>>; Mark
> Cresitello-Dittmar <mdittmar at cfa.harvard.edu <mailto:mdittmar at cfa.harvard.edu>>____
>
> *Subject:* Re: vo-dml for cube____
>
> ____
>
> Gerard,____
>
> I tried to fix everything up the way it should be____
>
> and posted it under 2015-10-25.____
>
> Could you see whether that will rattle through your script?____
>
> I'm not sure I did get it all right.____
>
> I did split the transformations into atomic ones.____
>
> - Arnold____
>
>
> ____
>
> -------------------------------------------------------------------------------------------------------------
> Arnold H. Rots Chandra X-ray Science Center
> Smithsonian Astrophysical Observatory tel: +1 617 496 7701 <tel:%2B1%20617%20496%207701>
> 60 Garden Street, MS 67 fax: +1 617 495 7356
> <tel:%2B1%20617%20495%207356>
> Cambridge, MA 02138 arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>
> USA http://hea-www.harvard.edu/~arots/
> --------------------------------------------------------------------------------------------------------------____
>
> ____
>
> On Mon, Oct 26, 2015 at 11:52 PM, Arnold Rots <arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>>
> wrote:____
>
> Gerard, ____
>
> Do I understand correctly that your subsetting constraint is owned by the property to which it
> applies; while a vanilla constraint is owned by the object that contains the property to which it
> applies? ____
>
> Btw, does VO_DML allow qualifiers on relations? I don't think so, but should it?____
>
> - Arnold____
>
> On Oct 26, 2015 10:35 PM, "Gerard Lemson" <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>> wrote:____
>
> Hi Arnold____
>
> In UML (MD) I do subsetting still the same way, defining it on the Role (Attribute, Reference or
> Collection).____
>
> (Mark, can you actually do this in Modelio?).____
>
> I just now translate it to a SubsettingConstraint on the Type owning the Role rather than
> defining a separate Role for it. That is a special Constraint, that has a pointer to the
> subsetted Role. ____
>
> Has some nice features compared to the old model. Most important is that it solves the problem
> that Omar identified, that the redefinition would require a separate vo-dml id for the new Role.
> Also, the concept is really a constraint on allowable values of the structural element defined
> above.____
>
> Cheers____
>
> Gerard ____
>
> ____
>
> ____
>
> *From:*Arnold Rots [mailto:arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>]
> *Sent:* Monday, October 26, 2015 7:21 AM
> *To:* Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>>
> *Cc:* CresitelloDittmar, Mark <mdittmar at cfa.harvard.edu <mailto:mdittmar at cfa.harvard.edu>>; Omar
> Laurino (olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>)
> <olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>>
> *Subject:* Re: vo-dml for cube____
>
> ____
>
> Gerard,____
>
> How do you want constraints expressed:____
>
> just like any ordinary UML constraint, on the class,____
>
> or using your subsetting mechanism, in which case it can be associated directly with an
> attribute?____
>
> - Arnold____
>
>
> ____
>
> -------------------------------------------------------------------------------------------------------------
> Arnold H. Rots Chandra X-ray Science Center
> Smithsonian Astrophysical Observatory tel: +1 617 496 7701
> <tel:%2B1%20617%20496%207701>
> 60 Garden Street, MS 67 fax: +1 617 495 7356
> <tel:%2B1%20617%20495%207356>
> Cambridge, MA 02138 arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>
> USA http://hea-www.harvard.edu/~arots/
> --------------------------------------------------------------------------------------------------------------____
>
> ____
>
> On Sat, Oct 24, 2015 at 9:04 AM, Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>>
> wrote:____
>
> Hi Mark____
>
> ____
>
> Ok, I did not import ds as I did not know where the model was.____
>
> This can be updated if you point me to it. Do yu have a separate Modelio project for that?____
>
> Based on what I did for stc2 you can see how to proceed (I hope ;)____
>
> ____
>
> Stereotypes can be created on the root, with “Create stereotype”.____
>
> I had problems seeing where they end up.____
>
> In case you don’t know this already, on the project view window, in the top right there is a
> triangle.____
>
> Open up the menu and click Show Options > Show MDA model____
>
> This will show a new item, “LocalModule” that shows all the stereotypes under LocalProfile.____
>
> Right click a stereotype and use Create element > Tag type.____
>
> When now assigning the stereotype to an element, you can give values for that tag type.____
>
> Select the element, go to the “Elements” Tab. You should see the stereotype show up below
> UML and Modeler Module.____
>
> Clicking it will show the tags and you can add a value.____
>
> I am using this for example for modelimport to define the url and documentationURL.____
>
> Similarly for <<Model>> you can add author, version etc.____
>
> ____
>
> Let me know if yu can see all of this on the Cube-GL.zip version I checked in.____
>
> ____
>
> Are you in Australia already? Enjoy the meeting in any case and let me know if/when I may
> participate in a session.____
>
> ____
>
> Cheers____
>
> ____
>
> Gerard____
>
> ____
>
> ____
>
> *From:*CresitelloDittmar, Mark [mailto:mdittmar at cfa.harvard.edu
> <mailto:mdittmar at cfa.harvard.edu>]
> *Sent:* Saturday, October 24, 2015 2:38 AM
> *To:* Gerard Lemson <glemson1 at jhu.edu <mailto:glemson1 at jhu.edu>>
> *Cc:* Arnold Rots <arots at cfa.harvard.edu <mailto:arots at cfa.harvard.edu>>; Omar Laurino
> (olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>)
> <olaurino at head.cfa.harvard.edu <mailto:olaurino at head.cfa.harvard.edu>>
> *Subject:* Re: vo-dml for cube____
>
> ____
>
> that's great news.____
>
> I sent comments from the other thread, but yes.. stc and ds are imported to cube. dataset
> has it's own model/xmi file.____
>
> I'll want to see what you did with the stereotypes.. you were able to generate new ones?____
>
> The stc2 model in my cube doc is a little different than arnolds, but most closely related
> to the 2015-10-14 stuff.____
>
> In the end, all the stc2 content will be removed from dataset, and imported as you show.____
>
> Mark____
>
> ____
>
> ____
>
> ____
>
> ____
>
> ____
>
> ____
>
> __ __
>
>
>
>
> --
> Omar Laurino
> Smithsonian Astrophysical Observatory
> Harvard-Smithsonian Center for Astrophysics
> 100 Acorn Park Dr. R-377 MS-81
> 02140 Cambridge, MA
> (617) 495-7227
--
jesuischarlie
Laurent Michel
SSC XMM-Newton
Tél : +33 (0)3 68 85 24 37
Fax : +33 (0)3 )3 68 85 24 32
laurent.michel at astro.unistra.fr <mailto:laurent.michel at astro.unistra.fr>
Université de Strasbourg <http://www.unistra.fr>
Observatoire Astronomique
11 Rue de l'Université
F - 67200 Strasbourg
http://amwdb.u-strasbg.fr/HighEnergy/spip.php?rubrique34
More information about the dm
mailing list