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-stumbling from an admissible file for the a great dialect, D, was a great semantics-retaining mapping to a document in almost any code L followed closely by good semantics-sustaining mapping about L-document back once again to a keen admissible D-file. If you are semantically similar, the first additionally the round-set off D-data need not be the same.
cuatro.1 XML on the RIF-FLD Language
RIF-FLD spends [XML1.0] for the XML syntax. New XML serialization to have RIF-FLD try alternating otherwise completely striped [ANF01]. A completely striped serialization feedback XML files due to the fact objects and divides the XML tags with the category descriptors, entitled variety of labels, and property descriptors, named role labels [TRT03]. I stick to the community of using capitalized labels getting sorts of labels and you may lowercase names having role labels.
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 Exists or =) become XML elements with optional attributes, as shown below.
To have convenience of site, the original formulas are included 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 Import 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 out of a prefix is not associated with the an XML feature, because it is handled through preprocessing just like the talked about in Point Mapping of your Low-annotated RIF-FLD Words.
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 a keen XML serialization with the algorithms inside the Analogy step three. To own most readily useful readability, we once more use the shortcut sentence structure 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 https://datingranking.net/bdsm-review/ 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.