<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi Sebastian, I agree to clean up, the folder structure is good. If possible, it would be good if you could look into the currenty ANT scripts that do the whole business of generating the HTML files and converting the ontologies. The current layout is not because we like chaos, but because our current set of ANT scripts works with that setup and it was too hard to change the script (it was easier to just put all ontologies into the same folder and then tweak the ant script) In general, I do not like the smell of release/draft folders, but I think its ok. I think each ontology should be in its own folder and some readme.txt should show the status, but its also fine the way with superfolders. but we should not try to classify them further using folder strucutres, this will end up in sucking, rather use the wiki to guide people around. The W3C way is something like ...2009/06/ndo-draft  .... then ...2006/08/ndo-draft  ... then ...tr/ndo we should use SVN tags to mark releases and otherwise keep the files always in the same folder, its much more convenient, but also here I am open for ideas. about TRIG: (I would like N3, see below) this is fine, we stopped using protégé for ontology development some time ago, because as we are doing a standardization process, the SVN logs are very very very important to verify what chnages have been done, and a visual ontology editor sometimes reformats the whole file, which makes it impossible to verify what has been changed by whom and why, so I am in favor for TRIG and text files. Could someone write this down on our OntologyMaintenance page? there is only one problem - there is a lack of online tools [1] for checking/validating/converting trig, this sucks. For the sake of keeping a sane mind, and being quick while hacking, I would propose to use N3 instead because there is more tool support for it. [1] <a class="moz-txt-link-freetext" href="http://rdfabout.com/demo/validator/index.xpd">http://rdfabout.com/demo/validator/index.xpd</a> <a class="moz-txt-link-freetext" href="http://www.mindswap.org/2002/rdfconvert/">http://www.mindswap.org/2002/rdfconvert/</a> -> these tools, which I daily use when cheking ontologies, do not support trig. Trig=bad n3=good best Leo It was Ivan Frade who said at the right time 26.06.2009 14:56 the following words: <blockquote cite="mid:b50f4ef30906260556k550e33cdgb9679852f80a8e@mail.gmail.com" type="cite">Hi! <div class="gmail_quote">On Fri, Jun 26, 2009 at 11:41 AM, Sebastian Trüg <<a moz-do-not-send="true" href="mailto:strueg@mandriva.com">strueg@mandriva.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I'd say we make it very simple: top level dirs "ontologies" and "tools" in the trunk. And then: trunk  ontologies     release        pimo        nie        nfo        nco        nmo        ncal        nexif        nid3     draft        ndo        nmm  tools     <whatever> </blockquote> <div> I like it. Just to clarify "release" means that are "public" ontologies. Every now and then we will create tags in the svn to have a "released" pack of ontologies, right? </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">In the single ontology dirs I would put the trig sources directly. I propose we work on those since trig is way easier to read and hack than rdf+xml and it is the distribution format anyway.</blockquote> <div> I think it is a good idea.  </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Then the folders could have "documentation" subdirs which in the case of pimo should include the sources for the pimo.pdf written by leo (if he agrees). Each ontology folder will also have a ChangeLog file in which we should note each change to the onto.</blockquote> <div> The HTML documentation with the classes and properties, and links between them... is generated directly from the ontology files? so, that documentation folder is just for "extra" stuff? </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Do we need anything else?</blockquote> <div> I dont see anything evident missing. </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Once an ontology is decided and should be released it is moved from the draft to the release folder. A tool could gather all release ontologies and package them for a release. If you agree I will take care of this. </blockquote> <div> Sounds great! Thanks! </div> </div> Ivan <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ Xesam mailing list <a class="moz-txt-link-abbreviated" href="mailto:Xesam@lists.freedesktop.org">Xesam@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/xesam">http://lists.freedesktop.org/mailman/listinfo/xesam</a> </pre> </blockquote> <pre class="moz-signature" cols="72">-- ____________________________________________________ DI Leo Sauermann <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz DFKI GmbH Trippstadter Strasse 122 P.O. Box 2080 Fon: +49 631 20575-116 D-67663 Kaiserslautern Fax: +49 631 20575-102 Germany Mail: <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a> Geschaeftsfuehrung: Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 ____________________________________________________ </pre> </body> </html>