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-tripping away from an admissible document from inside the a beneficial dialect, D, try good semantics-preserving mapping to help you a file in every language L with a semantics-preserving mapping from the L-document back again to a keen admissible D-file. While you are semantically equivalent, the first plus the bullet-set-off D-data doesn’t have to be identical.
cuatro.step one XML for the RIF-FLD Vocabulary
RIF-FLD spends [XML1.0] for its XML sentence structure. Brand new XML serialization to possess RIF-FLD was switching otherwise totally striped [ANF01]. A totally striped serialization opinions XML data because things and you may splits all of the XML tags on group descriptors, entitled sorts of tags, and you will property descriptors, called role tags [TRT03]. We follow the heritage of employing capitalized brands having form of tags and you will lowercase brands to own 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 Can be acquired or =) become XML elements with optional attributes, as shown below.
To have capacity for source, the original algorithms come 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 Ft and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.
Title from good prefix is not on the an XML function, because it is managed through preprocessing once the discussed from inside the Area Mapping of 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 shows an XML serialization into formulas during the Example step 3. For most useful readability, we once again utilize 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.