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

utworzone przez | sie 11, 2022 | BDSM review

4.dos Mapping on the RIF-FLD Presentation Sentence structure on 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 round-falling out of a keen admissible file in a dialect, D, is a semantics-retaining mapping to a document in almost any vocabulary L accompanied by a great semantics-sustaining mapping regarding L-file back to a keen admissible D-file. When you’re semantically similar, the initial and also the round-set off D-documents need not be the same.

cuatro.1 XML on RIF-FLD Words

RIF-FLD spends [XML1.0] because of its XML sentence structure. The fresh new XML serialization having RIF-FLD is actually alternating or completely striped [ANF01]. A completely striped serialization opinions XML files since the objects and you can splits the XML labels for the classification descriptors, named kind of tags, and you may assets descriptors, named character labels [TRT03]. I stick to the society of using capitalized brands having type labels and you can lowercase names having character tags.

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 bdsm, as shown below.

To have capability of resource, the initial formulas are included ahead

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 Feet and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.

Title away from good prefix is not of this an enthusiastic XML function, because it’s treated through preprocessing as the chatted about during the Section Mapping of your own Low-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 case reveals an enthusiastic XML serialization on the formulas inside Example 3. To possess finest readability, i once again make use of the shortcut sentence structure defined in [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.