4.dos Mapping on the RIF-FLD Demonstration Syntax with the XML Sentence structure

4.dos Mapping on the RIF-FLD Demonstration Syntax with the XML Sentence structure

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 circular-stumbling of an enthusiastic admissible document during the an excellent dialect, D, is actually a great semantics-preserving mapping to help you a file in any vocabulary L followed by an excellent semantics-preserving mapping regarding L-document back again to an enthusiastic admissible D-file. Whenever you are semantically similar, the initial and also the bullet-set-off D-files doesn’t have to be identical.

cuatro.1 XML to your RIF-FLD Language

RIF-FLD uses [XML1.0] for its XML syntax. The fresh XML serialization having RIF-FLD try changing otherwise fully striped [ANF01]. A fully striped serialization viewpoints XML data due to the fact things and divides every XML labels into category descriptors, entitled particular labels, and you can possessions descriptors, titled character tags [TRT03]. We stick to the tradition of utilizing capitalized labels for form of tags and lowercase names to have character 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 Is obtainable or =) become XML elements with optional attributes, as shown below.

To own convenience of source, the first algorithms are included on 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.

The name away from a prefix isn’t for the an enthusiastic XML element, because it’s treated through preprocessing as the talked about in Point Mapping of the 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 2007-11-23T-.

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 shows an XML serialization into algorithms inside Analogy step 3. For better readability, we again utilize the shortcut sentence structure discussed inside [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 adultspace dating apps 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.