Cart
|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: U.S. Federal Goverment's Data Reference Model (DRM) XMLSch
 Len,
I am
quite interested in statistics on the
timeframes from product availability to implementations. Do you have any
relevant data? For example, how long it actually took from the time
major vendors like Oracle started to support XML to first
implementations?
I also wonder how much (if at
all) release timings matter. Some people I talked to say that most
government sites are still running on Oracle 9i, but plan to move to 10g once
Version 2 is available. The logic being that they never go to version 1 of the
major release. It just so happens that 10g Version 2 is the upcoming release
with RDF support. I guess we will start to see soon what impact it
has.
I can't answer a question of what you can do with rdf:id in
the DRM. I do not know. Btw, we've done other FEA models in RDF/OWL. They are
available at: http://www.osera.gov/owl/2004/11/fea/FEA.owl
As far is GJXML goes, it effectively invents its own
version of RDF with things like:
<xsd:attribute name="name" type="xsd:QName" use="required" /> <xsd:attribute name="subject" type="xsd:IDREF" use="required" /> <xsd:attribute name="object" type="xsd:IDREF" use="required" /> </xsd:complexType>
Regards,
Irene From: Bullard, Claude L (Len) [mailto:len.bullard@i...] Sent: Friday, June 24, 2005 12:42 PM To: 'Irene Polikoff'; 'Chiusano Joseph'; xml-dev@l... Subject: RE: U.S. Federal Goverment's Data Reference Model (DRM) XML Schema Thanks for the
information, Irene.
So if you are seeing the betas now, procurement
catches up in say three years,
implementations appear at the earliest, two years after
that.
At five years
ahead, the costs for this won't be seen until the first
half
of the first term of the next administration. And that is definitely
synonymous with Federal. That
doesn't answer the questions of what we do with the rdf:id that we
wouldn't do
with
another semantic for an id. Let's talk for a minute about the
impact
of costing systems using these specs. Remember, it's useful to
have
an RFP
say "Comply with" without some means of showing how to comply
with
it.
GJXML
is a good example. Today the RFP says "comply with"
and
then leaves it to the local procuring agency to figure out how to determine
compliance. The GJX... IEP is better because it requires
the actual subset work
to be
performed, a URI-identified instance of the schema to be produced
as a
Reference Schema, and possibly, the agency or State level instance
of
that. Now we have a definition (eg, incident-AL.xsd) that can be cited
and
validated. Note carefully: every one of these processes is bid
at
consultant rates every time the customer asks for it. Until the
agency-
selected IEP emerges, the system procured remains in implementation
phase
and does not cutover to live operations.
How
long will an agency wait before the system goes live? Answer:
about
six to 12 months, but usually less than a year. Local budgets
and
political priorities won't take the pressure of long
rollouts.
The
world is festering with meta-specs. They are decidedly expensive
items
to chuck into an RFP.
len
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||
