What is needed to help the masses of developers out there work with Linked Data more effectively? They are already learning and using OOP, Object/Relational Mappers, RMI, JNDI and other similar technologies so it seems to me that Linked Data should easily be within reach. What are the barriers to adoption and what can we do to remove them?
asked 02 Nov '09, 22:55
My personal opinion is that the more Linked Data is seen as good RESTful web development practices the more uptake it will see. I think uptake is going to be sluggish as long as Linked Data is about having to convert your webapp to use a triple-store and offer up a SPARQL endpoint.
answered 03 Nov '09, 07:34
Something like Adenine (maybe not that extreme) could make things easier.
Adenine (Haystack, MIT) was a language that supported native RDF data model, and it could be "compiled to RDF" see Adenine: A Metadata Programming Language
More on Adenine in Karun Bakshi's thesis "Tools for End-User Creation and Customization of Interfaces for Information Management Tasks"
answered 06 Nov '09, 17:06
One thing is something Danny Ayers suggested a couple of years ago: Semantic Web in a Box (SWAB). There is a cached writeup here*. In a nuttshell: one-click install package, with software, tools, bundled examples, tutorials, etc.
For instance, someone starting to learn about webdevelopment can install a webstack like XAMPP, load some examples or point-and-click-install webapplications, and (s)he is ready to go. I would like something like that for semantic webdevelopment.
*Danny talks about a unified GUI; I'm not sure about that.
answered 03 Nov '09, 01:55
The hard part is often have to convince your IT dept to give you enough access to their web space so you can set up the server to do linked data properly. They can often get nervous about unfamiliar technology.
Personally I think it would be nice to see more linked data apps out there..ones that are really "living the linked data dream" to show people why they should care.
answered 03 Nov '09, 10:04
We need better documented best practices and guidelines, and we need better software engineering support for implementing such best practices and guidelines.
Another important issue is making the effort and drawbacks of using Semantic Web technologies apparent, so that comparing e.g. RDBMS centric application architecture with RDF centric application architecture becomes possible.
The issue of taking Software Engineering into account for encouraging uptake of Semantic Web technologies has been largely ignored up to now by the academic Semantic Web community.
Which is exactly the reason why I have written a paper about it. It got the best paper award at the workshop "Semantic Web enabled Software Engineering" at the International Semantic Web Conference 2009.
Implementing Semantic Web applications: reference architecture and challenges
Abstract: To date, Semantic Web research has tended to focus on data modelling challenges, at the expense of software architecture and engi- neering issues. Our empirical analysis shows that implementing Semantic Web technologies creates challenges which can affect the whole applica- tion. Standard solutions and best practices for Semantic Web technologies are just emerging. The lack of these has been an obstacle for implementing and deploying applications which exploit Semantic Web technologies for real world use cases.
In this paper we conduct an empirical survey of Semantic Web applica- tions. We use this empirical data to propose a reference architecture for Semantic Web applications, and to identify the four main challenges for implementing the most common functionality related to Semantic Web technologies from a software engineering perspective: (i) the issues in- volved in integrating noisy and heterogeneous data, (ii) the mismatch of data models and APIs between components, (iii) immature and belated best practices and standards, and (iv) the distribution of application logic across components. We describe two orthogonal approaches for mitigating these challenges: (a) simplifying the application architecture by delegat- ing generic functionality to external service providers, and (b) assembling and customising of components provided by software frameworks for rapid development of complete applications.
I guess it depends on the size of the enterprise being developed for? Big companies can have evangelists within their ranks who see the value of linking up data. Smaller organisations won't have a clue, and it's pretty much blind chance whether a developer building a site for an SME will have the knowledge or inclination to use it.
I imagine having more tools mapped to existing development frameworks (ruby, python, php etc) which can be used by anyone would lower barriers. But, maybe more importantly, is for "the masses" of developers to see the reason why they'd want to build this stuff into their projects at an early stage. There are case-studies for larger organisations using RDF because of their huge datasets. But what about the smaller services companies or organisations fairly divorced from the development world anyway?
The biggest barrier to lower is one of ignorance.
answered 06 Nov '09, 14:57
I have a query along this.........can we use MATLAB to build up an application on linked data?
answered 28 Feb '11, 13:44