I am simply quoting the term :-). I assumed it was some pangalactic system
for associating names with things. Like FPIs/catalogs etc. Only here, for
classes and elements.
>convention for associating XML Beans ("XObjects") with element names;
>and since it's a flat namespace, it can't plug in to XML namespaces.
>
>Sometimes when folk say "registry" they mean some global database.
>I design such things out of systems every chance I get.
I agree completely. Let's get things working first and design the cosmos
later.
>
>
[...]
>A draft I wrote up a while ago defined such bindings in XML syntax
>something like this ...
>
> <bindings>
> <!-- a set of namespace-specific bindings -->
> <namespace
> uri="http://www.example.com/xmlbeans/app1">
> codebase="xmlbeans.jar"
> >
> <element name="reservation">
> <bean class="com.example.app1.Reservation"/>
> <!-- Bean tag actually lets you define properties
> and so on -->
> </element>
> <!-- ... more element bindings in this namespace -->
> </namespace>
> <!-- ... more namespace-specfiic bindings -->
> </bindings>
This looks as if it should map trivially into XSchema (Ron, Simon???)
XSchema comes out this week, I think - I'm not suggesting it should be
altered to fit this - more that this - along with help could be the first use.
>
>That sketch omits two important features: (a) importing bindngs
>defined for other namespaces, (b) document-specific bindings, such
>as for the "default" namespace or embedded in a document.
XSchema suggestions?
Looks very promising...
P.
Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
net connection
VSMS http://www.nottingham.ac.uk/vsms, Virtual Hyperglossary
http://www.venus.co.uk/vhg