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-tripping out of an admissible document in a good dialect, D, are a great semantics-retaining mapping so you’re able to a file in virtually any code L followed closely by a beneficial semantics-preserving mapping from the L-file amateurmatch returning to an enthusiastic admissible D-file. If you are semantically equivalent, the initial together with round-set off D-data files doesn’t have to be identical.
cuatro.step one XML on the RIF-FLD Words
RIF-FLD uses [XML1.0] for the XML syntax. The new XML serialization to possess RIF-FLD try alternating otherwise completely striped [ANF01]. A totally striped serialization feedback XML documents as objects and you can divides most of the XML labels on group descriptors, called sort of tags, and you will possessions descriptors, entitled part labels [TRT03]. I stick to the customs of employing capitalized labels to have form of tags and lowercase names having role tags.
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 Exists or =) become XML elements with optional attributes, as shown below.
To have capacity for reference, the original formulas come ahead
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 Ft and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.
Title away from a great prefix is not from the a keen XML function, because it’s addressed via preprocessing while the talked about in the Section Mapping of Low-annotated RIF-FLD Code.
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 an enthusiastic XML serialization towards the formulas for the Example step 3. To have most readily useful readability, i once again utilize the shortcut sentence structure laid out in 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.