Lists Home |
Date Index |
- From: Peter Murray-Rust <email@example.com>
- To: firstname.lastname@example.org
- Date: Thu, 08 Oct 1998 19:19:52
At 10:34 08/10/98 -0700, David Brownell wrote:
>Peter Murray-Rust wrote:
>> There have been warnings about the complexity of registries - I assume that
>> the xml-ea1 props file is a registry?
>What do you mean by 'registry'? Currently it's just the simplest
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
>A draft I wrote up a while ago defined such bindings in XML syntax
>something like this ...
> <!-- a set of namespace-specific bindings -->
> <element name="reservation">
> <bean class="com.example.app1.Reservation"/>
> <!-- Bean tag actually lets you define properties
> and so on -->
> <!-- ... more element bindings in this namespace -->
> <!-- ... more namespace-specfiic 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.
Looks very promising...
Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
VSMS http://www.nottingham.ac.uk/vsms, Virtual Hyperglossary
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)