4.2 Mapping from the RIF-FLD Speech Syntax on XML Sentence structure

Note that if D requires the directive Dialect(D) as part of its syntax then this implies that any D-admissible document must have this directive. ?

A circular-stumbling away from an enthusiastic admissible document from inside the a beneficial dialect, D, is an excellent semantics-preserving mapping so you’re able to a document in almost any vocabulary L followed by an effective semantics-preserving mapping about L-file to an admissible D-document. Whenever you are semantically similar, the initial and the round-set-off D-data files doesn’t have to be the same.

cuatro.1 XML into the RIF-FLD Code

RIF-FLD uses [XML1.0] for the XML syntax. This new XML serialization to own RIF-FLD was alternating or completely striped [ANF01]. A completely striped serialization viewpoints XML files once the things and you can splits all the XML tags into the classification descriptors, named sorts of of labels, and possessions descriptors, titled role tags [TRT03]. We follow the community of employing capitalized labels to own type tags and you may lowercase names having character tags.

The all-uppercase classes in the EBNF of the presentation syntax, such as Algorithm, become XML Schema groups in Appendix XML Schema for FLD. They are not visible in instance markup. The other classes as well as non-terminals and symbols (such as Can be obtained or =) become XML elements with optional attributes, as shown below.

Getting convenience of source, the first algorithms come over the top

The RIF serialization framework for the syntax of Section EBNF Grammar for the Presentation Syntax of RIF-FLD uses the following XML tags. While there is a RIF-FLD element tag for the Import directive and an attribute for the Dialect directive, there are none for the Foot and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.

The name regarding a beneficial prefix isn’t with the a keen XML element, since it is managed thru preprocessing given that chatted about in Point Mapping of one’s Non-annotated RIF-FLD Language.

The id and meta elements, which are expansions of the IRIMETA element, can occur optionally as the initial children of any Class element.

The XML syntax for symbol spaces uses the type attribute associated with the XML element Const. For instance, a literal in the xs:dateTime datatype is represented as 2007-11-23T-.

The xml:lang attribute, as defined by 2.12 Language Identification of XML 1.0 or its successor specifications in the W3C recommendation track, is optionally used to identify the language for the presentation of the Const to the user. It is allowed only in association with constants of the type rdf:plainLiteral. A compliant implementation MUST ignore the xml:lang attribute if the type of the Const is not rdf:plainLiteral.

This situation suggests an XML serialization towards formulas inside the Example step 3. Getting best readability, i again utilize the shortcut syntax discussed when you look at the [RIF-DTB].

This section defines a normative mapping, ?fld, from the presentation syntax of Section EBNF Grammar for the Presentation Syntax of RIF-FLD to the XML syntax of RIF-FLD. The mapping is given via tables where each row specifies the mapping of a particular syntactic pattern in the presentation syntax. These patterns appear http://www.datingranking.net/tr/spicymatch-inceleme/ in the first column of the tables and the bold-italic symbols represent metavariables. The second column represents the corresponding XML patterns, which may contain applications of the mapping ?fld to these metavariables. When an expression ?fld(metavar) occurs in an XML pattern in the right column of a translation table, it should be understood as a recursive application of ?fld to the presentation syntax represented by the metavariable. The XML syntax result of such an application is substituted for the expression ?fld(metavar). A sequence of terms containing metavariables with subscripts is indicated by an ellipsis. A metavariable or a well-formed XML subelement is marked as optional by appending a bold-italic question mark, ?, to its right.