#opendata much spoken concept, but just data is not enough. Yes + the code, it's critically important!
The
REST architectural style widely used today has no data format, as usual it's
JSON or
XML but no matter what it is. JSON is the best choose, easy for humans to use, easy for programms to manipulate.
Ok, just data is not enough, data + code. What code? Code what for?
Two things:
- open source code is not ready to use immediately, you have to build it as minimum, resolve dependencies, create config files, etc. But imagine what if any one can run open source software as a service (OSSaaS), no make files, no linux stuff, just put query in a browser address line, no programming skills required!
- just data is not enough, who put this data to open data cloud?
Men in black, doubt it. Humans manually upload exel files there, omg. An idea to make opendataobjects live, just add code!
opendataobjects=opendata+opencode!
How it might looks like, no bicycle inventing, just in JSON:
{
field1 : "value1",
field2 : "value2",
...
field_method1: "script code",
field_method1_lang: "javascript",
...
field_method2: "script code",
field_method2_lang: "python",
...
}
Opendataobjects is a concept to represent opendata with open methods to play with this opendata. Yes we know all this
OOP stuff, lets take what we need here!
You put in
wikipedia just static text, let's imagine you put live opendataobjects here!
Who's responsible for execution of opendataobjects methods, both open data cloud providers and 3d party services, this code can do any http calls, send messages to other objects, etc.
Lets make cloud more open!
..to be probably continued :)