From 2e90c0b30f1addb3ef46c4da64d6d37e0a65318b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Holger=20Wei=C3=9F?= Date: Mon, 4 Jul 2011 17:21:03 +0200 Subject: Allow nested Bundle tags in XML Schema Nesting Bundle tags is now allowed in order to support XInclude within Bundles. --- schemas/bundle.xsd | 213 +++++++++++++++++++++++++++++------------------------ 1 file changed, 115 insertions(+), 98 deletions(-) diff --git a/schemas/bundle.xsd b/schemas/bundle.xsd index c0a7e08ac..2dd77e9af 100644 --- a/schemas/bundle.xsd +++ b/schemas/bundle.xsd @@ -110,6 +110,14 @@ + + + + Nesting Bundle tags is allowed in order to support + XInclude within Bundles. + + + @@ -135,7 +143,113 @@ - + + + + + + Abstract implementation of a Package entry. The full + specification will be included in Rules. + + + + + + + Abstract implementation of a Path entry. The entry will + either be handled by Cfg, TGenshi, or another + DirectoryBacked plugin; or handled by Rules, in which case + the full specification of this entry will be included in + Rules. + + + + + + + Abstract implementation of a Service entry. The full + specification will be included in Rules. + + + + + + + Abstract implementation of an Action entry. The full + specification will be included in Rules. + + + + + + + Fully bound description of a software package to be managed. + + + + + + + Fully bound description of a filesystem path to be handled + by the POSIX driver. + + + + + + + Fully bound description of a system service to be managed. + + + + + + + Fully bound description of a command to be run. + + + + + + + Elements within Group tags only apply to clients that are + members of that group + + + + + + + Elements within Client tags only apply to the named client + (or vice-versa; see #element_negate below) + + + + + + + Nesting Bundle tags is allowed in order to support + XInclude within Bundles. + + + + + + + + + + + + + + + + + + + + A bundle describes a group of inter-dependent configuration @@ -150,102 +264,5 @@ that a given client will receive. - - - - - - Abstract implementation of a Package entry. The full - specification will be included in Rules. - - - - - - - Abstract implementation of a Path entry. The entry will - either be handled by Cfg, TGenshi, or another - DirectoryBacked plugin; or handled by Rules, in which case - the full specification of this entry will be included in - Rules. - - - - - - - Abstract implementation of a Service entry. The full - specification will be included in Rules. - - - - - - - Abstract implementation of an Action entry. The full - specification will be included in Rules. - - - - - - - Fully bound description of a software package to be managed. - - - - - - - Fully bound description of a filesystem path to be handled - by the POSIX driver. - - - - - - - Fully bound description of a system service to be managed. - - - - - - - Fully bound description of a command to be run. - - - - - - - Elements within Group tags only apply to clients that are - members of that group - - - - - - - Elements within Client tags only apply to the named client - (or vice-versa; see #element_negate below) - - - - - - - - - - - - - - - - - - -- cgit v1.2.3-1-g7c22