cuatro.2 Mapping on RIF-FLD Presentation Sentence structure on XML Sentence structure

cuatro.2 Mapping on RIF-FLD Presentation Sentence structure on 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 round-tripping regarding a keen admissible document inside the an effective dialect, D, is actually a semantics-preserving mapping so you can a file in every code L followed closely by good semantics-retaining mapping from the L-document to a keen admissible D-document. Whenever you are semantically similar, the initial and round-trigger D-documents need not be similar.

cuatro.1 XML on the RIF-FLD Vocabulary

RIF-FLD uses [XML1.0] because of its XML sentence structure. The new XML serialization for RIF-FLD is actually changing otherwise fully striped [ANF01]. A fully striped serialization feedback XML files just like the objects and you will splits every XML labels to your class descriptors, called sort of tags, and assets descriptors, called character labels [TRT03]. I stick to the community of utilizing capitalized brands to own form of labels and lowercase names for 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 possess capacity for resource, the first algorithms are included 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 Ft and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.

The name regarding a good prefix isn’t for the a keen XML ability, because it’s managed via preprocessing due to the fact talked about inside the Area Mapping of your own Non-annotated RIF-FLD Code.

The id and meta elements, which are expansions of the IRIMETA element, can occur optionally babel 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 case reveals an enthusiastic XML serialization into algorithms within the Analogy step three. To have finest readability, we once more make use of the shortcut syntax laid out inside 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.