[prev in list] [next in list] [prev in thread] [next in thread]
List: xml-dev
Subject: RE: [xml-dev] U.S. Federal Goverment's Data Reference Model (DRM) XML Schema
From: "Bullard, Claude L (Len)" <len.bullard () intergraph ! com>
Date: 2005-06-24 16:41:34
Message-ID: 15725CF6AFE2F34DB8A5B4770B7334EE072070AF () hq1 ! pcmail ! ingr ! com
[Download RAW message or body]
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
From: Irene Polikoff [mailto:irene@topquadrant.com]
[len] Show the support for RDF in the major commercial software frameworks.
Next version of Oracle 10g to be released this summer has RDF/S built in. I
can attest that they've done a good job at supporting the standard (we've
been beta testing the product). Some OWL support is currently being worked
on.
Software AG (vendor of XML database Tamino) supports RDF and OWL. They've
recently integrated Ontoprise's Ontobroker engine into Tamino.
Adobe has had RDF support for quite some time now.
I've heard rumors that IBM will announce something by the end of the year -
but these are just rumors.
Regards,
Irene
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2900.2668" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2><SPAN
class=705172816-24062005><FONT face=Arial color=#0000ff size=2>Thanks for the
information, Irene.</FONT></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2><SPAN
class=705172816-24062005></SPAN></FONT></SPAN> </DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2><SPAN
class=705172816-24062005></SPAN>So if you are seeing the betas now, procurement
catches up in say three years, </FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2>implementations appear at the earliest, two years after
that. </FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2><SPAN
class=705172816-24062005><FONT face=Arial color=#0000ff size=2>At five years
ahead, the costs for this won't be seen until the first </FONT></SPAN></DIV>
<DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>half
of the first term of the next administration. And that is definitely
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2>synonymous with Federal.</FONT></SPAN></DIV></FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>That
doesn't </FONT></SPAN><SPAN class=705172816-24062005><FONT face=Arial
color=#0000ff size=2>answer the questions of what we do with the rdf:id that we
wouldn't do </FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>with
another semantic for an id. Let's talk for a minute about the
impact </FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2>of costing systems using these specs. Remember, it's useful to
have </FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>an RFP
say "Comply with" without some means of showing how to comply
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>with
it. </FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>GJXML
is a good example. Today the RFP says "comply with" </FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>and
then leaves it to the local procuring agency to figure out how to determine
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2>compliance. The GJX... IEP is better because it requires
the actual subset work </FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>to be
performed, a URI-identified instance of the schema to be produced
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>as a
Reference Schema, and possibly, the agency or State level instance
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>of
that. Now we have a definition (eg, incident-AL.xsd) that can be cited
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>and
validated. Note carefully: every one of these processes is bid
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>at
consultant rates every time the customer asks for it. Until the
agency-</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2>selected IEP emerges, the system procured remains in implementation
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>phase
and does not cutover to live operations.</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>How
long will an agency wait before the system goes live? Answer:
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>about
six to 12 months, but usually less than a year. Local budgets
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>and
political priorities won't take the pressure of long
rollouts.</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>The
world is festering with meta-specs. They are decidedly expensive
</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff size=2>items
to chuck into an RFP.</FONT></SPAN></DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=705172816-24062005><FONT face=Arial color=#0000ff
size=2>len</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2><BR><B>From:</B> Irene Polikoff
[mailto:irene@topquadrant.com]<BR></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2>[len] Show the
support for RDF in the major commercial software
frameworks. </FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT> </DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2>Next version of Oracle 10g to be released this summer has
RDF/S built in. I can attest that they've done a good job at
supporting the standard (we've been beta testing the product). Some OWL
support is currently being worked on.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2>Software AG (vendor of XML database Tamino) supports
RDF and OWL. They've recently integrated Ontoprise's Ontobroker engine into
Tamino.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2>Adobe has had RDF support for quite some time
now.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2>I've heard rumors that IBM will announce something by the
end of the year - but these are just rumors.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=894263115-24062005><FONT face=Arial
color=#0000ff size=2>Irene</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma color=#000000
size=2><STRONG></STRONG></FONT> </DIV></BLOCKQUOTE></BODY></HTML>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic