W3C home > Mailing lists > Public > public-lod@w3.org > December 2009

Re: DBTropes.org, a TVTropes.org linked data wrapper

From: Daniel O'Connor <daniel.oconnor@gmail.com>
Date: Mon, 14 Dec 2009 00:13:41 +1030
Message-ID: <106cc1200912130543p47ff5e96h1250b7d5f2a7b2a3@mail.gmail.com>
To: Kingsley Idehen <kidehen@openlinksw.com>
Cc: Malte Kiesel <malte.kiesel@dfki.de>, public-lod@w3.org
>
>>  Daniel,
>
> What's the aversion to simply thinking in SPARQL re. Freebase?
>

I can think in both, MQL just is more readily accessable to me and with the
freebase query editor, more easily learned.


>
> Freebase folks: Why not provide a SPARQL option (basically a SPARQL to MQL
> translator if mapping to your lower level APIs isn't a short term option) ?


It's not impossible, but there are nice bits of freebase which might be hard
to map. IE, freebase automagically guesses if you wanted the dc:title of the
thing or the freebase:id of it.

{
  "id": null,
  "type": "/location/city",
  "population": null,
  "name": "/en/adelaide/"
}

will return a population of X

{
  "id": null,
  "type": "/location/city",
  "population": {
     "id": null,
     "name": null,
     "measured_date": null
  },
  "name": "/en/adelaide/"
}

will return a structured object.


SPARQL on the other hand doesn't necessarily act as kindly to the novice
user.

Again, it's probably quite possible, but would scare me to try and
implement.
Received on Sunday, 13 December 2009 13:44:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 13 December 2009 13:44:14 GMT