4 ms·
How about creating a universal notation which can then be parsed into the code needed in a particular platform or language. Suppose we need to get a JPEG from
by thewarrior 12y ago
How about creating a universal notation which can then be parsed into the code needed in a particular platform or language.
Suppose we need to get a JPEG from a particular URL.
So the corresponding universal notation would be :
Image -> Representation : Image::JPEG
Image -> LocationType : Network URL
Image -> NetworkPath : http://xyz.com/a.jpg http://xyz.com/a.jpg
Then suppose we want the contents of the image in Base64
We need to query for a function or chain of functions which leads from semantic representation Image::JPEG -> String:Base64.
Kind of like a cross-language Hoogle. We could then have a community effort to annotate all APIs this way.
Another thing we need is an encyclopedia of things that can go wrong. For instance what are the things to watch out for when copying one file to another ?
Permissions ? Lack of disk space ? Power goes out?
There are many things we might miss. So a repository of corner cases would be useful.
Though I don't have enough skills I'm thinking of making something along these lines. Does anyone here think that this is worth doing ?
- tel 12y agoPeople have tried to make these many times. In targeted domains (e.g. health decision support software) they're actually quite popular. Look up the OWL project on W3C for instance.
- deleted 12y ago[deleted]