<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Arnold, Gerard, Omar, Laurent, all,<br>
I also read the following emails in this thread but answer
this one, becaus eit is more appropriate to the use case I have in
mind.<br>
On 12/12/2015 15:37, Arnold Rots wrote:<br>
</div>
<blockquote
cite="mid:CAJXToE8DkXQn5HhEQJco=Sqwiv_=6X+feqGsiTdSUfWt-uQ63w@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Just to make things
clear for those in DM
who have not paid much
attention<br>
to VO-DML, let me as a
simple question.<br>
</div>
Below, I offer two very
simple models of a
Polynomial.<br>
</div>
They just provide the
coefficients, so for
argument's sake,<br>
</div>
let's assume they are
derived from an abstract
Transformation class<br>
</div>
that provides the independent
variable x and the dependent
variable y.<br>
<br>
</div>
Model 1 is disallowed by the
current VO-DML WD, Model 2 is
legal.<br>
</div>
My question: what is so wrong with
Model 1 that it is disallowed<br>
</div>
and why is Model 2 a so much better
solution?<br>
</div>
<div>To me they look pretty equivalent
and Model 1 is simpler.<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
I definitely agree with Arnold there.<br>
<br>
One important use case for STC is pixel/world coordinate
transformation. STC can provide a unified view of this, which
unfortunately was missed by astronomical community with WCS
standard. As you know the non linear spatial distortions have been
rendered have been renderered by plenty of WCS dialects (PV
parameters with TPV projection, TAN-SIP or SIN-SIP, SCAMP PV
parameters, etc....).<br>
It would be nice to get an harmonization of this and Arnold and Mark
Cresitello have been working on this.<br>
<br>
Specifically I have data access issues in mind for future version of
DAL protocols<br>
<br>
Polynomial description is a basic part of the Transformation
encoding. <br>
I think it would be very strange to describe this by a collection
of coefficient objects. We definitely need a uniform view of "any
order polynomial" and manage them all the same way.<br>
<br>
For this reason The VO-DML datamodel description should allow
datatypes as flexibel arrays.<br>
<br>
Cheers<br>
François<br>
<br>
PS : I am not considering here any kind of serialisation of these
VO-DML decscriptions (Object relational maaping, VOTABLE Mapping,
specific-stc2-xml-schema xml documents, json, etc... ). this is
another story but the initial VO-DML description will constraint the
solution. <br>
<blockquote
cite="mid:CAJXToE8DkXQn5HhEQJco=Sqwiv_=6X+feqGsiTdSUfWt-uQ63w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Cheers,<br>
<br>
</div>
<div> - Arnold<br>
</div>
<div><br>
<br>
</div>
Model 1<br>
-------<br>
</div>
Class Polynomial<br>
</div>
attribute order<br>
</div>
type = nonnegativeInteger<br>
</div>
multiplicity = 1<br>
</div>
attribute coeff<br>
</div>
type = real<br>
</div>
multiplicity = order+1<br>
</div>
isOrdered = true<br>
<br>
</div>
This evaluates y as:<br>
</div>
y = sum (coeff[i] * x^i) where i=0..order<br>
<br>
<br>
Model 2<br>
-------<br>
Class Coefficient<br>
</div>
attribute value<br>
</div>
type = real<br>
</div>
multiplicity = 1<br>
<div>
<div>
<div>Class Polynomial<br>
attribute order<br>
type = nonnegativeInteger<br>
multiplicity = 1<br>
collection coeff<br>
type = Coefficient<br>
multiplicity = order+1<br>
isOrdered = true<br>
<br>
This evaluates y as:<br>
y = sum (coeff[i].value * x^i) where i=0..order<br>
<br>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div>
<div class="gmail_signature">
<div dir="ltr">-------------------------------------------------------------------------------------------------------------<br>
Arnold H. Rots
Chandra X-ray Science Center<br>
Smithsonian Astrophysical Observatory
tel: +1 617 496 7701<br>
60 Garden Street, MS 67
fax: +1 617 495 7356<br>
Cambridge, MA 02138
<a moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a><br>
USA <a
moz-do-not-send="true"
href="http://hea-www.harvard.edu/%7Earots/"
target="_blank">http://hea-www.harvard.edu/~arots/</a><br>
--------------------------------------------------------------------------------------------------------------<br>
<br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Fri, Dec 11, 2015 at 10:32 AM,
Arnold Rots <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Yes, what I am proposing
is an extension of what was
agreed regarding the
[0..]<literal>
specification.<br>
<br>
</div>
I think requiring that the
length of an array of values
that is an attribute of an
Objecttype (class) or Datatype
(structure) has to be fixed by
the data model is too
restrictive.<br>
</div>
There are plenty of use cases
where that length can only
sensibly be set when
instantiating the Object or Data
item.<br>
</div>
Examples are:<br>
</div>
- The array of coefficients in a
polynomial class; its length should
be set by the order of the
polynomial expression, which is a
legitimate parameter for such an
Objecttype<br>
</div>
- The pixel data values in a spectrum<br>
</div>
- The coordinate values along an
enumerated coordinate axis<br>
</div>
- The number of samples in a time series<br>
</div>
Just think how often the length of an array
is left variable in your code and set at
runtime.<br>
<br>
</div>
VO-DML in its current specification requires
that in such situations the array not be
modeled as an array of data values (either
primitive or compound - like structures), but
as lists of objects - the instantiations of
classes.<br>
</div>
My sense is that that is overkill and results in
unnecessary overhead. There is no good reason to
have to model a simple coefficient as a class in
order to be able to use it in a polynomial class
that has its order as a attribute.<br>
<br>
</div>
I think allowing multiplicity of attributes to be
variable, but requiring it to be explicitly
specified by a nonnegative integer attribute is an
acceptable compromise for this issue.<br>
<br>
</div>
For me, the matter is that I need to have this issue
resolved before I can proceed with the remainder of
the STC2 development; it has become a major
stumbling block requiring changes that I would
prefer not to have to make.<br>
</div>
And, at the same time, I believe that this is an issue
that will trip up future VO-DML developers as well, so
I would rather see it changed right now.<br>
<br>
</div>
Cheers,<br>
<br>
</div>
- Arnold<br>
</div>
<div class="gmail_extra"><span class=""><br>
<div>
<div>
<div dir="ltr">-------------------------------------------------------------------------------------------------------------<br>
Arnold H. Rots
Chandra X-ray Science Center<br>
Smithsonian Astrophysical
Observatory tel: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20496%207701"
value="+16174967701" target="_blank">+1 617 496
7701</a><br>
60 Garden Street, MS 67
fax: <a moz-do-not-send="true"
href="tel:%2B1%20617%20495%207356"
value="+16174957356" target="_blank">+1 617 495
7356</a><br>
Cambridge, MA 02138
<a moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu"
target="_blank">arots@cfa.harvard.edu</a><br>
USA
<a moz-do-not-send="true"
href="http://hea-www.harvard.edu/%7Earots/"
target="_blank">http://hea-www.harvard.edu/~arots/</a><br>
--------------------------------------------------------------------------------------------------------------<br>
<br>
</div>
</div>
</div>
<br>
</span>
<div>
<div class="h5">
<div class="gmail_quote">On Fri, Dec 11, 2015 at 7:58
AM, Gerard Lemson <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote">
<div lang="EN-US">
<div>
<p class="MsoNormal"><span>HI (adding dm@ivoa
in the Cc)</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Allowing 0..n,
implying EITHER 0 OR exactly n with n a
literal is same as discussed before (and
below in email trail).</span></p>
<p class="MsoNormal"><span>The current doc
does not include this yet, I have had no
other opinions about this but yours, but I
think it is reasonable.</span></p>
<p class="MsoNormal"><span>I thought I had
already updated the doc, but apparently
not yet.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Allowing n to be an
integer attribute with multiplicity 1 I am
still strongly against.</span></p>
<p class="MsoNormal"><span>For example, what
if, after initializing the 0..n attribute,
you change the value of n?</span></p>
<p class="MsoNormal"><span>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.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>I am also still
doubtful of the use cases that would seem
to require this.</span></p>
<p class="MsoNormal"><span>The cases where I
have seen you use this feature in STC can
and imho SHOULD be designed differently.
</span></p>
<p class="MsoNormal"><span>I think the dm
group MUST start looking seriously at STC
before its presumed requirements are used
to influence the language.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Any comments from
the others.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Cheers</span></p>
<p class="MsoNormal"><span>Gerard</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="15191abd916bf11e_151911ee10cadf7c__MailEndCompose"><span> </span></a></p>
<div>
<div>
<div>
<p class="MsoNormal"><b><span>From:</span></b><span>
Arnold Rots [mailto:<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu"
target="_blank">arots@cfa.harvard.edu</a>]
<br>
<b>Sent:</b> Thursday, December 10,
2015 5:23 PM<br>
<b>To:</b> Gerard Lemson <<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu"
target="_blank">glemson1@jhu.edu</a>><br>
<b>Cc:</b> CresitelloDittmar, Mark
<<a moz-do-not-send="true"
href="mailto:mdittmar@cfa.harvard.edu"
target="_blank">mdittmar@cfa.harvard.edu</a>>;
Omar Laurino (<a
moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu"
target="_blank">olaurino@head.cfa.harvard.edu</a>)
<<a moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu"
target="_blank">olaurino@head.cfa.harvard.edu</a>>;
<a moz-do-not-send="true"
href="mailto:msdemlei@ari.uni-heidelberg.de"
target="_blank">msdemlei@ari.uni-heidelberg.de</a></span></p>
<div>
<div><br>
<b>Subject:</b> Re: vo-dml for cube</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Would it be
acceptable extend this
slightly:</p>
</div>
<p class="MsoNormal">Multiplicity
must be "[0..]n", meaning that
the multiplicity is either 0
(but only if "0.." is present)
or n,</p>
</div>
<p class="MsoNormal">and where n is
either a numeric literal or an
existing nonnegative integer
attribute with multiplicity 1.<br>
<br>
</p>
</div>
<div>
<p class="MsoNormal">Cheers,</p>
</div>
<div>
<p class="MsoNormal"> - Arnold</p>
</div>
</div>
<div>
<p class="MsoNormal"><br>
</p>
<div>
<div>
<div>
<p class="MsoNormal">-------------------------------------------------------------------------------------------------------------<br>
Arnold H.
Rots
Chandra X-ray
Science Center<br>
Smithsonian Astrophysical
Observatory
tel: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20496%207701"
value="+16174967701"
target="_blank">+1 617 496
7701</a><br>
60 Garden Street, MS
67
fax: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20495%207356"
value="+16174957356"
target="_blank">+1 617 495
7356</a><br>
Cambridge, MA
02138
<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu"
target="_blank">
arots@cfa.harvard.edu</a><br>
USA
<a
moz-do-not-send="true"
href="http://hea-www.harvard.edu/%7Earots/"
target="_blank">
http://hea-www.harvard.edu/~arots/</a><br>
--------------------------------------------------------------------------------------------------------------</p>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On Sat, Oct 31,
2015 at 9:16 AM, Gerard Lemson
<<a moz-do-not-send="true"
href="mailto:glemson1@jhu.edu"
target="_blank">glemson1@jhu.edu</a>>
wrote:</p>
<blockquote>
<div>
<div>
<p class="MsoNormal"><span>Hi
Arnold</span></p>
<p class="MsoNormal"><span>Thanks,
will pass through
pipeline.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>To
all:</span></p>
<p class="MsoNormal"><span>I
think we should allow 0..n
for attributes, but with a
different interpretation
from its counterpart in
composition relations and
references.</span></p>
<p class="MsoNormal"><span>It
would imply that the value
of the attribute is either
*, or an array of length
exactly n.</span></p>
<p class="MsoNormal"><span>In
relations the
interpretation remains
that one can have between
0 and n (inclusive)
instances in the
collection.</span></p>
<p class="MsoNormal"><span>Makes
sense?</span></p>
<p class="MsoNormal"><span>Shall
I update docs?</span></p>
<p class="MsoNormal"><span>Cheers</span></p>
<p class="MsoNormal"><span>Gerard</span></p>
<p class="MsoNormal"><a
moz-do-not-send="true"
name="15191abd916bf11e_151911ee10cadf7c_150be0b16d64e98e__MailEndCompose"><span> </span></a></p>
<div>
<div>
<div>
<p class="MsoNormal"><b><span>From:</span></b><span>
Arnold Rots [mailto:<a
moz-do-not-send="true" href="mailto:arots@cfa.harvard.edu"
target="_blank">arots@cfa.harvard.edu</a>]
<br>
<b>Sent:</b>
Saturday, October
31, 2015 8:50 AM<br>
<b>To:</b> Gerard
Lemson <<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>><br>
<b>Cc:</b> Omar
Laurino (<a
moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu" target="_blank">olaurino@head.cfa.harvard.edu</a>)
<<a
moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu" target="_blank">olaurino@head.cfa.harvard.edu</a>>;
Mark
Cresitello-Dittmar
<<a
moz-do-not-send="true"
href="mailto:mdittmar@cfa.harvard.edu" target="_blank">mdittmar@cfa.harvard.edu</a>>;
<a
moz-do-not-send="true"
href="mailto:msdemlei@ari.uni-heidelberg.de" target="_blank">msdemlei@ari.uni-heidelberg.de</a></span></p>
<div>
<div>
<p class="MsoNormal"><br>
<b>Subject:</b>
Re: vo-dml for
cube</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">I
have checked in my
latest version,
2015-10-30.</p>
</div>
<p class="MsoNormal">
- Arnold</p>
</div>
<div>
<p class="MsoNormal"><br>
</p>
<div>
<div>
<div>
<p
class="MsoNormal">-------------------------------------------------------------------------------------------------------------<br>
Arnold H.
Rots
Chandra X-ray
Science Center<br>
Smithsonian
Astrophysical
Observatory
tel: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20496%207701" target="_blank">
+1 617 496
7701</a><br>
60 Garden
Street, MS
67
fax: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20495%207356" target="_blank">
+1 617 495
7356</a><br>
Cambridge, MA
02138
<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">
arots@cfa.harvard.edu</a><br>
USA
<a
moz-do-not-send="true"
href="http://hea-www.harvard.edu/%7Earots/" target="_blank">
http://hea-www.harvard.edu/~arots/</a><br>
--------------------------------------------------------------------------------------------------------------</p>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On
Thu, Oct 29, 2015
at 8:46 AM, Gerard
Lemson <<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>>
wrote:</p>
<blockquote>
<div>
<div>
<p
class="MsoNormal"><span>Hi
Arnold</span></p>
<p
class="MsoNormal"><span>(Cc-ing
Markus)</span></p>
<p
class="MsoNormal"><span>It
was an
unforeseen
advantage that
VO-DML makes
it so much
easier
identifying
errors.</span></p>
<p
class="MsoNormal"><span>Could
you check in
your latest
version of the
Umodel file(s)
as well?</span></p>
<p
class="MsoNormal"><span>In
particular
because I
realize you
are still
using
<<skosconcept>>,
whereas my
XSLT is now
looking for
<<semanticconcept>>.</span></p>
<p
class="MsoNormal"><span>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.</span><a
moz-do-not-send="true"
name="15191abd916bf11e_151911ee10cadf7c_150be0b16d64e98e_150b3a26d1839eb7__MailE"></a></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>The
aspect ratio
of the PNG is
bit hard to
control in
GraphViz.
</span></p>
<p
class="MsoNormal"><span>It
should be seen
on a screen
where you can
zoom in/out
and move the
diagram. Hard
to print
especially for
unwieldy
models ;) </span></p>
<p
class="MsoNormal"><span>I
find it nice
to zoom out a
lot to see
where what
colors reside
and which
areas have
lots of
associations.</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>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?</span></p>
<p
class="MsoNormal"><span>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. </span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>Cheers</span></p>
<p
class="MsoNormal"><span>Gerard</span></p>
<p
class="MsoNormal"><span> </span></p>
<div>
<div>
<div>
<p
class="MsoNormal"><b><span>From:</span></b><span>
Arnold Rots
[mailto:<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a>]
<br>
<b>Sent:</b>
Wednesday,
October 28,
2015 6:37 PM<br>
<b>To:</b>
Gerard Lemson
<<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>></span></p>
<div>
<div>
<p
class="MsoNormal"><br>
<b>Cc:</b>
Omar Laurino (<a
moz-do-not-send="true" href="mailto:olaurino@head.cfa.harvard.edu"
target="_blank">olaurino@head.cfa.harvard.edu</a>)
<<a
moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu" target="_blank">olaurino@head.cfa.harvard.edu</a>>;
Mark
Cresitello-Dittmar
<<a
moz-do-not-send="true"
href="mailto:mdittmar@cfa.harvard.edu" target="_blank">mdittmar@cfa.harvard.edu</a>><br>
<b>Subject:</b>
Re: vo-dml for
cube</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p
class="MsoNormal"> </p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p
class="MsoNormal">Thank
you.</p>
</div>
<p
class="MsoNormal">I
had missed the
error in
coords - it's
pretty hard to
find in
UModel.</p>
</div>
<p
class="MsoNormal">Yes,
four double-l
typos</p>
</div>
<p
class="MsoNormal">I
replaced the
subset on
PixelFrame by
a constraint.</p>
</div>
<p
class="MsoNormal">I
had made an
attempt to see
whether
providing
defaults for
attributes
like npix</p>
</div>
<p
class="MsoNormal">would
solve the
illegal
multiplicities,
but that
doesn't do the
trick. I guess
that</p>
</div>
<p
class="MsoNormal">one
is for you to
figure out.</p>
</div>
<p
class="MsoNormal">The
question about
the Qualifier
was prompted
by my
wondering
whether</p>
</div>
<p
class="MsoNormal">that
could/should
be the
mechanism to
split on the
basis of
dimensionality</p>
</div>
<p
class="MsoNormal">(instead
of the
naxes=naxes
constraints).</p>
</div>
<p
class="MsoNormal">In
specialized I
wasn't clear
on where to
use "=" and
where "->".</p>
</div>
<p
class="MsoNormal">I
know you like
those PNGs - I
don't, because
their
ridiculous
aspect</p>
</div>
<p
class="MsoNormal">ratio
makes them
very hard to
navigate and
impossible to
print.</p>
</div>
<p
class="MsoNormal">Cheers,</p>
</div>
<p
class="MsoNormal">
- Arnold</p>
</div>
<div>
<p
class="MsoNormal"><br>
</p>
<div>
<div>
<div>
<p
class="MsoNormal">-------------------------------------------------------------------------------------------------------------<br>
Arnold H.
Rots
Chandra X-ray
Science Center<br>
Smithsonian
Astrophysical
Observatory
tel: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20496%207701" target="_blank">
+1 617 496
7701</a><br>
60 Garden
Street, MS
67
fax: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20495%207356" target="_blank">
+1 617 495
7356</a><br>
Cambridge, MA
02138
<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">
arots@cfa.harvard.edu</a><br>
USA
<a
moz-do-not-send="true"
href="http://hea-www.harvard.edu/%7Earots/" target="_blank">
http://hea-www.harvard.edu/~arots/</a><br>
--------------------------------------------------------------------------------------------------------------</p>
</div>
</div>
</div>
<p
class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">On
Wed, Oct 28,
2015 at 8:42
AM, Gerard
Lemson <<a
moz-do-not-send="true" href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>>
wrote:</p>
<blockquote>
<div>
<div>
<p
class="MsoNormal"><span>Hi
Arold</span></p>
<p
class="MsoNormal"><span>Pretty
similar, you
have now and
then some
typos
(pixellType
with double
l). Attached
the error
report.</span></p>
<p
class="MsoNormal">
<span>I had
made the
</span><span>coords.SpatialCoord.error</span><span>
an attribute,
you still have
it as
reference for
some reason.</span></p>
<p
class="MsoNormal">
<span>You used
to have a
subsetted role
on PixelFrame
but no longer.</span></p>
<p
class="MsoNormal">
<span>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.</span></p>
<p
class="MsoNormal"><span>Cheers</span></p>
<p
class="MsoNormal"><span>Gerard</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span> </span></p>
<div>
<div>
<p
class="MsoNormal"><b><span>From:</span></b><span>
Arnold Rots
[mailto:<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a>]
<br>
<b>Sent:</b>
Wednesday,
October 28,
2015 7:45 AM<br>
<b>To:</b>
Gerard Lemson
<<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>><br>
<b>Cc:</b>
Omar Laurino (<a
moz-do-not-send="true" href="mailto:olaurino@head.cfa.harvard.edu"
target="_blank">olaurino@head.cfa.harvard.edu</a>)
<<a
moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu" target="_blank">olaurino@head.cfa.harvard.edu</a>>;
Mark
Cresitello-Dittmar
<<a
moz-do-not-send="true"
href="mailto:mdittmar@cfa.harvard.edu" target="_blank">mdittmar@cfa.harvard.edu</a>></span></p>
<div>
<div>
<p
class="MsoNormal"><br>
<b>Subject:</b>
Re: vo-dml for
cube</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p
class="MsoNormal"> </p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p
class="MsoNormal">Gerard,</p>
</div>
<p
class="MsoNormal">Yes
I got it and,
for the sake
of
understanding
it, produced
my own
version.</p>
</div>
<p
class="MsoNormal">Can
you check the
attached XMI?</p>
</div>
<p
class="MsoNormal">I
am not sure I
have the
constraint
syntax right
in the
Specialized
package.</p>
</div>
<p
class="MsoNormal">The
qualifier
question isn't
really
relevant
anymore, but
no, I didn't
mean</p>
</div>
<p
class="MsoNormal">ordered.
I meant the
use of a
qualifier on
an
association,
as in<br>
<a
moz-do-not-send="true"
href="http://www.uml-diagrams.org/property.html" target="_blank">http://www.uml-diagrams.org/property.html</a></p>
</div>
<p
class="MsoNormal">Cheers,</p>
</div>
<p
class="MsoNormal">
- Arnold</p>
</div>
<p
class="MsoNormal"><br>
</p>
<div>
<div>
<div>
<p
class="MsoNormal">-------------------------------------------------------------------------------------------------------------<br>
Arnold H.
Rots
Chandra X-ray
Science Center<br>
Smithsonian
Astrophysical
Observatory
tel: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20496%207701" target="_blank">
+1 617 496
7701</a><br>
60 Garden
Street, MS
67
fax: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20495%207356" target="_blank">
+1 617 495
7356</a><br>
Cambridge, MA
02138
<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">
arots@cfa.harvard.edu</a><br>
USA
<a
moz-do-not-send="true"
href="http://hea-www.harvard.edu/%7Earots/" target="_blank">
http://hea-www.harvard.edu/~arots/</a><br>
--------------------------------------------------------------------------------------------------------------</p>
</div>
</div>
</div>
<p
class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">On
Wed, Oct 28,
2015 at 6:54
AM, Gerard
Lemson <<a
moz-do-not-send="true" href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>>
wrote:</p>
<blockquote>
<div>
<div>
<p
class="MsoNormal"><span>Hi
Arnold</span></p>
<p
class="MsoNormal"><span>Yes,
when looking
at the model I
understood
your question
better.</span></p>
<p
class="MsoNormal"><span>Have
you seen my
version with
the possible
fixes in
place?</span></p>
<p
class="MsoNormal"><span>Btw,
when you asked
about
qualifiers
relations, did
you think
about things
like
“ordered”?</span></p>
<p
class="MsoNormal"><span>That
particular one
already exists
(isOrdered),
were there
other ones you
were thinking
about?</span></p>
<p
class="MsoNormal"><span>Btw,
In that case
the ordering
is supposed to
be
“implicitly”
imposed by the
order in which
elements were
added to the
collection.</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>Cheers</span></p>
<p
class="MsoNormal"><span>Gerard</span></p>
<p
class="MsoNormal"><span> </span></p>
<div>
<div>
<div>
<p
class="MsoNormal"><b><span>From:</span></b><span>
Arnold Rots
[mailto:<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a>]
<br>
<b>Sent:</b>
Tuesday,
October 27,
2015 4:27 PM</span></p>
<div>
<div>
<p
class="MsoNormal"><br>
<b>To:</b>
Gerard Lemson
<<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>><br>
<b>Cc:</b>
Omar Laurino
<<a
moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu" target="_blank">olaurino@head.cfa.harvard.edu</a>>;
Mark
Cresitello-Dittmar
<<a
moz-do-not-send="true"
href="mailto:mdittmar@cfa.harvard.edu" target="_blank">mdittmar@cfa.harvard.edu</a>><br>
<b>Subject:</b>
Re: vo-dml for
cube</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p
class="MsoNormal"> </p>
<div>
<div>
<div>
<p
class="MsoNormal">Ah,
yes. That is
what my
earlier
question was
about.</p>
</div>
<p
class="MsoNormal">Will
try to fix.</p>
</div>
<p
class="MsoNormal">
- Arnold</p>
</div>
<div>
<p
class="MsoNormal"><br>
</p>
<div>
<div>
<div>
<p
class="MsoNormal">-------------------------------------------------------------------------------------------------------------<br>
Arnold H.
Rots
Chandra X-ray
Science Center<br>
Smithsonian
Astrophysical
Observatory
tel: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20496%207701" target="_blank">
+1 617 496
7701</a><br>
60 Garden
Street, MS
67
fax: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20495%207356" target="_blank">
+1 617 495
7356</a><br>
Cambridge, MA
02138
<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">
arots@cfa.harvard.edu</a><br>
USA
<a
moz-do-not-send="true"
href="http://hea-www.harvard.edu/%7Earots/" target="_blank">
http://hea-www.harvard.edu/~arots/</a><br>
--------------------------------------------------------------------------------------------------------------</p>
</div>
</div>
</div>
<p
class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">On
Tue, Oct 27,
2015 at 9:43
AM, Gerard
Lemson <<a
moz-do-not-send="true" href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>>
wrote:</p>
<blockquote>
<div>
<div>
<p
class="MsoNormal"><span>Hi
Arnold</span></p>
<p
class="MsoNormal"><span>Getting
errors below
after
transforming
to VO-DML and
validating.</span></p>
<p
class="MsoNormal"><span>Most
have to do
with your use
of an
attribute
inside a
multiplicity
constraint.
Please create
a real
constraint
about that in
some way.</span></p>
<p
class="MsoNormal"><span>And
there is the
case where you
define a
constraint by
susetting, in
Xform3D for
example. Use
an ordinary
constraint
there.</span></p>
<p
class="MsoNormal"><span>I
can make a
suggested
version and
check it in
once I’m at
workCHeers</span></p>
<p
class="MsoNormal"><span>Gerard</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>XSD:</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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'.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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.</span></p>
<p
class="MsoNormal">
<span>[</span><u><span>schemavalidate</span></u><span>]
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</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>Schematron:</span></p>
<p
class="MsoNormal">
<span>-------</span></p>
<p
class="MsoNormal">
<span>error:</span></p>
<p
class="MsoNormal">
<span>-------</span></p>
<p
class="MsoNormal">
<u><span>datatype</span></u><span>
stc2:stctypes.MultiStruct
of reference
coords.SpatialCoord.error
is not an
object type
but a
'dataType'</span></p>
<p
class="MsoNormal"><span>
</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span> </span></p>
<div>
<div>
<div>
<p
class="MsoNormal"><b><span>From:</span></b><span>
Arnold Rots
[mailto:<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a>]
<br>
<b>Sent:</b>
Tuesday,
October 27,
2015 8:24 AM<br>
<b>To:</b>
Gerard Lemson
<<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>><br>
<b>Cc:</b>
Omar Laurino
<<a
moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu" target="_blank">olaurino@head.cfa.harvard.edu</a>>;
Mark
Cresitello-Dittmar
<<a
moz-do-not-send="true"
href="mailto:mdittmar@cfa.harvard.edu" target="_blank">mdittmar@cfa.harvard.edu</a>></span></p>
<div>
<div>
<p
class="MsoNormal"><b>Subject:</b>
Re: vo-dml for
cube</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p
class="MsoNormal"> </p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p
class="MsoNormal">Gerard,</p>
</div>
<p
class="MsoNormal">I
tried to fix
everything up
the way it
should be</p>
</div>
<p
class="MsoNormal">and
posted it
under
2015-10-25.</p>
</div>
<p
class="MsoNormal">Could
you see
whether that
will rattle
through your
script?</p>
</div>
<p
class="MsoNormal">I'm
not sure I did
get it all
right.</p>
</div>
<p
class="MsoNormal">I
did split the
transformations
into atomic
ones.</p>
</div>
<p
class="MsoNormal">
- Arnold</p>
</div>
<div>
<p
class="MsoNormal"><br>
</p>
<div>
<div>
<div>
<p
class="MsoNormal">-------------------------------------------------------------------------------------------------------------<br>
Arnold H.
Rots
Chandra X-ray
Science Center<br>
Smithsonian
Astrophysical
Observatory
tel: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20496%207701" target="_blank">
+1 617 496
7701</a><br>
60 Garden
Street, MS
67
fax: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20495%207356" target="_blank">
+1 617 495
7356</a><br>
Cambridge, MA
02138
<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">
arots@cfa.harvard.edu</a><br>
USA
<a
moz-do-not-send="true"
href="http://hea-www.harvard.edu/%7Earots/" target="_blank">
http://hea-www.harvard.edu/~arots/</a><br>
--------------------------------------------------------------------------------------------------------------</p>
</div>
</div>
</div>
<p
class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">On
Mon, Oct 26,
2015 at 11:52
PM, Arnold
Rots <<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a>>
wrote:</p>
<blockquote>
<p>Gerard, </p>
<p>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?
</p>
<p>Btw, does
VO_DML allow
qualifiers on
relations? I
don't think
so, but
should it?</p>
<p><span> -
Arnold</span></p>
<div>
<div>
<div>
<p
class="MsoNormal">On
Oct 26, 2015
10:35 PM,
"Gerard
Lemson" <<a
moz-do-not-send="true" href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>>
wrote:</p>
<blockquote>
<div>
<div>
<p
class="MsoNormal"><span>Hi
Arnold</span></p>
<p
class="MsoNormal"><span>In
UML (MD) I do
subsetting
still the same
way, defining
it on the Role
(Attribute,
Reference or
Collection).</span></p>
<p
class="MsoNormal"><span>(Mark,
can you
actually do
this in
Modelio?).</span></p>
<p
class="MsoNormal"><span>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.
</span></p>
<p
class="MsoNormal"><span>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.</span></p>
<p
class="MsoNormal"><span>Cheers</span></p>
<p
class="MsoNormal"><span>Gerard
</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span> </span></p>
<div>
<div>
<div>
<p
class="MsoNormal"><b><span>From:</span></b><span>
Arnold Rots
[mailto:<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a>]
<br>
<b>Sent:</b>
Monday,
October 26,
2015 7:21 AM<br>
<b>To:</b>
Gerard Lemson
<<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>><br>
<b>Cc:</b>
CresitelloDittmar,
Mark <<a
moz-do-not-send="true"
href="mailto:mdittmar@cfa.harvard.edu" target="_blank">mdittmar@cfa.harvard.edu</a>>;
Omar Laurino (<a
moz-do-not-send="true" href="mailto:olaurino@head.cfa.harvard.edu"
target="_blank">olaurino@head.cfa.harvard.edu</a>)
<<a
moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu" target="_blank">olaurino@head.cfa.harvard.edu</a>><br>
<b>Subject:</b>
Re: vo-dml for
cube</span></p>
</div>
</div>
<p
class="MsoNormal"> </p>
<div>
<div>
<div>
<div>
<div>
<p
class="MsoNormal">Gerard,</p>
</div>
<p
class="MsoNormal">How
do you want
constraints
expressed:</p>
</div>
<p
class="MsoNormal">just
like any
ordinary UML
constraint, on
the class,</p>
</div>
<p
class="MsoNormal">or
using your
subsetting
mechanism, in
which case it
can be
associated
directly with
an attribute?</p>
</div>
<p
class="MsoNormal">
- Arnold</p>
</div>
<div>
<p
class="MsoNormal"><br>
</p>
<div>
<div>
<div>
<p
class="MsoNormal">-------------------------------------------------------------------------------------------------------------<br>
Arnold H.
Rots
Chandra X-ray
Science Center<br>
Smithsonian
Astrophysical
Observatory
tel: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20496%207701" target="_blank">
+1 617 496
7701</a><br>
60 Garden
Street, MS
67
fax: <a
moz-do-not-send="true"
href="tel:%2B1%20617%20495%207356" target="_blank">
+1 617 495
7356</a><br>
Cambridge, MA
02138
<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">
arots@cfa.harvard.edu</a><br>
USA
<a
moz-do-not-send="true"
href="http://hea-www.harvard.edu/%7Earots/" target="_blank">
http://hea-www.harvard.edu/~arots/</a><br>
--------------------------------------------------------------------------------------------------------------</p>
</div>
</div>
</div>
<p
class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">On
Sat, Oct 24,
2015 at 9:04
AM, Gerard
Lemson <<a
moz-do-not-send="true" href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>>
wrote:</p>
<blockquote>
<div>
<div>
<p
class="MsoNormal"><span>Hi
Mark</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>Ok,
I did not
import ds as I
did not know
where the
model was.</span></p>
<p
class="MsoNormal"><span>This
can be updated
if you point
me to it. Do
yu have a
separate
Modelio
project for
that?</span></p>
<p
class="MsoNormal"><span>Based
on what I did
for stc2 you
can see how to
proceed (I
hope ;)</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>Stereotypes
can be created
on the root,
with “Create
stereotype”.</span></p>
<p
class="MsoNormal"><span>I
had problems
seeing where
they end up.</span></p>
<p
class="MsoNormal"><span>In
case you don’t
know this
already, on
the project
view window,
in the top
right there is
a triangle.</span></p>
<p
class="MsoNormal"><span>Open
up the menu
and click Show
Options >
Show MDA model</span></p>
<p
class="MsoNormal"><span>This
will show a
new item,
“LocalModule”
that shows all
the
stereotypes
under
LocalProfile.</span></p>
<p
class="MsoNormal"><span>Right
click a
stereotype and
use Create
element >
Tag type.</span></p>
<p
class="MsoNormal"><span>When
now assigning
the stereotype
to an element,
you can give
values for
that tag type.</span></p>
<p
class="MsoNormal"><span>Select
the element,
go to the
“Elements”
Tab. You
should see the
stereotype
show up below
UML and
Modeler
Module.</span></p>
<p
class="MsoNormal"><span>Clicking
it will show
the tags and
you can add a
value.</span></p>
<p
class="MsoNormal"><span>I
am using this
for example
for
modelimport to
define the url
and
documentationURL.</span></p>
<p
class="MsoNormal"><span>Similarly
for
<<Model>>
you can add
author,
version etc.</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>Let
me know if yu
can see all
of this on the
Cube-GL.zip
version I
checked in.</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>Are
you in
Australia
already? Enjoy
the meeting in
any case and
let me know
if/when I may
participate in
a session.</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>Cheers</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><span>Gerard</span></p>
<p
class="MsoNormal"><span> </span></p>
<p
class="MsoNormal"><a
moz-do-not-send="true"
name="15191abd916bf11e_151911ee10cadf7c_150be0b16d64e98e_150b3a26d1839eb7_150ae7"><span> </span></a></p>
<div>
<div>
<div>
<p
class="MsoNormal"><b><span>From:</span></b><span>
CresitelloDittmar,
Mark [mailto:<a
moz-do-not-send="true" href="mailto:mdittmar@cfa.harvard.edu"
target="_blank">mdittmar@cfa.harvard.edu</a>]
<br>
<b>Sent:</b>
Saturday,
October 24,
2015 2:38 AM<br>
<b>To:</b>
Gerard Lemson
<<a
moz-do-not-send="true"
href="mailto:glemson1@jhu.edu" target="_blank">glemson1@jhu.edu</a>><br>
<b>Cc:</b>
Arnold Rots
<<a
moz-do-not-send="true"
href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a>>;
Omar Laurino (<a
moz-do-not-send="true" href="mailto:olaurino@head.cfa.harvard.edu"
target="_blank">olaurino@head.cfa.harvard.edu</a>)
<<a
moz-do-not-send="true"
href="mailto:olaurino@head.cfa.harvard.edu" target="_blank">olaurino@head.cfa.harvard.edu</a>><br>
<b>Subject:</b>
Re: vo-dml for
cube</span></p>
</div>
</div>
<div>
<div>
<p
class="MsoNormal"> </p>
<div>
<div>
<div>
<div>
<div>
<div>
<p
class="MsoNormal">that's
great news.</p>
</div>
<p
class="MsoNormal">I
sent comments
from the other
thread, but
yes.. stc and
ds are
imported to
cube. dataset
has it's own
model/xmi
file.</p>
</div>
<p
class="MsoNormal">I'll
want to see
what you did
with the
stereotypes..
you were able
to generate
new ones?</p>
</div>
<p
class="MsoNormal">The
stc2 model in
my cube doc is
a little
different than
arnolds, but
most closely
related to the
2015-10-14
stuff.</p>
</div>
<p
class="MsoNormal">In
the end, all
the stc2
content will
be removed
from dataset,
and imported
as you show.</p>
</div>
<p
class="MsoNormal">Mark</p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p
class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<p
class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p
class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<div>
<p
class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p
class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>