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
OpenStreetMap <provides> an API interface to their Software and Database.
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@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@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
There is two things : API specs, and services that can implement that specs.
Which property links something to the class of stuffs that represents its properties ? "Instance of", a pretty natural way in computing :) The spec is a set of property its implementations fulfills ... Problem solved :)
Example please Thomas.
Thad +ThadGuidry https://www.google.com/+ThadGuidry
On Tue, Jul 12, 2016 at 12:40 PM, Thomas Douillard < thomas.douillard@gmail.com> wrote:
There is two things : API specs, and services that can implement that specs.
Which property links something to the class of stuffs that represents its properties ? "Instance of", a pretty natural way in computing :) The spec is a set of property its implementations fulfills ... Problem solved :)
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 12 July 2016 at 18:27, Thad Guidry thadguidry@gmail.com wrote:
OpenStreetMap is an Organization.
Alternatively:
The OpenStreetMap Foundation is an organisation
OpenStreetMap is a web service, a database (and, if you must, a map - though I usually tell people it's not a map.)
Exactly my point Andy. (and I meant to add the "Foundation" after that...my bad)
Same String = Many Things
BUT !!!! sometimes we really should not use that Same String in 2 Wikidata Topics, but can do a little research to find the Real name that each topic should ideally be using)
One topic for the Organization could be named OpenStreetMap Foundation
Another topic could be named OpenStreetMap the service, db, map (or if you have to say many things about each part, then ideally each should be a separate WD Topic)
Another topic could be named the OpentStreetMap API
In Freebase, we had a great way to move statements to other topics where they really should be. This helped with Split topics. In Freebase, we had both Merges, and Splits. And Splits are the most painful and require nice gui tools to make moving statements around from one topic to another. We had a great view that should 2 topics side by side...so you could move statements from one to the other to disentangle it all after a Topic Split.
Thad +ThadGuidry https://www.google.com/+ThadGuidry
On Tue, Jul 12, 2016 at 2:39 PM, Andy Mabbett andy@pigsonthewing.org.uk wrote:
On 12 July 2016 at 18:27, Thad Guidry thadguidry@gmail.com wrote:
OpenStreetMap is an Organization.
Alternatively:
The OpenStreetMap Foundation is an organisation
OpenStreetMap is a web service, a database (and, if you must, a map - though I usually tell people it's not a map.)
-- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
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@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@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikidata
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
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 ?
Thad +ThadGuidry https://www.google.com/+ThadGuidry
On Tue, Jul 12, 2016 at 4:31 PM, Loic Dachary 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@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" propertywhich 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@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikidata
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
-- Loïc Dachary, Artisan Logiciel Libre
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 13/07/2016 03:53, Thad Guidry wrote:
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 ?
I did not find anything like that in https://www.wikidata.org/wiki/Wikidata:List_of_properties/all#Generic
Properties matching "service" https://www.wikidata.org/w/index.php?title=Special:Search&limit=500&... Properties matching "offer" https://www.wikidata.org/w/index.php?title=Special:Search&limit=500&...
And I'm not sure I understand how properties are classified (i.e. what makes them show up in https://www.wikidata.org/wiki/Wikidata:List_of_properties/all)
I guess it's when a property is an instance of a subclass of Wikidata property (https://www.wikidata.org/wiki/Q18616576 ) such as "Wikidata property for items about organizations" https://www.wikidata.org/wiki/Q18608993 and a bot takes the last part of the property name to be the category ?
Thad +ThadGuidry https://www.google.com/+ThadGuidry
On Tue, Jul 12, 2016 at 4:31 PM, Loic Dachary <loic@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@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@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@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@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikidata
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata