[
Lists Home |
Date Index |
Thread Index
]
> >> So when do we stop relying on idiom and switch to markup?
> >
> > It is a choice made every day by document designers.
> > What level of granularity to use. What are their expectations on
> > the libraries and parsing that will be available at the receiving end.
>
> Unfortunately this leads to (at least) two things: the requirement of
> complex technologies to comprehend the text values; assumptions that data
> types correspond to text values.
I would re-write this as:
* The requirement of technology for parsing text
I guess "complex" is relative, and if by "comprehend" you mean some sort of AI
thingie, I don't see why. All it takes is parsing text. People do this all
the time in their sleep. This is a requirement that doesn't bother me at all.
* The expression of rules to relate text to data types
This is exactly what I've been wanting, so again I don't see a down side.
--
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
|
