OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] XML Data Modellling/Linking (was RE: [xml-dev] After XQuer

[ Lists Home | Date Index | Thread Index ]

Data Access Layers are about "abstracting away from the 
presentation as much as one can".  XML isn't.  XML 
doesn't care.   It's just good practice 
from a particular point of view that is shared 
by a lot of people.  But it is a myth that XML 
is 'about' anything except a common syntax.  
Wishing it were otherwise won't make it so. 

I agree about URI theology, but it is also basic 
to web architecture.  It is a neat solution until 
someone asks us to define 'resource' and we discover 
there is no 'there' there.  


From: Michael Kay [mailto:michael.h.kay@ntlworld.com]

But XML is about abstracting away from the presentation as much as one
possibly can, and to my mind XLink doesn't do that.

Part of the problem, I think, is the focus on URIs as identifiers (and
links). I've heard a number of talks recently advocating that we should use
URIs whenever we want to identify anything, and I simply don't think that's
the right direction. To my mind <postcode>RG4 7BS</postcode> is a perfectly
good identifier (for a small piece of geography in which my house is found),
and any technology that requires me to write it differently if I'm going to
use it for linking purposes is too constraining.

Even in the document world, authors should be encouraged to write
<postcode>RG4 7BS</postcode> without too much thought about the fact that in
one particular application, hovering the mouse over it might show you a map.


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS