[
Lists Home |
Date Index |
Thread Index
]
As I cannot get to the challenge :), I will talk about the pre-challenge
portion.
I think syntax is only 1 of the problems with RDF - but definitely a
problem. RPV makes syntax better, but not sure if it works..
Other problems with RDF as mentioned --
1. Even if I know the "predicate", I have to look up and find out the
predicate.
2. for RPV, where R and V are both URIs, there is a confusion between
whether we should write RPV or VPR -- this will be a problem, probably the
predicate explanation will have to include this, with examples..
Who can benefit from inferencing supported? - I believe domains where
people do not mind doing this bit of extra work, provided they get lot of
benefit. I think data (and not metadata) describing symptoms of diseases,
and symptoms of symptoms etc in the medical domain from different parts of
the world/different hospitals etc??
best, murali.
Note; In RDF Schema, I am curious why subproperties do not talk anything
about domain and range being subclasses.. To ensure that the logic stays
in first-order? I am not sure if this will affect a lot, when do we need
subproperties/subclasses in the first place?? Not in the application
domains that I am thinking of??
On Wed, 10 Nov 2004, Dave Beckett wrote:
> On Tue, 09 Nov 2004 22:32:22 -0800, Ronald Bourret
> <rpbourret@rpbourret.com> wrote:
>> Tim Bray wrote:
>>> Just a reminder that the RDF.net challenge is still open: see
>>> http://www.tbray.org/ongoing/When/200x/2003/05/21/RDFNet (you can skip
>>> all the history and markup-pedantry and jump to the challenge itself, at
>>> the bottom of that essay). -Tim
>>
>> I read the history and markup-pedantry and skipped the challenge :)
>
> <snip/>
>
> I read it all and decided XML couldn't even meet the challenge at that point
> after 5 years of XML.
>
> Maybe, just *maybe* RSS with some aggregator (web based or otherwise)
> would meet that, a year or so later, for XML. I wouldn't say it's a
> brilliant XML
> format - it's not even 1 format and you especially have to hold your nose
> if you look at all the &-escaping and encoding issues.
>
> Dave
|
