[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [legalruleml] WD26
Here is some new material - Tara
5.15.1 Modules The missing citation is Athan, Tara, and Harold Boley. 2011.
“Design and Implementation of Highly Modular Schemas for XML:
Customization of RuleML in Relax NG.” In Rule - Based
Modeling and Computing on the Semantic Web, edited by
Frank Olken, Monica Palmirani, and Davide Sottara, 7018:17–32.
Lecture Notes in Computer Science. Springer Berlin Heidelberg.
http://dx.doi.org/10.1007/978-3-642-24908-2_9.
Question: should there be a listing of all the individual Relax NG modules at this point? 5.15.3 (should be 5.15.2?) Drivers => Suites and Drivers Or perhaps 5.15.2 Suites and 5.15.3 Drivers Insert The fine-grained Relax NG modules are assembled into driver schemas through re-usable module "suites", as follows. Core Suites LegalRuleML core suites define the essential features of a LegalRuleML schema, aside from RuleML modules. There are two module suites considered to be at the "core" level, as follows: * "relaxng/suites/core.rnc", the main core suite, * "relaxng/suites/core-basic.rnc", the basic core suite. The basic core suite is a subset of the module in the main core suite, excluding only the prefix module. Basic, Compact, and Normal Suites There are three module suites that expand on the core suites to include serialization aspects: * "relaxng/suites/basic.rnc", the basic suite, expands the basic core suite to include the stripe-skipping module. * "relaxng/suites/compact.rnc", the compact serialization suite, , expands the main core suite to include the "stripe_skipping" module. * "relaxng/suites/normal.rnc", the normalized serialization suite, , expands the main core suite to include the "stripe_optional" modules. LegalRuleML Drivers The Relax NG schemas that are used directly for validation or generation of other artifacts are called "drivers". There are three groups of drivers, according to their purposes, as follows: * Validation drivers are intended to be used directly for validation of LegalRuleML instances. ** "relaxng/lrml-basic.rnc" may be used to validate LegalRuleML instances in the basic dialect. It expands the basic suite with ** "relaxng/lrml-compact.rnc" may be used to validate LegalRuleML instances in the compact serialization ** "relaxng/lrml-normal.rnc? may be used to validate LegalRuleML instances in the normalized serialization * XSD-conversion drivers are intended to be used only for generation of the corresponding XSD schemas, as described in Section 5.16 XSD Schema Generation. ** "relaxng/lrml4xsd-basic.rnc" is the source used to generate the XSD basic dialect schema, "xsd/xsd-basic/lrml-basic.xsd" as well as its companion schema "xsd/xsd-basic/ruleml.xsd" for the RuleML namespace ** "relaxng/lrml4xsd-compact.rnc" is the source used to generate the XSD compact serialization schema, "xsd/xsd-compact/lrml-compact.xsd as well as its companion schema "xsd/xsd-compact/ruleml.xsd" for the RuleML namespace ** "relaxng/lrml4xsd-normal.rnc" is the source used to generate the XSD normalized serialization schema, lrml-normal.xsd as well as its companion schema "xsd/xsd-normal/ruleml.xsd" for the RuleML namespace * Simplification drivers are intended to be used only for generation of the simplified Relax NG schemas, as described in section 5.XX Simplified Relax NG Schema Generation. ** "relaxng/drivers4simp/lrml-basic4simp.rnc" is the source used to generate the basic dialect simplified schema, "simplified/lrml-basic4simp.rnc" ** "relaxng/drivers4simp/lrml-compact4simp.rnc" is the source used to generate the compact serialization simplified schema, "simplified/lrml-compact4simp.rnc" ** "relaxng/drivers4simp/lrml-normal4simp.rnc"is the source used to generate the normalized serialization simplified schema, "simplified/lrml-normal4simp.rnc" 5.16.1 Alternate Drivers To accomplish the automated conversion from Relax NG to XSD, alternate driver schemas were constructed (lrml4xsd-compact and lrml4xsd-normal). These schemas differ from the normative Relax NG schemas only in the following ways: * inclusion of a different module (modules-xsd/id_datatype_ID) defining the type of the key attribute in LegalRuleML elements to be xsd:ID. * inclusion of a different module (modules-xsd/time4xsd) defining the type of <ruleml:Data> within <ruleml:Time> to be xs:any. * inclusion of a different module (modules-xsd/stripe_required_4xsd) defining the Leaf/Branch-type edge elements by a lenient pattern that is exactly expressible in XSD * inclusion of a modified RuleML schema suitable for conversion to XSD. ==> 5.16.1 XSD-Conversion Drivers To accomplish the automated conversion from Relax NG to XSD, XSD-conversion drivers were constructed (lrml4xsd-basic, lrml4xsd-compact, and lrml4xsd-normal). These schemas differ from the normative Relax NG schemas only in the following ways: * inclusion of a different module (modules-xsd/time4xsd) defining the type of the content of <ruleml:Data> within <ruleml:Time> to be xsd:dateTime, xsd:date, or xsd:duration, omitting the explicit implementation of the xsi:type attribute because it is inherently implemented in XSD schemas. * inclusion of a different module (modules-xsd/stripe_required_4xsd) defining the Leaf/Branch-type edge elements by a lenient pattern that is exactly expressible in XSD * inclusion of a modified RuleML schema suitable for conversion to XSD. On 12/17/15 7:17 PM, monica.palmirani wrote: Dear all, |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]