Years ago we produced a product called "Component-X" which provided for choreographed data flows between composable components. It was based on the “EDOC” (Enterprise Distributed Object Computing) standard of the Object Management Group. It was killed by the tech crash of the early 2000’s.
As you may guess from the name, it was based on XML flowing between the components but just as well could use RDF (and the component metamodel could be defined in RDF). I have always thought this would be a great execution model for the semantic web. Something like a traditional programming language would be used to implement the primitive components that are then configured and assembled for an application.
Here is an example of what a component definition looked like:
[cid:image001.jpg@01D3595C.F3846600]
You could then press “execute”, send it some data and it ran.
See also, OMG standard: http://modeldriven.com/docs/EdocCCA.pdf
-----Original Message-----
From: Victor Porton [mailto:porton@narod.ru]
Sent: Wednesday, November 8, 2017 9:51 PM
To: semantic-web <semantic-web@w3.org>
Subject: Mad idea: Programming language based on RDF
Just a few seconds ago I had a mad idea:
Make a programming language based on RDF rather than on plain text.
Well, this would require many (...) lists to specify the order of execution.
What do you think?
