Cart
[Home] [By Thread] [By Date] [Recent Entries]
> 3) Allow you to apply semantic rules for a namespaced element that are > specified in another document. 95% of the arguments in these threads are > about the semantics, but XML is about syntax, not semantics. So can we just > drop all these other arguments, please? If someone wants to put up a set of > recommended semantic practices for xml, that is fine and can even be useful, > just like best practices for code layout and commenting can be extremely > useful. I'm confused. 90% of what I've seen in the XMLNS branch of this thread is syntax, not semantics. As I see it, the namespace name that gets reported when a processor comes across an attribute is a matter of syntax. How it's interpreted is the semantics, and I don't think anyone has really brought that up (nor would I expect anyone to bring it up). I see the namespace and local name of the nodes as the lexical tokens on which I build my semantic apps. After all, as a programmer, this is one of the things that attracted me to XML. Then again, one man's syntax is another's semantics (are function names tokens or symbols?: it depends on your vocabulary and what is practical for your implementation: do you bloat the scanner, or do you incur the run-time over-head of a symbol table lookup?). But it is certainly not undisputed fact that we're not dicsussing syntax here. -- 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
|
