Manybubbles added a comment.
In https://phabricator.wikimedia.org/T89949#1052955, @mkroetzsch wrote:
> In https://phabricator.wikimedia.org/T89949#1052731, @daniel wrote:
>
> > Nik tells me that the HA features in Virtuoso are only available in the
> > closed source enterprise version. That basi
mkroetzsch added a comment.
In https://phabricator.wikimedia.org/T89949#1052731, @daniel wrote:
> Nik tells me that the HA features in Virtuoso are only available in the
> closed source enterprise version. That basically means WMF is not going to
> use it in production.
Yes, I guessed that th
daniel added a comment.
Nik tells me that the HA features in Virtuoso are only available in the closed
source enterprise version. That basically means WMF is not going to use it.
TASK DETAIL
https://phabricator.wikimedia.org/T89949
REPLY HANDLER ACTIONS
Reply to comment or attach files, or
mkroetzsch added a comment.
> We are, indeed, playing with the idea of a SPARQL endpoint now...
Interesting. Virtuoso is your best bet in terms of performance. It should be
able to handle the data volume without too much problems. Not sure about the
query volume. It has an open source version
daniel added a comment.
> unless of course you are returning query results in RDF so that these results
> would turn into another kind of RDF export that needs to be consistent with
> those we have now
We are, indeed, playing with the idea of a SPARQL endpoint now...
TASK DETAIL
https://ph
mkroetzsch added a comment.
Now my reply was so long that the ticket has already been closed in the
meantime :-D Anyway, those are my two (or more) cents on this topic ;-) I don't
think the paper goes into these topics very much (as they are not so much
technical as philosophical).
TASK DETAI
mkroetzsch added a comment.
Thanks for adding Denny. Long reply, but details matter here.
I agree that there are different things one could talk about (document, real
thing). However, for now I am mainly interested in talking about the latter,
since this should be our primary concern in Wikibas
Denny added a comment.
No, /entity/Q23 is not the description, indeed, it is the item.
Refer also to http://korrekt.org/papers/Wikidata-RDF-export-2014.pdf (as per
IRC chat).
TASK DETAIL
https://phabricator.wikimedia.org/T89949
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !c
daniel added a comment.
Denny: fine. But then we are //not// talking about the description, but the
thing when using /entity/Q23. So if we want to say the description //has// a
statement, we need to use /wiki/Special:EntityData/Q23.
TASK DETAIL
https://phabricator.wikimedia.org/T89949
REPLY
Denny added a comment.
/entity/Q23 rdf:type wikibase:Item .
wikibase:Item is the set of all things that have a QID. I.e. the real Adam
Weish... George Washington is identified by /entity/Q23 and he is a
Wikibase-Item.
I would also suggest to close this as WAI or invalid.
TASK DETAIL
https:
daniel added a comment.
Of course, we can just say that George Washington actually //is// a
wikidata:Item in "the real world". Then the RDF would be correct. But then we'd
still //not// be talking about the description. In particular, statements apply
to the real world thing, not the descriptio
daniel added a comment.
> In neither case are we referring to the HTML page or any other electronic
> document.
That's our basic disagreement. We actually do have separate URIs for the
document/description and the thing as such. We also make separate statements
about these, in RDF. It would b
daniel added a comment.
Thanks for your input, Markus!
> things that are of rdf:type Item are things that are described by on item on
> Wikidata
So, what type would the description have? schema:Dataset seems a bit broad...
> I think confusion is very unlikely here since we do not export any R
Smalyshev added a comment.
So, what should the dump look like? Nothing is a wikibase:Item, something else
is a wikibase:Item ? If we think that entity:Q23 is the thing, should we have
`entity:Q23 a entity:Q5`? Should we drop `data:Q23 a schema:Dataset`?
TASK DETAIL
https://phabricator.wikime
mkroetzsch added a comment.
The RDF should certainly contain information about the entity type of exported
data. This is essential to ensure that the RDF data contains all the
information that is found in the JSON (other than the ordering). As I read it,
things that are of rdf:type Item are thi
15 matches
Mail list logo
