← Prev in month ← Prev in thread
Next in thread → Next in month →

RE: [xml-dev] Re: I can XInclude where I [expletive deleted] want to

From
Bullard, Claude L (Len) <>
To
'Uche Ogbuji' <>, "W. E. Perry" <>
Date
2002-04-30T20:19:29Z
ID
<2C61CCE8A870D211A523080009B94E430752B3C2@HQ5>
Thread
RE: [xml-dev] Re: I can XInclude where I [expletive deleted] want to
Len's mouth is usually well-occupied, so thanks for 
not adding to the population explosion. ;-)

It's again, a path dependence issue.  Again

http://www.utdallas.edu/~liebowit/paths.html

Path dependency:  early decisions have effects on later 
decisions (aka, karma).  Knowledge is the determinant 
of fault given sensitive processes.

Degree one:  Information is known but there is no long 
term inefficiency, or the path may be optimal even 
if not uniquely optimal.  No Fault.

Degree two:  Information is imperfect and there is a long 
term inefficiency.  Fault is adjudicated (issues of malice, 
who knew what when, etc).

Degree three:  sufficient information existed to choose correctly 
but the user chooses incorrectly.  Fault to user.

Uche's position is sound in that he provides the option. The 
difference in degree one or two in cases of inefficiency could 
be decided by the warranty of information provided to the user 
as to the possible outcomes of their choices.  Again, this is 
why liquidated damage clauses are inserted into contracts.  It
is important to understand that a contract is itself a set of 
carefully chosen choices given potentials.  It is not a computer 
program in that kama (pleasure) and dharma (duty) affect its 
application.  Humans in the loop.

len

-----Original Message-----
From: Uche Ogbuji [mailto:]

Translation to the pertinent argument: if you construct a source document that 
uses elements in the namespace and with the name reserved by the XInclude 
specification, why on earth would you blame a processor for acting on those 
instructions?  4Suite advertizes itself as an XInclude processor, among other 
things.  Act accordingly.

It's simple.  If you don't want 4XSLT to pergorm XInclude processing on your 
docuemnts, either tell it not to, or don't use XInclude in the first place.  
What does Pyrrhus have to do with it?


-- 
Uche Ogbuji                           Fourthought, Inc.
           http://fourthought.com
http://4Suite.org                     http://uche.ogbuji.net
Track chair, XML/Web Services One (San Jose, Boston): 
http://www.xmlconference.com/
RDF Query using Versa - http://www-106.ibm.com/developerworks/xml/library/x-thi
nk10/index.html
WSDL and the Wild, Wild West - http://adtmag.com/article.asp?id=6004
XML, The Model Driven Architecture, and RDF @ XML Europe - 
http://www.xmleurope.com/2002/kttrack.asp#themodel



-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>
← Prev in month ← Prev in thread
Next in thread → Next in month →