W3C home > Mailing lists > Public > public-xg-webid@w3.org > January 2012

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

From: Henry Story <henry.story@bblfish.net>
Date: Mon, 9 Jan 2012 12:20:30 +0100
Message-Id: <3B0C21A1-9E24-4101-A786-F5603A971FC7@bblfish.net>
To: Peter Williams <home_pw@msn.com>, "public-xg-webid@w3.org XG" <public-xg-webid@w3.org>
Peter Williams is sending WebID Certificates with the following SAN


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

  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


   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
     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.


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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:39:54 UTC