turtle/n3 - Peter's Williams' idea of going trough translators

Peter Williams is sending WebID Certificates with the following SAN

  http://rdf-translator.appspot.com/parse?of=n3&url=http%3A%2F%2Fidweb.cloudapp.net:8080%2FHome%2FAbout

Exactly what the purpose of this is, is not clear to me. The translator just translates the rdf from the original rdfa to n3. You might as well then make a copy of the output and put it on data.fm, and use that as your webid. The translator in any case only points to the original WebID
  
  http://idweb.cloudapp.net:8080/Home/About#

  So the translation cannot be proof about what the original said, unless you have a list of good translation services that each WebID implementation had to keep up to date all the time, which would inevitably be out of sync, and so lead to confusion. 

  PW could of course make this WebID be

     http://rdf-translator.appspot.com/parse?of=n3&url=http%3A%2F%2Fidweb.cloudapp.net:8080%2FHome%2FAbout#me

   which would also be silly for two other reasons:

  0. It would require him to publish the document at http://idweb.cloudapp.net:8080/Home/About# so that it be about
       http://rdf-translator.appspot.com/parse?of=n3&url=http%3A%2F%2Fidweb.cloudapp.net:8080%2FHome%2FAbout#me
     which requires quite a bit more thought than just writing a document about an entity defined in the original document

   1. It would make for a slower service, since the translator fetches and translates the document on each authentication attempt
   2. It ties the WebID to a particular representation (n3 in this case, which is not parsed by most libraries btw, turtle would be better)
   

  And probably a few other problems of the same nature. 

  Notice how all Peter Williams' ideas since the beginning are constantly attempts to make something simple complicated.

  Henry

Social Web Architect
http://bblfish.net/

Received on Monday, 9 January 2012 15:29:37 UTC