cuatro.dos Mapping regarding the RIF-FLD Demonstration Sentence structure into the 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 spherical-falling out-of a keen admissible document inside the a dialect, D, was a semantics-preserving mapping to a file in just about any language L followed closely by a good semantics-retaining mapping about L-document to an enthusiastic admissible D-file. While you are semantically comparable, the original while the bullet-set off D-data files doesn’t have to be the same.

cuatro.1 XML to your RIF-FLD Vocabulary

RIF-FLD uses [XML1.0] because of its XML sentence structure. The brand new XML serialization getting RIF-FLD was alternating or fully striped [ANF01]. A completely striped serialization feedback XML files given that items and you will splits all XML labels towards the group descriptors, called method of labels, and possessions descriptors, named role tags [TRT03]. We follow the tradition of utilizing capitalized brands getting type labels and you will lowercase bbpeoplemeet labels getting 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 found or =) become XML elements with optional attributes, as shown below.

To own capacity for reference, the initial formulas are included on 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 Transfer directive and an attribute for the Dialect directive, there are none for the Ft and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.

Title of a beneficial prefix isn’t on the an enthusiastic XML function, because it’s addressed via preprocessing given that chatted about inside the Area Mapping of the Low-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 example suggests an XML serialization toward algorithms into the Analogy step three. To have finest readability, i once again make use of the shortcut syntax defined during 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 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.