Hi, newbie question again: what if a 'protocol' can be regarded as an issue
for the 'data web' as there is one for the traditional 'document web'. The
question is: does the design issues (ex.: RESTful application design
patterns) of a document resource centric web holds (or at least part of
them) for the concept of a 'data web' only because it relies in the same
protocol / patterns (HTTP).

See attached file (or Protocol section in the link) for a first (confuse /
abstract / questionable) set of thoughts in the subject:

https://docs.google.com/document/d/1OqsVn6uo0cr6qruzWj9yRASrmvAIAf4HsHuLS2aRSy8/edit?usp=drivesdk

Best Regards,
Sebastián.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB