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-falling out-of an enthusiastic admissible document within the a beneficial dialect, D, is a good semantics-preserving mapping so you can a document in every code L with a beneficial semantics-preserving mapping on L-document returning to an admissible D-file. Whenever you are semantically equivalent, the first and also the bullet-set off D-documents need not be similar.
4.step one XML to your RIF-FLD Words
RIF-FLD uses [XML1.0] for the XML syntax. The latest XML serialization for RIF-FLD is alternating or fully striped [ANF01]. A completely striped serialization opinions XML records because items and you can divides all the XML labels to your category descriptors, titled type tags, and you may property descriptors, named part labels [TRT03]. We proceed with the tradition of using capitalized names for particular tags and lowercase names for character labels.
The all-uppercase classes in the EBNF of the presentation syntax, such as Formula, 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 obtainable or =) become XML elements with optional attributes, as shown below.
For convenience of reference, the first 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 Feet and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.
The name away from good prefix is not regarding the an XML feature, because it is treated through preprocessing since discussed inside the Point Mapping of your own Non-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 example suggests a keen XML serialization towards formulas during the Analogy step three. Having best readability, i again use the shortcut sentence structure 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 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.