[
Lists Home |
Date Index |
Thread Index
]
> At 03:51 PM 8/4/2002 -0400, Liam Quin wrote:
> >The XML way to do this, I claim, is
> ><zoo>
> > <name>Utica Zoo</name>
> > <lat>
> > <deg>75</deg>
> > <min>15</min>
> > </lat>
> > <long>
> > <deg>43</deg>
> > <min>05</min>
> > </long>
> ></zoo>
> >
> >Now you can represent both lat and long in W3C XML Schema.
So let me ask Liam this: if this is such a hunky dory approach, why was date
not defined as
<date>
<year>2002</year>
<month>08</month>
<day>04</day>
</date>
Why did we need gDate and co?
The dead simple answer is that if <lat>75°15'00" N</lat> is what I want in my
data, then
<lat>
<deg>75</deg>
<min>15</min>
</lat>
is a contrivance and a distortion, and a schema language that requires me to
resort to this before I can take advantage of the most effective processing
tools is blinkered.
--
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Track chair, XML/Web Services One Boston: http://www.xmlconference.com/
Basic XML and RDF techniques for knowledge management, Part 7 -
http://www-106.ibm.com/developerworks/xml/library/x-think12.html
Keeping pace with James Clark - http://www-106.ibm.com/developerworks/xml/libra
ry/x-jclark.html
Python and XML development using 4Suite, Part 3: 4RDF -
http://www-105.ibm.com/developerworks/education.nsf/xml-onlinecourse-bytitle/8A
1EA5A2CF4621C386256BBB006F4CEC
- References:
- Re: maps
- From: "Simon St.Laurent" <simonstl@simonstl.com>
|
