W3C home > Mailing lists > Public > public-rif-wg@w3.org > May 2008

RE: non-RDF-compatible type-tagged XML

From: Alex Kozlenkov <alex.kozlenkov@betfair.com>
Date: Tue, 27 May 2008 13:53:44 +0100
Message-ID: <E39E50172D7A6546BCE3E981C985C9872D6BD7CF@UKMAIL.sportex.com>
To: "Sandro Hawke" <sandro@w3.org>, <public-rif-wg@w3.org>


I want to know more about this option.



-----Original Message-----
From: public-rif-wg-request@w3.org [mailto:public-rif-wg-request@w3.org]
On Behalf Of Sandro Hawke
Sent: 26 May 2008 23:36
To: public-rif-wg@w3.org
Subject: non-RDF-compatible type-tagged XML

Harold mentioned an idea today that was not taken very seriously, but
I think is worth some more consideration, at least to help understand
the lay of the land.  The idea was to make small changes to the XML to
make it self-describing (like RDF), but still not use the RDF

With certain weights for the pro/con factors, this is the best
solution.  Specifically, if you only care about (1) having a
self-describing syntax and (2) avoiding the RDF allergy, then this is
a great option.

Self-description happens to be the factor I care most about
personally, because I want to be able to write straightforward
frame-style rules which operate on the syntax of RIF documents,
instead of having to use XML tools.  I think this will make fallback
transformations much easier to write, but since I haven't actually
done it seriously in either style, I can't be sure.

I'm also very sensitive to the RDF allergy; I don't see it very often,
but when I do see a knee-jerk reaction to RDF, almost a disgust, I
sometimes wish my project (whatever it is at the time) was not
associated with RDF.  Mostly, though, the irrational technology
decisions I see are pro-RDF not anti-RDF.

Anyway -- I don't think these factor weights are widely shared in the
WG, so this option probably doesn't have much support, but I wanted to
at least make the pitch for it as a fallback :-) if we don't end up
with an RDF-compatible XML syntax.

   -- Sandro

[ cf ISSUE-55 ]

In order to protect our email recipients, Betfair Group use SkyScan from 
MessageLabs to scan all Incoming and Outgoing mail for viruses.

Received on Tuesday, 27 May 2008 12:54:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:07:44 UTC