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 a keen admissible file when you look at the a beneficial dialect, D, are an excellent semantics-sustaining mapping so you can a document in any vocabulary L with an excellent semantics-retaining mapping in the L-document back once again to an admissible D-document. When you find yourself semantically equivalent, the first together with bullet-set-off D-records need not be the same.
4.step 1 XML for the RIF-FLD Vocabulary
RIF-FLD spends [XML1.0] for its XML sentence structure. The new XML serialization to have RIF-FLD was switching otherwise fully striped [ANF01]. A fully striped serialization feedback XML data because objects and splits all of the XML tags into the category descriptors, called kind of tags, and you will property descriptors, called role labels [TRT03]. I proceed with the traditions of utilizing capitalized labels to have type tags and you may lowercase names to own part 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 obtained or =) become XML elements with optional attributes, as shown below.
Having convenience of site, the original formulas come at 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 Import directive and an attribute for the Dialect directive, there are 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.
Title out of a beneficial prefix isn’t of the an XML element, since it is managed thru preprocessing as discussed for the Area Mapping of the Non-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 case suggests a keen XML serialization towards formulas in Analogy 3. To possess greatest readability, we once again make use of the shortcut syntax discussed 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.