[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
Archaeology Materials and Database Manager,
Archaeology Technologies Laboratory (ATL),
North Dakota State University (NDSU).
Ph. 701-231-7115 FAX: 701-231-1047
Email: james.landrum@ndsu.nodak.edu <mailto:james.landrum@ndsu.nodak.edu>
ATL Web Site: http://atl.ndsu.edu <http://atl.ndsu.edu>
Digital Archive Network for Anthropology and World Heritage (DANA-WH)
DANA-WH Web Site: http://www.dana-wh.net <http://www.dana-wh.net>
------_=_NextPart_001_01C3F1B7.2F17434E
Content-Type: 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">
<TITLE></TITLE>
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>It's
hard to say. The push to web services is really happening. On the
other hand, </FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>the
release of the next generation MS system with Longhorn, Indigo etc is won't
</FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>happen
for another two or three years. That's a long time. If you are
asking about </FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff
size=2>tightly focused apps such as we build for public safety, that's about two
years away </FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>before
we do really noticeable bits although some bits we do today, and we are
</FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>in a
late adopter industry. The bigger event that isn't mentioned
in that prediction </FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>is the
convergence of web services and GPS to enable ever more interesting geolocation
</FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>based
services based on user preferences. That is why the distributed
identity apps </FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>are
appealing to some, but they scare others. I suspect that 2010 is a good
round </FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>SWAG
for this stuff, but I am often surprised as the speed with which these things
</FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff
size=2>happen. When I was asked in the eighties what all these
'feedback mediated </FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff
size=2>systems' based on global hypermedia systems would do, all I could reply
was, </FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff
size=2>"Things will speed up and evolution is one of those things. There
are dangers."</FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>We are
in a bewildering time of propagandized paranoia and rapid uptake of
</FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff
size=2>NotReadyForPrimeTime technologies. I don't even have a cell
phone but it </FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff size=2>is
because I am a) cheap and b) don't want a digital leash or c) more
data.</FONT></SPAN></DIV>
<DIV><SPAN class=103561722-12022004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=103561722-12022004><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>-----Original Message-----<BR><B>From:</B> James Landrum
[mailto:james.landrum@ndsu.nodak.edu]<BR><BR></FONT></DIV>Thanks Len,<BR>Good
tight discussion of the issues, and muchly appreciated.<BR> I suppose I
should have also specified concerns regarding the actualy timeline (by 2010),
and am wondering if in the interim since the report was published, (December
2002) if things have changed in the industry that would either (1) shorten the
timeframe by one or more years (circa 2008-2009) or sooner, or (2)
extend the timeframe (2011-2012)? <BR><BR>Bullard, Claude L (Len) wrote:<BR>
<BLOCKQUOTE
cite=mid15725CF6AFE2F34DB8A5B4770B7334EE03F9F33E@hq1.pcmail.ingr.com
type="cite">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>It
is but it is unremarkable as predictions go:</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>1. One reason to build a data warehouse is to shield enterprise
systems from the Internet. </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>Putting mission-critical systems on today's Internet is a profoundly
risky idea given DDoS. </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>See replication and isolation: inside the Intranet and on the
Internet.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>2. Using a single application may or may not mean a single
database. Usually it doesn't. </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>Large system database builders recognize the need to
replicate. Otherwise, locking </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>problems are deadly at some n scale (some relational databases are
better than others </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>at
locking).</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>3. The generalizations in that description are vast. "The
world of tomorrow will have many </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>more people in it." D'oh. Yes, the bandwidth is a
problem. D'oh.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>4. What does 'customized access to data in real time'
mean? In other words, a report </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>is
a report is a report. A form is a form is a form. Are
either 'customized in real time' </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>or
do programmers customize forms, deliver them, and then the data they 'get'
or 'post' </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>or
'put' is returned in 'real time' minus network hops, minus processing time
on the </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>server, minus traffic conditions, and so on?</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>5. Data that is not validated before it is stuffed into a
database is dangerous data. </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>Full stop. ALL business databases use some form of business
rules on the client or the </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>server or both validate data. Sometimes they validate it,
then pull it back out </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>and send it to another system (think Federal reporting of crime
statistics) </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>which revalidates it. Again, d'oh. So
what is the role of synchronization? I can </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>guess but enough.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>It's valid in the sense that yeah, that's what we do with
databases. How web services </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>changes that is a mystery. Wireless is just another device with
possibly server-side </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>XSLT or other means to make the package sent to it light enough to
process.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>A
service-oriented architecture is a big API for exchanging documents be it
change </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>orders, contracts, or geek love letters. One can adopt an
RPC approach to that, </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>but all the Internet knows is bits on the wire and all the WWW adds
are ways to </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>name those bits on the wire so they can be located, then put, get,
posted,. and you </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>get the idea. We used to call these Document
architectures before that quit being </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>trendy. As a thought experiment, try to visualize a set
of services that an enterprise </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>can perform digitally and determine how many of those are not reliant
on sending and </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>receiving documents. I want to know the time.
Fine. Does it send me a clock? Does </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>it
send me a timestamp? Does it send me a message instructing the clock
on my machine </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>to
display the time?</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>The idea behind web services at the base is to expose parts of a
database via a set </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>of
ports with named resources such that anyone can write a client to
them. The hope is </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>that a client can then aggregate information from multiple sources,
organizations, etc. </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>for a specific view. Think tight fusion from loosely
organized sources. If you think </FONT></SPAN></DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff size=2>in
HumanML or ontology terms, there are some semantic issues with doing
that.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=986093021-12022004><FONT face=Arial color=#0000ff
size=2>len</FONT></SPAN></DIV>
<DIV><FONT face=Tahoma><BR><FONT size=2><SPAN class=986093021-12022004><FONT
face=Arial color=#0000ff> </FONT></SPAN>-----Original
Message-----<BR><B>From:</B> James Landrum [<A class=moz-txt-link-freetext
href="mailto:james.landrum@ndsu.nodak.edu";>mailto:james.landrum@ndsu.nodak.edu</A>]<BR><B>Sent:</B>
Thursday, February 12, 2004 3:29 PM<BR><B>To:</B> Human
Markup<BR><B>Subject:</B> [huml] is this a valid
prediction?<BR><BR></FONT></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">reference:<BR>
<P class=MsoNormal>Betts, Mitch. 2002. “More Predictions on the Future of
Mobile/Wireless Computing.” ComputerWorld Magazine, <ST1:DATE year="2002"
day="16" month="12">December 16, 2002</ST1:DATE>. ComputerWorld, Inc. <A
class=moz-txt-link-freetext
href="http://www.computerworld.com/mobiletopics/mobile/story/0,10801,76656p2,00.html";>http://www.computerworld.com/mobiletopics/mobile/story/0,10801,76656p2,00.html</A><O:P></O:P></P><BR>Quote:<BR><SPAN
class=storybody>The marriage of Web services and mobile devices will have
powerful implications for enterprise users and IT managers. It will give
them customized access to relevant data in real time. For example, remote
sales distributors using handheld devices in the field could use a single
application that could access inventory records, price lists and customer
profitability statements without having to build a huge data warehouse.
Also, synchronizing data through a Web services interface allows the
application to validate the data before writing it directly to the
database, which is critical to maintaining data integrity. However, the
limitations of current network connections will prevent the use of Web
services for thin mobile applications until after 2010. <I>-- Joe Owen,
chief technology officer, XcelleNet Inc., Alpharetta, Ga.</I></SPAN><BR><PRE class=moz-signature cols="72">--
</PRE></BLOCKQUOTE></BLOCKQUOTE><BR><PRE class=moz-signature cols="72">--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]