Lists Home |
Date Index |
- From: Len Bullard <firstname.lastname@example.org>
- To: Tim Bray <email@example.com>
- Date: Tue, 09 Nov 1999 20:54:55 -0600
Tim Bray wrote:
> At 06:18 PM 11/9/99 -0600, Len Bullard wrote:
> >How can a namespace enable us to discover a record of authority by
> >which we may determine which variant or subset of the definition
> >is in effect for some time slice of a process?
> It can't. Yes, we need a way to do this, but namespaces weren't designed
> for this and they won't do the job.
We need a means to name aggregate namespaces.
That is the level of definition required to
name complex document types for business.
Whatever a namespace is lexically, in practice,
it appears to be the name or near name of the contract
depending on how you feel about FPIs.
As spec'd, no. As applied? The
namespaces I see are system application
identifiers mapping to vendor framework objects.
If I buy an object from a business, they control the
record of authority for the item I purchase.
Yes, not all namespace names are ROA, but some
are. In these cases, it seems the business
transaction is one where that is better to
know apriori. That is why FPIs were important.
It is the Published name. The objection in
TimBLs Myth's paper on names and location is the
ultimate need for an authoritative registry.
Outermost parentheses are systemic.
So... we leave it to BizTalk and OASIS to
fight over until someone is left standing?
Ok. Keiretsu it is: businesses defined
by their registered namespaces in publically
controlled, owned and operated registries.
How do they aggregate?
The URI/URN may not have to directly map to
the FPI, but if not, should map to something
that lets me find one. LexicalClarifier or
not, it looks like a URL. Click. If not
by spec, then by common practice. Maybe
the easiest thing is to use the FPI on the
right side of the colon.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)