<div dir="ltr">Markus,<br><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 5, 2017 at 8:28 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Mark, Dear everyone-else-who-as-stuff-in volute/.../DM,<br>
<br>
I got hold of some time series data and would now like to write a<br>
prototype service for these. I'd like this to spit out something as<br>
close to current drafts, Jiris proposal, SPLAT implemenation, and my<br>
hopes at the same time. For that, it would be great if I had a<br>
blueprint of the "current upstream idea", as it were. So,<br>
<span class=""><br>
On Mon, Mar 27, 2017 at 05:38:55PM -0400, CresitelloDittmar, Mark wrote:<br>
> I have 'mocked' the resulting model changes and generated some example<br>
> files:<br>
> 1) chandra event list (real-world cube file)<br>
> 2) timeseries example from the Note.. Figures 5, 6, 7<br>
> with added detail about the CoordSys, Frames, etc.<br>
<br>
</span>Are these files available now? If so, where?<br></blockquote><div><br></div><div>I have the file from this pass. I did not submit it because upon review, we realized that the change I made to the model broke a different requirement.. namely the ability to specify the flavor of a 'Measurement' (eg; target.pos:Position )<br><br></div><div>I have a new revision which accommodates both, and will be generating that (and other) examples in the next couple days.<br></div><div>We have been focused the past few days on resolving some details needed to get a PDF working draft out to the group.<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But since I just stumbled around in the DM tree in volute, I've<br>
accumulated some additional requests as regards its (particular)<br>
contents. They come mainly with my user hat on (at least for me, it<br>
is *very* hard to figure out what's what right now), but a little bit<br>
of what's on my head is also coming from me as operator; everything's<br>
much easier for a VCS (and makes more sense) if the amount of binary<br>
data is a low as it can possibly be.<br>
<br>
(1) volute is a VCS, so it does versioning by itself. It would<br>
therefore be great if you just kept the latest version of each<br>
document in there and *not* use version number in file names. If<br>
people actually want to go back in time, they can use the standard<br>
svn mechanisms (svn log, svn co -r...; yes, with office files there<br>
are no diffs, which is regrettable, but the full files are still<br>
there). That would already clean up a directory like<br>
<a href="http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/doc/" rel="noreferrer" target="_blank">http://volute.g-vo.org/svn/<wbr>trunk/projects/dm/vo-dml/doc/</a> very nicely.<br></blockquote><div><br></div><div>Agreed!<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
(2) Being a VCS, I think volute should not be polluted by things that<br>
aren't "source" but can be generated from things in volute. In<br>
particular, I don't think "baked" PDFs should be in there. They are<br>
almost certain to cause version conflicts, and there's no added value<br>
in having them in a VCS. And no, putting PDFs into volute don't<br>
really improve any of the issues associated with using docx...<br>
<br></blockquote><div>A little more problematic since a lot of people do their documenting in something other than tex, but I understand the concern.<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
(3) It'd be great if there was a top-level readme explaining where<br>
things are supposed to be (there's vo-dml/README.txt that goes a long<br>
way, but how does that relate to the rest of the dm tree?). Right now,<br>
if I look for, say, the vo-dml of Dataset, where do I go? Is<br>
<a href="http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/" rel="noreferrer" target="_blank">http://volute.g-vo.org/svn/<wbr>trunk/projects/dm/vo-dml/<wbr>models/</a> the right<br>
place? Or<br>
<a href="http://volute.g-vo.org/svn/trunk/projects/dm/DatasetMetadata-1.0/model/" rel="noreferrer" target="_blank">http://volute.g-vo.org/svn/<wbr>trunk/projects/dm/<wbr>DatasetMetadata-1.0/model/</a>?<br>
In the latter directory, there's even a zip file -- that in turn<br>
contains a project.conf that says "GENERATED FILE, PLEASE DO NOT<br>
EDIT!!!" [all the bangs included] -- does something like this really<br>
have to be under version control?<br></blockquote><div>We have need to share the model project in progress, this zip file is that project. As things evolve, and we have better, vo-dml savvy, modeling tools available, this will be cleaner.<br></div><div> </div><div>There is a section in the vo-dml beginner's guide which describes the layout that I would like to see here...<br></div><div>(obviously, there is a lot of heritage stuff, but it is the layout that I've been using). I agree that a README<br></div><div>with that content in the 'dm' directory would be helpful.<br><br></div><div>In general<br></div><div> .../dm/<model>/* == model document (PDF), diagrams, project file (UML) content, and XMI export<br></div><div> .../vo-dml/models/<model> == vo-dml XML and HTML products<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
(4) Lastly, again since volute is a VCS, it would be great if you<br>
could just delete from trunk the traces of efforts that are pretty<br>
certainly abandoned (e.g., ImageDM, I guess, SpectralDM-2.0 as well).<br>
These things can always be recovered from the history if really<br>
necessary, and if you think they must be visible somewhere in<br>
HEAD, just make a tag containing whatever is going on (e.g.<br>
<br>
svn copy <a href="http://volute.g-vo.org/svn/trunk/projects/dm/SpectralDM-2.0/" rel="noreferrer" target="_blank">http://volute.g-vo.org/svn/<wbr>trunk/projects/dm/SpectralDM-<wbr>2.0/</a> \<br>
<a href="http://volute.g-vo.org/svn/tags/DM-attic/SpectralDM-2.0-as-abandoned" rel="noreferrer" target="_blank">http://volute.g-vo.org/svn/<wbr>tags/DM-attic/SpectralDM-2.0-<wbr>as-abandoned</a><br>
svn remove <a href="http://volute.g-vo.org/svn/trunk/projects/dm/SpectralDM-2.0/" rel="noreferrer" target="_blank">http://volute.g-vo.org/svn/<wbr>trunk/projects/dm/SpectralDM-<wbr>2.0/</a><br>
<br>
All of that would really help usability of the dm subtree in volute.<br></blockquote><div><br></div><div>Good suggestion. <br></div><br><br></div><div class="gmail_quote">I know the 'stc' project is particularly confusing in this regard, with some early prototypes to cast stc1 etc, <br></div><div class="gmail_quote">We will be cleaning some of this up as we go forward.<br><br></div><div class="gmail_quote">Mark<br><br></div></div></div></div>