cuatro.2 Mapping regarding RIF-FLD Presentation Syntax with the XML Syntax

cuatro.2 Mapping regarding RIF-FLD Presentation Syntax with the XML Syntax

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-falling out of a keen admissible document from inside the a beneficial dialect, D, is an effective semantics-sustaining mapping so you can a file in any language L with good semantics-retaining mapping regarding L-document to an admissible D-file. If you find yourself semantically comparable, the original and also the bullet-set-off D-files need not be identical.

4.1 XML to the RIF-FLD Words

RIF-FLD spends [XML1.0] for the XML sentence structure. The brand new XML serialization to have RIF-FLD try switching or fully striped [ANF01]. A fully striped serialization viewpoints XML data since the stuff and you can splits all XML labels for the classification descriptors, titled method of tags, and you will possessions descriptors, entitled role labels [TRT03]. We follow the traditions of utilizing capitalized names to own style of labels and you can lowercase brands to beetalk tips own part 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 Can be acquired or =) become XML elements with optional attributes, as shown below.

To have capacity for source, the first algorithms are included 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 Foot and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.

Title away from a prefix isn’t with the a keen XML element, since it is handled through preprocessing as chatted about during the Section Mapping of your 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 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 situation shows a keen XML serialization to your algorithms in the Analogy step three. To have most useful readability, we once more use the shortcut syntax 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 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.

No Comments

Post a Comment