Re: [relax-ng-comment] Wildcard mechanism for include

[James Clark <jjc@jclark.com>]

The value of href is a URL.  Wildcards in URLs don't generally make sense.
You can't ask an HTTP server to find all the URLs that match a particular
wildcard all even all the URLs in a particular directory.  This makes sense
only with file URLs not with HTTP URLs (though maybe WebDAV extensions could
help, but I certainly wouldn't want RELAX NG to depend on these).

---- Original Message -----
From: "Peter Wilson" <pwilson@gorge.net>
To: <relax-ng-comment@lists.oasis-open.org>
Sent: Saturday, December 08, 2001 10:52 PM
Subject: [relax-ng-comment] Wildcard mechanism for include


> I am trying to code the Mozilla XUL syntax into a Relax NG schema.
>
> It looks like it will be common practice in large schema's to have a
> list
> of <includes> in the master document which reference a set of modules.
> (see the xhtml.rng definition on the Oasis web site).
>
> XUL is no different, but has the additional twist that users can define
> new widgets(modules) using xbl so the schema must be open-ended.
>
> Suggestion:
>
> Allow a wild card character in the include href parameter:
>
>     <include href="modules/*.rng"/>
>
> <aside>
>     I know this breaks the definition of URI, so other alternatives to
> the same effect could be used.
>         <include href="modules/?*.rng"/> or
>         <include href="modules/" documents="*.rng"/>
> </aside>
>
> This would allow an unknown number of modules to be included without the
>
> need to modify the master document.
>
> This is especially important in an IDE environment where the ability to
> introduce a new widget - and then have it validated correctly - is
> essential.
>
>
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
>
>