I would certainly support this proposal or can even
propose it. Would it
also be an idea to do the narrow equivalent, at the same time?
Any
objection to naming them broad and narrow match, to reflect the mapping
relations in SKOS?
I object to this. "broad match" and "narrow match" are used to
compare
concepts, and "super class" and "subclass" to compare classes. It
could
make sense to say that C1 is a sub class of C2 if all instances of C1 are
also instances of C2 even if the concept C1 is not related to C2.
I believe that not having a specific property for
schema.org is actually
more convenient. Having one would mean to use qualifiers to replace the
different possible relations subClassOf, equivalentClass, superClassOf,
subPropertyOf, equivalentProperty, superPropertyOf, narrowMatch, exactMatch
and broadMatch and require people querying the data to always take care of
them.
Restricting to only
schema.org is fast and easy in SPARQL with
FILTER(STRSTARTS(STR(?url), "http://schema.org"))
Cheers,
Thomas
Le mer. 26 sept. 2018 à 11:45, James Heald <jpm.heald(a)gmail.com> a écrit :
On 26/09/2018 10:16, Andra Waagmeester wrote:
On Wed, Sep 26, 2018 at 9:47 AM James Heald
<jpm.heald(a)gmail.com> wrote:
Far better to have a dedicated external-id property for
schema.org,
which would avoid this; and if there are important concepts there that
we don't have an item for on Wikidata, then create those items.
Creating a dedicated property for
schema.org, would also imply the need
for
creating designated properties for other context
providers such as OBO,
SIO, etc. I see that having to filter on matching uri providers in a
single
property can be complicated, but would that be
more complicated than
having
to consider all possible schema/context providers
through distinct
properties?
In SPARQL the latter is very easy. Just make a VALUES list of all the
properties you are interested in,
VALUES ?prop_wdt {wdt:P1111, wdt:P2222, wdt:P3333, wdt:P6666}
then look for
?item ?prop_wdt ?ext_id
Alternatively, if there is something characteristic about a whole set of
properties that you want to use, then add that information to the
wikidata item for the property. You will then be easily able to select
all the with that characteristic, eg:
?prop wdt:1234 wd:Q5678901
?prop wikibase:directClaim ?prop_wdt
This gives you the fine control to retrieve just the URIs of the
services you want, rather than only being able to retrieve everything
all lumped together.
Using distinct external-ID properties also makes it much easier to see
what properties are currently in play, for project tracking pages like
this one:
https://www.wikidata.org/wiki/Wikidata:WikiProject_BHL/Statistics:Titles#Ti…
-- James.
---
This email has been checked for viruses by AVG.
https://www.avg.com
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata