<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>HI</p>
<p>Just a comment to correct one statement by Francois:<br>
</p>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div dir="ltr"> - As both Arnold and Laurent stated in different wordings one of the usage of UML (and attached VO-DML description) is generation of code. ObjectType will become classes and having instances of that for "coefficient" and "pixel" will lead
to considerable overhead.<br>
</div>
</div>
<div style="color: rgb(33, 33, 33);">-----------------------------------------------------------------</div>
<div style="color: rgb(33, 33, 33);"><br>
</div>
<div style="color: rgb(33, 33, 33);">Arnold and Laurent may have stated that a supposed usage of VO-DML is code generation, but that does not make it true.
</div>
<div style="color: rgb(33, 33, 33);">If you want, you *can* generate code from the VO0-DML , but that is not necessarily a good thing to do in all cases.</div>
<div style="color: rgb(33, 33, 33);">It depends on application. <br>
</div>
<div style="color: rgb(33, 33, 33);"><br>
</div>
<div style="color: rgb(33, 33, 33);">
<div style="color: rgb(33, 33, 33);">The original motivation of VO-DML was its use in annotations for VOTable. In general it is supposed to be used to represent the concepts in what is sometimes called the "universe of discourse" of some application domain
in an interoperable form.</div>
<div style="color: rgb(33, 33, 33);">Hence VO-DML is supposed to be application neutral, and it is *not* a requirement on the VO-DML spec that efficient code can be generated from it in all cases.
<br>
<div style="color: rgb(33, 33, 33);">To use the model in a specific application/implementation in general requires one to derive application specific representations, "serializations" if you will. <br>
</div>
</div>
<div style="color: rgb(33, 33, 33);">These representations will generally be optimized for their actual application, which will not always be possible using a simple mapping approach that can be implemented in a code generator.<br>
One example where that might happen is in DAL protocols.<br>
</div>
<div style="color: rgb(33, 33, 33);"><br>
</div>
</div>
<div style="color: rgb(33, 33, 33);">Btw, please do not confuse VO-DML with UML, VO-DML is the only language we propse, UML is NOT a required, nor normative part of the spec.<br>
<div style="color: rgb(33, 33, 33);"><br>
Cheers</div>
<div style="color: rgb(33, 33, 33);">Gerard<br>
</div>
<br>
</div>
<div style="color: rgb(33, 33, 33);">
<div dir="ltr"><br>
Cheers<br>
François <br>
</div>
<div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Omar.</div>
<div class="gmail_extra"><br>
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">Omar Laurino<br>
Smithsonian Astrophysical Observatory<br>
Harvard-Smithsonian Center for Astrophysics
<div>100 Acorn Park Dr. R-377 MS-81</div>
<div>02140 Cambridge, MA<br>
<span><a value="+16174957227">(617) 495-7227</a></span></div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</div>
</body>
</html>