In several places of the InternetWide Architecture, we use LDAP as our
data protocol — because it is the most refined standard protocol
for digging around in data. What we haven't yet discussed is how its
privacy compares to, say, HTTP.
Give a technician a hammer, and soon she'll see nails everywhere.
Why use other tools, if a hammer works so well?
This is pretty much the position that HTTP is in, and this is far
from well-deserved. A healthy Internet requires a plethora of protocols,
all optimised for their particular purposes.
Last week we posted an idea for automatic processing of legal agreements. Today, we want to show a case study, which is still far from complete and definately not final. What this demonstration captures is how we want other parties to communicate with us. Something like this could be used by companies to automatically decide whether they can sign you up for email marketing, and so on. Moreover, it provides handles for law enforcement.
Legal terms on the Internet are a nuisance. The term TL;DR ("Too Long, Didn't Read") is used to indicate how meaningless the wordy drivel has become, due to sheer length. Interestingly, contracts have a lot of similarity. We should be able to automate them, in fact.
We published articles on pernicious developments on the web; now it is time to explain how we see this improve under the InternetWide Architecture. As usual, our approach is practical, but we don’t shy away from adopting new standards if they improve the overall situation.