Loïc
,
Yes, I highly suggest a property like that to complete the graph structure between the 2
kinds of topics.
but instead of something very narrow like "provides API" you might call it
"provides Service" ? Perhaps you have something along those lines already ?
Then you can just query those that provide a Service of the Class=API ... or some
such... that seems more flexible with a property like "provides Service" which
can be just about anything... or just simply "provides" or "offers".
Thoughts ? already have properties like that ?
And I'm not sure I understand how properties are classified (i.e. what makes them show
up in
)
I guess it's when a property is an instance of a subclass of Wikidata property
(
Thad
+ThadGuidry <https://www.google.com/+ThadGuidry>
On Tue, Jul 12, 2016 at 4:31 PM, Loic Dachary <loic(a)dachary.org
<mailto:loic@dachary.org>> wrote:
Hi Thad,
On 12/07/2016 19:27, Thad Guidry wrote:
OpenStreetMap <provides> an API interface
to their Software and Database.
Unless I'm mistaken, there is no "provides" property at the moment. Do
you suggest one should be created ?
Cheers
OpenStreetMap is an Organization.
It provides things. It has things.
One thing is Software. OpenStreeMap Maps and DB.
Another thing is the Software provides an API interface to retrieve data from that
Software.
Looks like Wikidata does NOT currently provide a nice proper property to say
"provides API".
Ideally, it would also be shown as a "see also" here:
https://www.wikidata.org/wiki/Property:P2699
An API typically "uses" a Protocol
https://www.wikidata.org/wiki/Property:P2700
another view would be to say that the API doesn't "use" a Protocol, but
instead that a user communicates with an API through a Protocol.
Also, the "OpenStreetMap API" can be "used by" other Organizations
and Software
https://www.wikidata.org/wiki/Property:P1535
I would avoid using subclass ... you could say "part of" ... but then it gets
lost in the shuffle with Sparql queries because there no easy way to see just API
Providers versus Parts of Organizations which could be anything.
It would be much better and way cooler to easily list and see all the organizations that
"provide API" and even then filter on those API's by different criteria and
categories.
Thad
+ThadGuidry <https://www.google.com/+ThadGuidry>
On Tue, Jul 12, 2016 at 11:48 AM, Loic Dachary <loic(a)dachary.org
<mailto:loic@dachary.org> <mailto:loic@dachary.org
<mailto:loic@dachary.org>>> wrote:
Hi,
An API such as the OpenStreetMap API (
https://www.wikidata.org/wiki/Q25822543 ) is a
subclass of the API item
https://www.wikidata.org/wiki/Q16519, it makes sense to me that
the OpenStreetMap API is a part of (
https://www.wikidata.org/wiki/Property:P361 )
OpenStreetmap (
https://www.wikidata.org/wiki/Q936 ).
Another way of looking at it would be to have an "API" property which would
link OpenStreetmap to its API. I'm new to wikidata and would very much appreciate your
advice on this.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org>
<mailto:Wikidata@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org>>
https://lists.wikimedia.org/mailman/listinfo/wikidata
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikidata
--
Loïc Dachary, Artisan Logiciel Libre
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikidata
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata