From gruninger at mie.utoronto.ca Tue Sep 25 16:14:04 2012 From: gruninger at mie.utoronto.ca (Michael Gruninger) Date: Tue, 25 Sep 2012 10:14:04 -0400 Subject: [Hets-devel] [Hets] #1061: check whether COLORE can be analysed with Hets In-Reply-To: <053.c0ab3c2fbdaf7c7a3401b4fb422c739a@informatik.uni-bremen.de> References: <044.e3651a2c6ee78b54e872ce3fe16500c2@informatik.uni-bremen.de> <053.c0ab3c2fbdaf7c7a3401b4fb422c739a@informatik.uni-bremen.de> Message-ID: <5061BC2C.8000803@mie.utoronto.ca> The ISO 2407 Defect Report recommended that the correct syntax for comments be (cl-comment "foo") and this is what is adopted in COLORE and the parsers that we have implemented. What other syntax errors have you found? You can post issues to the COLORE googlegroup. - michael On 12-09-25 6:13 AM, Hets wrote: > #1061: check whether COLORE can be analysed with Hets > --------------------+------------------------------------------------------- > Reporter: till | Owner: sschulze > Type: task | Status: assigned > Priority: normal | Milestone: 0.99 > Component: hets | Version: 0.98 > Keywords: | > --------------------+------------------------------------------------------- > Changes (by sschulze): > > * status: new => assigned > > > Comment: > > The most common errors seem to be: > > 1. Files that are located in other sub-directories cannot be imported. > > 2. Some files employ the {{{ (cl-comment "foo") }}} syntax, which does not > seem to be legal. ({{{ (cl-comment 'foo') }}} is correct.) > > After flattening the tree and permitting the former comment syntax, most > files parse, whereas all that did not and that I inspected so far contain > obvious syntactic errors. > > How are these points supposed to be addressed? > From christoph.lange at uni-bremen.de Thu Sep 27 13:45:23 2012 From: christoph.lange at uni-bremen.de (Christoph LANGE) Date: Thu, 27 Sep 2012 12:45:23 +0100 Subject: [Hets-devel] [Hets] #1020: add serialisation syntax to DOL/HetCASL parser In-Reply-To: <053.12b73da3e6205da1e479f2aa5daa647b@informatik.uni-bremen.de> References: <044.a2ca367939c0e571ca0419baf229e10b@informatik.uni-bremen.de> <053.12b73da3e6205da1e479f2aa5daa647b@informatik.uni-bremen.de> Message-ID: <50643C53.6000808@uni-bremen.de> Hi all, as I can't access the Trac right now (server down?), let me reply to this ticket to the mailing list. 2012-09-27 12:24 Hets: > #1020: add serialisation syntax to DOL/HetCASL parser > ----------------------+----------------------------------------------------- > Reporter: till | Owner: sschulze > Type: task | Status: assigned > Priority: normal | Milestone: 0.99 > Component: casl-ext | Version: 0.98 > Keywords: | > ----------------------+----------------------------------------------------- > Changes (by sschulze): > > * status: new => assigned > > > Comment: > > Should the {{{ syntax }}} keyword also be supported, as used in the > examples in > http://www.informatik.uni-bremen.de/~till/papers/tke12.pdf? I'd say yes, but Till has to decide. Oh, and the name of the keyword is now "serialization", for coherence. Please consult the _standard_ if in doubt about any syntax; most of the papers contain obsolete examples. IMHO supporting this keyword in Hets makes sense, but in a limited way. AFAIK Hets so far only supports one serialization per ontology language, so supporting the keyword effectively means: 1. If an ontology is not prefixed with a serialization keyword, Hets assumes an application-specific default (which is the only serialization that Hets supports for the respective ontology language) 2. If a file contains "serialization ", the effect is the same as in (1) 3. If a file contains "serialization ", it is not necessarily a syntax error, but Hets can't parse the ontology. Cheers, Christoph -- Christoph Lange, Universit?t Bremen (now: University of Birmingham) http://kwarc.info/clange, Skype duke4701 ? Building & Exploring Web Based Environments. Seville, Spain, 27 Jan? 1 Feb 2013. Deadline 22 Sep. http://iaria.org/conferences2013/WEB13.html