Hi Marcus,
On Wed, May 09 2012,
mendicott.com wrote:
> I would like to request any "quickstart" documentation for using the
> BigML API, especially videos, something like "Hello World". If this
> already exists, please send a quick pointer.
We don't have API-specific videos yet, but the API is fully documented
in
https://bigml.com/developers/
and, in particular, it contains a quick-start:
https://bigml.com/developers/quick_start
In addition, in the bash and python bindings READMEs there are several
simple usage examples:
https://github.com/bigmlcom/bigml-bash/blob/master/README.md
https://github.com/bigmlcom/python/blob/master/README.md
> In particular, my first reaction is, how would I automagically flip
> ScraperWiki CSV data into BigML (with the BigML API) ?
If you can grab the data and put it in a CSV file, you'll see in the
docs that you're in business: you upload the file to create a
datasource, and build from there.
[We are working on providing other ways of making data available to our
services, so stay tunned for even easier ways of pushing data to us]
> Secondly, how can I use the BigML API to access results via Yahoo!
> Pipes (Web Service Module) ?
As you'll see in the API documentation, our API is based on RESTful JSON
requests over HTTPS. My understanding is that Yahoo! Pipes operates
over RSS/Atom sources, so one would need to translate our JSON responses
to, say, Atom feeds before being able to use them in Pipes.
Currently, we don't provide out-of-the-box support for that; in
particular, it's not totally immediate what data to offer in the feeds
for a predictive model that is per se not evolving and requires input to
be used for making predictions.
For instance, it shouldn't be difficult to write a little script that
sends JSON requests to BigML.io and publishes in a feed the resulting
predictions. Or that periodically uploads data, creates a new model and
publishes some aspects of the resulting model (our trees are whitebox
and served as JSON documents). But one needs first to decide what
aspects of the tree to publish, what kind of predictions to make, etc..
We'll definitely consider the possibility of offering a standardized set
of RSS/Atom feeds... needless to say, any further feedback or ideas from
you or other users would be immensely useful and welcome!
Thanks!
Cheers,
jao