So far, in order to indicate the sentence structure away from RIF-FLD we relied on “analytical English,” a different sort of style of English having connecting statistical significance, advice, etcetera. The next points towards EBNF notation is going to be stored in mind:
- The brand new syntax regarding RIF-FLD relies on the fresh signature device that’s not context-100 % free, therefore EBNF doesn’t just take so it syntax correctly. Because of this, the fresh EBNF grammar talks of a rigid superset off RIF-FLD (not all formulas that will be https://datingranking.net/tr/tsdates-inceleme/ derivable making use of the EBNF grammar are well-formed).
- The EBNF syntax is not a concrete syntax: it does not address the details of how constants (defined in [RIF-DTB]) and variables are represented, and it is not sufficiently precise about the delimiters and escape symbols. White space is informally used as a delimiter, and is implied in productions that use Kleene star. For instance, TERM* is to be understood as Term Title . Label, where each ‘ ‘ abstracts from one or more blanks, tabs, newlines, etc. This is done intentionally since RIF’s presentation syntax is used as a tool for specifying the semantics and for illustration of the main RIF concepts through examples.
- RIF talks of a tangible syntax simply for buying and selling legislation, hence sentence structure was XML-established, obtained since the a sophistication and you will serialization of EBNF syntax via new demonstration-syntax-to-XML mapping having RIF-FLD.
Remaining the above at heart, the fresh new EBNF grammar is seen since the merely a mediator anywhere between new analytical English as well as the XML. Yet not, it gives a concise view of new sentence structure off RIF-FLD and thus can be handy to have dialect painters and you will profiles similar.
For each RIF-FLD algorithm and name should be prefixed which have that elective annotation
The RIF-FLD presentation syntax does not commit to any particular vocabulary and permits arbitrary sequences of Unicode characters in constant symbols, argument names, and variables. Such sequences are denoted with UNICODESTRING in the above syntax. Constant symbols have this form: "UNICODESTRING"^^SYMSPACE, where SYMSPACE is a ANGLEBRACKIRI or CURIE that represents the identifier of the symbol space of the constant. UNICODESTRING, ANGLEBRACKIRI, and CURIE are defined in Section Shortcuts for Constants in RIF’s Presentation Syntax of [RIF-DTB]. Constant symbols can also have several shortcut forms, which are represented by the non-terminal CONSTSHORT. These shortcuts are also defined in the same section of [RIF-DTB]. One of them is the CURIE shortcut, which is used in the examples in this document. Names are Unicode character sequences that form valid XML NCNames [XML-Names]. Variables are composed of Names prefixed with a ?-sign.
, which is used in several places in the grammar, is a non-terminal whose definition is left to the dialects. It is intended to specify the protocol by which external sources, remote modules, and imported RIF documents are located. This must include the basic form
The symbols NEWCONNECTIVE, NEWQUANTIFIER, NEWAGGRFUNC, and NEWTERM are RIF-FLD extension points. They are not actual symbols in the alphabet. Instead, dialects are supposed to replace NEWCONNECTIVE, NEWQUANTIFIER, and NEWAGGRFUNC, by zero or more actual new symbols, while NEWTERM is to be replaced by zero or more new kinds of terms. Note that the extension point NEWSYMBOL is not shown in the EBNF grammar completely avoids mentioning the alphabet of the language (which is infinite).
IRIMETA, for identification and metadata. IRIMETA is represented using (*. *)-brackets that contain an optional rif:iri constant as identifier followed by an optional Figure or cones as metadata. One such specialization is '"' IRI '"^^' 'rif:iri' from the Const production, where IRI is a sequence of Unicode characters that forms an internationalized resource identifier as defined by [RFC-3987].