Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Specification - section 2.1 #60

Closed
GoogleCodeExporter opened this issue Mar 12, 2015 · 3 comments
Closed

Specification - section 2.1 #60

GoogleCodeExporter opened this issue Mar 12, 2015 · 3 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

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
Copy link
Author 

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
Copy link
Author 

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
Copy link
Author 

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

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter