search

drdozer / oboformat

Automatically exported from code.google.com/p/oboformat
0 stars 0 forks source link

Specification - section 2.1 #60

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Same "For example, property_value-Tag should be interpreted as: 
'property_value:' { ws } " used for property-value tag and list example.

It would be helpful to say what <T>, <NT>, "TVP" (text value?), "BT" (boolean 
tag?) stand for.

Is there a definition somewhere of what a tag is and isn't?

Original issue reported on code.google.com by mcour...@gmail.com on 12 Dec 2011 at 11:00

GoogleCodeExporter commented 9 years ago 
Improved the docs, described what the acronyms stand for, and fixed some bold 
font issues. All non-terminals (NTs) should be in bold.

See what you think:
http://oboformat.googlecode.com/svn/trunk/doc/obo-syntax.html#BNF

Original comment by cmung...@gmail.com on 13 Dec 2011 at 1:34

GoogleCodeExporter commented 9 years ago 
Looks better - I didn't see the expansion for NT though. Also maybe adding a 
reference to BNF?
I went to check the wikipedia page 
http://en.wikipedia.org/wiki/Backus%E2%80%93Naur_Form which states "Terminals 
may appear in bold and NonTerminals in plain text rather than using italics and 
angle brackets." Though non normative, they say this is a commonly used rule. 
Do you abide by another standard/reference?

Original comment by mcour...@gmail.com on 13 Dec 2011 at 11:28

GoogleCodeExporter commented 9 years ago 
NT = non-terminal.

The bold/plain convention is followed in all of the W3 OWL speces I believe.

Also, these don't provide a reference for BNF either:

http://www.w3.org/TR/owl2-syntax/#BNF_Notation
http://www.w3.org/TR/owl2-manchester-syntax/

What is required is a high level companion guide to the formal specification. 
There is this, but it's not great:
http://www.geneontology.org/GO.format.obo-1_4.shtml

Original comment by cmung...@gmail.com on 16 Dec 2011 at 11:54