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 round-stumbling away from an enthusiastic admissible document inside an excellent dialect, D, try an effective semantics-preserving mapping in order to a file in any code L with a beneficial semantics-sustaining mapping from the L-file returning to an admissible D-file. When you are semantically similar, the initial therefore the bullet-trigger D-files need not be similar.
4.step one XML to the RIF-FLD Language
RIF-FLD spends [XML1.0] for its XML syntax. This new XML serialization to have RIF-FLD was changing otherwise fully striped [ANF01]. A totally striped serialization views XML files because stuff and you may divides all of the XML tags for the class descriptors, named types of tags, and assets descriptors, named part tags [TRT03]. We proceed with the society of employing capitalized labels having types of labels and you may lowercase labels to have 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 Is present or =) become XML elements with optional attributes, as shown below.
To possess capability of site, the first formulas come above
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 apex none for the Base and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.
The name off a good prefix is not of this an enthusiastic XML function, because it is treated through preprocessing since the discussed from inside the Area Mapping of your Low-annotated RIF-FLD Vocabulary.
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
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 reveals an enthusiastic XML serialization to the formulas inside Example step three. Having top readability, we once more make use of the shortcut syntax laid out 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 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.