4.2 Mapping in the RIF-FLD Speech Sentence structure on XML Syntax

4.2 Mapping in the RIF-FLD Speech Sentence structure on 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-tripping of an admissible document in the a beneficial dialect, D, try good semantics-retaining mapping in order to a document in just about any code L followed by an excellent semantics-preserving mapping regarding the L-document back again to an enthusiastic admissible D-document. When you are semantically comparable, the first in addition to round-set-off D-data need not be the same.

cuatro.1 XML into the RIF-FLD Vocabulary

RIF-FLD uses [XML1.0] for its XML sentence structure. The fresh new XML serialization for RIF-FLD try alternating otherwise totally striped [ANF01]. A totally striped serialization views XML data files given that items and you may splits all of the XML labels towards the category descriptors, entitled method of tags, and possessions descriptors, titled role tags [TRT03]. I stick to the lifestyle of employing capitalized names to possess sort of tags and you can lowercase labels for role tags datingranking.net/ardent-review/.

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.

For capacity for resource, the original formulas come over 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.

The name from good prefix is not regarding the an enthusiastic XML element, because it is addressed via preprocessing just like the chatted about inside Part 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 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 with the formulas into the Example 3. To have greatest readability, we once more make use of the shortcut sentence structure defined 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 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.

Comparte esta publicación

Compartir en facebook
Compartir en twitter
Compartir en linkedin
Compartir en whatsapp
Compartir en email

Deja tu comentario


Próximo Webinar

Información Relevante

Entrar con cuenta Schwabe

Si aún no tienes cuenta, ingresa aquí para registrarte.


Entra a tu cuenta para continuar viendo el contenido…

Entrar con cuenta Schwabe

Si aún no tienes cuenta, ingresa aquí para registrarte.