On Thu, Aug 07, 2014 at 11:23:26AM +0100, Brion Vibber wrote:
Well if we kill off XML and other funky formats we can call it the JSON
API :)
Actually, we should call it the YAML API, to be more complete.
https://en.wikipedia.org/w/api.php?format=yamlfm
--
Mark Holmquist
Software Engineer,
Summing up, it seems like action API and api.php are the two contenders.
api.php is least likely to be confused with anything (only its own entry
point file). But as a name it's somewhat awkward.
action API might be confused with the Action class and its subclasses,
although that doesn't seem
- Original Message -
From: Quim Gil q...@wikimedia.org
On Thu, Aug 7, 2014 at 1:42 PM, Legoktm legoktm.wikipe...@gmail.com
wrote:
I like api.php too, given that we refer to the old one as
query.php.
You are in a keynote session at OSCON introducing... which API?
Please
tl;dr: It already is the MediaWiki web API. A codename as well is fine.
Searching mediawiki.org, web API is almost as popular as MediaWiki API,
and some of the uses are correctly for extension APIs and Parsoid's API.
So the MediaWiki web API is a descriptive name that requires minimal
changes.
Call it Bob. Bob is always a good name.
- d.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
We could name it in honor of Jimbo. ;)
On Aug 7, 2014 1:18 AM, David Gerard dger...@gmail.com wrote:
Call it Bob. Bob is always a good name.
- d.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
something something Unicorn.
On Aug 6, 2014, at 2:32 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org wrote:
When api.php was basically the only API in MediaWiki, calling it the API
worked well. But now we've got a Parsoid API, Gabriel's work on a REST
content API, Gabriel's work on
UnicornPI (unicorn-pie) sounds good to me ;)
On 8/7/14, Brandon Harris bhar...@wikimedia.org wrote:
something something Unicorn.
On Aug 6, 2014, at 2:32 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
When api.php was basically the only API in MediaWiki, calling it the API
Mmmm, Unicorn Pie.
Now I'm hungry.
-Chad
On Thu, Aug 7, 2014 at 10:37 AM, Amir Ladsgroup ladsgr...@gmail.com wrote:
UnicornPI (unicorn-pie) sounds good to me ;)
On 8/7/14, Brandon Harris bhar...@wikimedia.org wrote:
something something Unicorn.
On Aug 6, 2014, at 2:32 PM,
On 07/08/14 02:37, MZMcBride wrote:
A quick count at https://www.mediawiki.org/w/api.php says that there are
currently 52 list=foo entries and 83 action=foo entries. While these
numbers are inflated due to installed extensions, I'm hesitant to present
the MediaWiki Web API as an action API.
but if you are a mobile developer using the REST API
every day, you need some other term to specify api.php.
Is api.php unsuitable for some reason?
- d
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Thu, Aug 7, 2014 at 10:58 AM, David Gerard dger...@gmail.com wrote:
but if you are a mobile developer using the REST API
every day, you need some other term to specify api.php.
Is api.php unsuitable for some reason?
That itself is awkward to say, and to disambiguate between the actual
Well if we kill off XML and other funky formats we can call it the JSON
API :)
-- brion
On Thu, Aug 7, 2014 at 11:00 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Thu, Aug 7, 2014 at 10:58 AM, David Gerard dger...@gmail.com wrote:
but if you are a mobile developer using the
On 7 August 2014 11:23, Brion Vibber bvib...@wikimedia.org wrote:
Well if we kill off XML and other funky formats we can call it the JSON
API :)
Except the other APIs will likely use JSON too, AIUI… :-)
J.
--
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.
On Wed, Aug 6, 2014 at 10:15 PM, James Forrester jdforres...@gmail.com wrote:
Yes, this is sensible. Let's certainly not call it the MediaWiki API
given how many are planned.
Core seems a reasonable qualifier, though, no? Seems like the
content API and a lot of other proposed interfaces are by
Core API can be misleading since people may think other APIs are based
on MW's API (i.e. It's core of other APIs) even though It's true in
some cases but not necessarily for all.
Am I wrong?
Best
On 8/7/14, Erik Moeller e...@wikimedia.org wrote:
On Wed, Aug 6, 2014 at 10:15 PM, James Forrester
On 8/7/14, 10:58 AM, David Gerard wrote:
but if you are a mobile developer using the REST API
every day, you need some other term to specify api.php.
Is api.php unsuitable for some reason?
I like api.php too, given that we refer to the old one as query.php.
-- Legoktm
On Thu, Aug 7, 2014 at 7:42 AM, Legoktm legoktm.wikipe...@gmail.com wrote:
I like api.php too, given that we refer to the old one as query.php.
We should just go back to query.php and get rid of api.php so we can avoid
all this confusion. /s
*-- *
*Tyler Romeo*
Stevens Institute of
I prefer Bob.
On 07/08/14 08:40, Pine W wrote:
We could name it in honor of Jimbo. ;)
On Aug 7, 2014 1:18 AM, David Gerard dger...@gmail.com wrote:
Call it Bob. Bob is always a good name.
- d.
___
Wikitech-l mailing list
On Thu, Aug 7, 2014 at 1:42 PM, Legoktm legoktm.wikipe...@gmail.com wrote:
I like api.php too, given that we refer to the old one as query.php.
You are in a keynote session at OSCON introducing... which API?
Please think on a name that is meaningful for the 3rd party developers out
there,
When api.php was basically the only API in MediaWiki, calling it the API
worked well. But now we've got a Parsoid API, Gabriel's work on a REST
content API, Gabriel's work on an internal storage API, and more on the
way. So just saying the API is getting confusing.
So let's bikeshed a reasonably
How about just the MediaWiki API? That's the only proper external API
core MediaWiki has, as far as I'm aware.
If anybody is planning to tack on something new, they should be the ones
thinking about what to name that thing ;)
--
Matma Rex
___
On 06/08/14 14:32, Brad Jorsch (Anomie) wrote:
When api.php was basically the only API in MediaWiki, calling it the
API worked well. But now we've got a Parsoid API, Gabriel's work on a
REST content API, Gabriel's work on an internal storage API, and more
on the way. So just saying the API is
wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] Bikeshedding a good name for the api.php API
How about just the MediaWiki API? That's the only proper external API
core MediaWiki has, as far as I'm aware.
signature.asc
Description: Message signed with OpenPGP using AMPGpg
Reply: Wikimedia developers wikitech-l@lists.wikimedia.org
Date: August 6, 2014 at 9:52:34
To: Wikimedia developers wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] Bikeshedding a good name for the api.php API
How about just the MediaWiki API? That's the only proper external API
core
Romeo
0x405D34A7C86B42DF
From: Bartosz Dziewoński matma@gmail.com
Reply: Wikimedia developers wikitech-l@lists.wikimedia.org
Date: August 6, 2014 at 9:52:34
To: Wikimedia developers wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] Bikeshedding a good name for the api.php
On 6 August 2014 14:53, Tim Starling tstarl...@wikimedia.org wrote:
On 06/08/14 14:32, Brad Jorsch (Anomie) wrote:
When api.php was basically the only API in MediaWiki, calling it the
API worked well. But now we've got a Parsoid API, Gabriel's work on a
REST content API, Gabriel's work on
Brad Jorsch (Anomie) wrote:
When api.php was basically the only API in MediaWiki, calling it the API
worked well. But now we've got a Parsoid API, Gabriel's work on a REST
content API, Gabriel's work on an internal storage API, and more on the
way. So just saying the API is getting confusing.
So
On 2014-08-06, 6:37 PM, MZMcBride wrote:
Tim Starling wrote:
How about the action API? The fact that it is organised in a
hierarchy of actions distinguishes it from REST, which is organised as
a hierarchy of objects. The term action also distinguishes it from RPC.
A quick count at
29 matches
Mail list logo
