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

>
>>  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.