{"id":279,"date":"2004-02-14T15:51:00","date_gmt":"2004-02-14T19:51:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=277"},"modified":"2004-02-14T15:51:00","modified_gmt":"2004-02-14T19:51:00","slug":"and-again-and-again","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2004\/02\/and-again-and-again\/","title":{"rendered":"And again, and again &#8230;"},"content":{"rendered":"<p><a href=\"http:\/\/webpages.charter.net\/chrisfer\/archives\/2004_02_01_oldrants.html#107679345917142953\">Chris Ferris writes<\/a>\nin response to my suggestion that processing an XML document is an all-or-nothing proposition;<\/p>\n\n<blockquote>\nI don&#8217;t see it that way. Understanding an XML document is not an all-or-nothing proposition by any stretch of the imagination. For instance, I can have a generic SOAP processor that understands the SOAP namespace but is oblivious to the content of the soap:Body element (amongst other things such as certain SOAP headers).[&#8230;]\n<\/blockquote>\n\n<p>I see the disconnect.  I&#8217;m referring to <em>any\/all XML document(s)<\/em>.\nNo fair saying that some <em>specific<\/em> kinds of XML documents are partially\nunderstandable, because clearly you can design one to be, and SOAP, as an envelope,\nis one as you correctly point out.<\/p>\n\n<p>So, consider this XML document;<\/p>\n\n<pre>\n&lt;iwoejaf xmlns=\"http:\/\/example.org\/oijerwer\"&gt;\n  &lt;ijrwer&gt;inm4jvxc&lt;\/ijrwer&gt;\n&lt;\/iwoejaf&gt;\n<\/pre>\n\n<p><em>That&#8217;s<\/em> the kind of document I&#8217;m talking about.  Wouldn&#8217;t you say that\nunderstanding that document is all or nothing?  You either recognize the namespace or\nyou don&#8217;t, right?  Well, that&#8217;s not the case with RDF\/XML since it gives you\n<a href=\"http:\/\/www.w3.org\/TR\/NOTE-webarch-extlang#Requirements\">&#8220;partial understanding&#8221;<\/a>;\nif that document above were known to be RDF\/XML\n(and it <a href=\"http:\/\/www.markbaker.ca\/2002\/09\/Blog\/2003\/10\/10#2003-10-rdf-and-xml\">is valid RDF\/XML<\/a>),\nthen an RDF\/XML processor can extract information from it piece-meal (in triples).\nNow, maybe none of the terms in any of the triples will be recognizable, but perhaps if you\n<a href=\"http:\/\/esw.w3.org\/topic\/WebClosure\">dereference the URI for each of the terms in those triples<\/a>,\nyou&#8217;ll find that the terms you don&#8217;t know are related to ones you do.<\/p>\n\n<p>Now can you see why TimBL is so keen to see folks use RDF\/XML?  It&#8217;s the answer to\nthe <a href=\"http:\/\/www.pacificspirit.com\/Authoring\/Compatibility\/ProvidingCompatibleSchemaEvolution.html\">schema evolution problem<\/a>.<\/p>\n\n<blockquote>\nHTTP is a great application protocol, for the application for which it was designed&#8230; the Web.\n<\/blockquote>\n\n<p>Finally, something we can agree on! 8-)  Now, if only you understood what the Web\nwas, and was capable of, we&#8217;d be all set.<\/p>","protected":false},"excerpt":{"rendered":"Chris Ferris writes in response to my suggestion that processing an XML document is an all-or-nothing proposition; I don&#8217;t see it that way. Understanding an XML document is not an all-or-nothing proposition by any stretch of the imagination. For instance, I can have a generic SOAP processor that understands the SOAP namespace but is oblivious [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[26,40],"class_list":["post-279","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-soap","tag-xml"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/279","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/comments?post=279"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/279\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=279"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=279"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=279"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}