- From: Chris Mungall <cjmungall@lbl.gov>
- Date: Wed, 11 Mar 2015 17:10:48 -0700
- To: "Ignazio Palmisano" <ipalmisano.mailings@gmail.com>
- Cc: "public-owl-dev@w3.org" <public-owl-dev@w3.org>
On 11 Mar 2015, at 12:00, Ignazio Palmisano wrote: > On 11 March 2015 at 17:56, Chris Mungall <cjmungall@lbl.gov> wrote: >> >> If the goal is pretty-printing, then it needs to emit labels after >> ##s, akin >> to obo format and the behavior of the owlapi rdf/xml writer. This >> dictates >> behavior regarding newlines for closing parentheses. >> >> E.g. >> >> SubClassOf( >> Annotation( >> :IAO_0000232 ## curator note >> "this is a text axiom" >> ) >> :ZFA_0005587 ## nephron progenitor >> ObjectSomeValuesFrom( >> :BFO_0000050 ## part of >> :ZFA_0000529 ## kidney >> )) >> >> If only annotations were the final argument rather than the first. >> >> Perhaps what we actually need is a new syntax designed from the >> ground up >> with specific requirements in mind (e.g. layered on a sensible syntax >> like >> yaml, no lingering traces of lisp, VCSable, readable, moderately >> hackable in >> a text editor, incorporating @context ideas from JSON-LD). >> > > This made me wonder if the intent is a pretty print only, for human > eyes to peruse, or if it's intended to be parseable by the existing > FSS parsers. > A lot more possibilities open up if parsing back is not a requirement > - would be a different output format, in actuality. Parsing is a requirement. Yes, if this wasn't a requirement there are a number of possibilities, e.g. Protege-style-Manchester-with-labels-for-rendering. > Cheers, > I.
Received on Thursday, 12 March 2015 00:11:29 UTC