[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: How could RDDL be distributed ?
- From: "Bullard, Claude L (Len)" <email@example.com>
- To: James Robertson <firstname.lastname@example.org>
- Date: Wed, 17 Jan 2001 08:36:51 -0600
Real world contextualization.
You are bidding a contract for a
project governed by a set of standards or
specifications. An example might be to
produce a new system for your government, a
large systems integrator, etc. The bidding
results in a contract which is the overall
governing record of authority for the project
scoped by time and other considerations such
as payment for performance. The standards or
specifications internally cite other documents
such as a DTD or schema family for the documents
and other data items to be delivered at specified
intervals of project time (eg, by phase) or
clock/calendar time (by date). Note that these
time types scale. During the negotiation, the contract
procurement officer and your contract officer
agree to waive specific requirements in specific
governing documents. They also agree that during the
performance of the project, authorities representing
all parties meet at scheduled times (either project
time or clock/calendar time) to review the
project deliverables and if necessary, to renegotiate
the conditions of the governing documents and make
agreed upon adjustments.
That is real world contextualization for which
you will receive real world money. The description
above is slightly simplified because the collection
of information exchanged during each negotiation must
be accounted for (traceability). Part of the solution
is how you distribute RDDL since it is essentially a
Contract Data Requirements List or CDRL. CDRLs cite
DID (Data Item Descriptions).
Your challenge is to use URIs to represent all of the
above and not open your company up to litigation
based on charges of fraud, misconduct, failure to
deliver, and so forth. Further, you should be able
to prove by URI that your company has bettered the
performance contracted to receive incentive payments.
In some cases, you must be able to drop deliverables
if they have been traded for new requirements discovered
during the course of the performance.
Real world: contextualization by control and feedback.
So called "hotspots" in the system are a symptom of a
problem you can easily solve as long as the name is not the
Intergraph Public Safety
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Michael Mealling [mailto:email@example.com]
Sent: Tuesday, January 16, 2001 10:41 PM
To: James Robertson
Subject: Re: How could RDDL be distributed ?
On Wed, Jan 17, 2001 at 03:23:40PM +1100, James Robertson wrote:
> At 15:04 17/01/2001, Michael Mealling wrote:
> >On Wed, Jan 17, 2001 at 02:19:56PM +1100, James Robertson wrote:
> > > At 03:19 17/01/2001, Michael Mealling wrote:
> > > > > 1. Allow for local overriding of authoritative resources.
> > > >
> > > >IMHO that's the c15n problem space...
> > >
> > > Damn these shortenings of words. They are
> > > causing way too much o9n.
> > >
> > > A few extra letters would kill you?
> >;-) You type it as much as I have and it will get annoying. Plus its
> >what the IETF BOF group was called so its easier to find by using that
> >acronym. But the point is valid. I'll try and spell it out
> >more often. ;-)
> I think you missed my subtle (?) point:
> WHAT DOES IT STAND FOR ?!?
Ah... Sorry. Thought you'd caught the start of the thread...
c15n is short for Contextualization. It's a concept whereby
a URI is resolved based on some locally defined set of context.
In academic research it could be based on research appropriate
copies (edition 1 vs edition 2, photograph vs digitization, etc).
In the cases we have been talking about here it means taking
some URI and resolving it based on your localized concept of
what that URI identifies (i.e. you think you have a better XML
Schema than the owner of the original, you have some locally
cached copy, you don't trust the holder of the URI to not change
the bit of XML underneath you, etc)....
Michael Mealling | Vote Libertarian! |
Sr. Research Engineer | www.ga.lp.org/gwinnett | ICQ#:
Network Solutions | www.lp.org |