Previously, in my first #dajsiepoznać post, I wrote about how I’ve been trying to create wikibus.org, the public transport encyclopedia. Sadly, Most of that development has been more of blind technology exploration, learning and very little delivery. Now, I’m going forward with renewed strength, and I’d like to share more details about the idea behind the project.Read on →
For anyone interested in the Semantic Web, data storage continues to be an issue. Although there is a fair number of triple- and quadstore, your mileage may vary. Some triple stores offer mediocre performance, there are stability issues, missing features or unsupported platforms. There however one simple, but hassle-free alternative in the cloud.Read on →
In the fourth part of my REST series I will expand the idea of links. Links are just a stepping stone no matter how important.
Simple links aren’t enough for the client to interact with the server. After all how is it going to know when to
and when to
PUT or what are the required parameters and request bodies. This is where affordances come into play. It
means that the server should include all information the client needs. Just as defined by the self-descriptive constraint.
This is the second post in a series about REST, where I intend to debunk some commonly repeated mistakes and bad advice for practitioners of RESTful services. The central, and agreeably most important element of any API, is the resource. On the Web resources are identified and addressed by URLs. REST defines some clear rules about these identifiers, yet we so commonly break them. Let’s see how this happens and what are the consequences.Read on →
This is the first in a series of posts where I want to discuss misconceptions about the REST architectural style. Much has been written and told about REST, yet there are a number of common mistakes prevalent in the community. In this post I will introduce (again) the basics of REST as defined by Roy T. Fielding.Read on →