Up to now, in order to identify new syntax from RIF-FLD we relied on “analytical English,” yet another style of English for connecting analytical significance, instances, etc. Another affairs regarding EBNF notation will be stored in mind:
LOCATOR
- The fresh sentence structure out of RIF-FLD utilizes the signature procedure and is not framework-totally free, thus EBNF doesn’t need so it syntax precisely. This means that, the latest EBNF grammar talks of a tight superset off RIF-FLD (not all formulas which can be derivable utilising the EBNF sentence structure is 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 Name Label . Term, 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 represent a tangible sentence structure simply for investing statutes, which syntax try XML-established, received just like the a sophistication and serialization of the EBNF syntax via the fresh new presentation-syntax-to-XML mapping to have RIF-FLD.
Staying the aforementioned at heart, the fresh EBNF sentence structure is seen due to the fact merely an intermediary between the fresh new statistical English and the XML. But not, it also gets a brief view of the new sentence structure away from RIF-FLD and thus they can be handy for dialect designers and profiles exactly the same.
For each RIF-FLD algorithm and label should be prefixed with you to optional 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 https://datingranking.net/tr/tsdating-inceleme/ 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 Body type 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].
