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 regarding an enthusiastic admissible document within the an effective dialect, D, try a beneficial semantics-retaining mapping so you’re able to a file in virtually any words L accompanied by a great semantics-retaining mapping from the L-document back to a keen admissible D-document. If you’re semantically similar, the first therefore the round-tripped D-data doesn’t have to be similar.
RIF-FLD uses [XML1.0] for its XML sentence structure. The latest XML serialization getting RIF-FLD is actually switching or totally striped [ANF01]. A completely striped serialization viewpoints XML data files as the stuff and you can divides all the XML labels to the category descriptors, entitled sorts of tags, and assets descriptors, titled role tags [TRT03]. We proceed with the traditions of using capitalized labels to possess sorts of tags and you will lowercase labels getting part labels.
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 Is present or =) become XML elements with optional attributes, as shown below.
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 Legs and Prefix directives: they are handled as discussed in Section Mapping from the RIF-FLD Presentation Syntax to the XML Syntax.
The name out of good prefix isn’t with the an enthusiastic XML function, because it’s treated through preprocessing since the talked about within the Part Mapping of 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
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 suggests an enthusiastic XML serialization with the algorithms during the Example step three. To possess most useful readability, i again make use of 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 https://datingranking.net/alua-review/ 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.