Data has been made reusable and machine-interpretable by publishing it as Linked Data. However, Linked Data automatic processing is not fully achieved yet, as manual effort is still needed to integrate existing tools and libraries within a certain technology stack. To enable automatic processing, we propose exposing functions and methods as Linked Data, publishing it in different programming languages, using content negotiation to cater to different technology stacks, and making use of common, technology-independent identifiers to make them discoverable. As such, we can enable automatic processing of Linked Data across formats and technology stacks. By using discovery endpoints, similar to those used to discover vocabularies and ontologies, the publication of these functions can remain decentralized.

1. Discovering and Using Functions
via Content Negotiation
Ben De Meester
ben.demeester@ugent.be | @Ben__DM
http://users.ugent.be/~bjdmeest/ | +32 9 331 49 59
http://users.ugent.be/~bjdmeest/function/
How can you use functions on Linked Data
without relying on the technology stack?
Web service
JAVA function
s1.example.com
JavaScript function
s2.example.com
POST /_query
Accept: application/x-javascript
_:a
fno:solves
ex:EuclideanDistanceProblem .
1. Give me a JavaScript
function that calculates
the Euclidean Distance!
Redirect 303
s2.example.com/euclidean.js
_:a a fno:Function;
fno:name “euclidean”;
fno:expects (
[ fno:name “points”; … ]
) .
2. Sure buddy!
GET /euclidean.js
function euclidean (points) { […] }
3. JavaScript? Right here!
Discovery Hub
Client