RE: broken turtle

Just announce when the tool works, right. I can wait (another 12 years). I just waited 25 for client certs to reach W3C (starting from 1986, when my tutor first showed us a CCITT draft - forwarded by some super half secret academic/military UK committee, playing james bond, with portable radios (!), required background investigations of all foreign reseach students, and other drivel designed to indoctrinate folks in how crypto OUGHT to be handled). I work in a business that can not tolerate this category of error. This issue would cause a $15 phone call, which is 3 months of per-subscriber revenue. Furthermore, the person will tell 4 other people about it, creating a wave of misery about how awful technology is (per se). realtors are as social as its gets (being the first and original social network, going back to the cave in the South of France, selling well-to-do cave couples spots around the central fire versus the property with the view (the draughty cave entrance)).  The nature of the web is that it commoditized the IT economy, and the revenues only contract - as every visual basic programmer with 3 weeks of programming experience can produce 80% of the features (at 80% of the quality). This means the cash flow side of the economics are about controlling the error rate (a bit like RSA...)    Date: Thu, 22 Dec 2011 21:10:53 -0500
From: kidehen@openlinksw.com
To: public-xg-webid@w3.org
Subject: Re: broken turtle


  


    
  
  
    On 12/22/11 8:56 PM, Peter Williams wrote:
    
      
      
        

        my new cert (old key) with turtle on azure cloud blob service:
        site reports ok. REport 1 URI, correctly.

         

        
          my old cert (old key) with RDFa
            on blogger page : site reports ok. Only reports 1 URI.
           
          ODS cert/key/proxyURI with proxied page (for an original
            twitter account): site reports fail
           
           
        
      
    
    Ah! There are some issues with the Proxy URIs. Myself and Henry had
    a quick one on one session and found two issues. One relates to
    across the wire serialization which we have to fix. The other is a
    niggling issue re. cache invalidation, but you can work around it by
    adding the following to the ProxyURI: ?@Lookup@=&refresh=clean 
    after you place the ProxyURI in your browser's address bar. 

    

    The simple test is this, if you don't see the cert. fingerprints in
    the page that is returned to your browser you know that the
    validation will fail due to incomplete graph. 

    

    

    Example:

    

    One of my ProxyURIs:
    http://id.myopenlink.net/about/id/entity/http/twitter.com/kidehen .

    

    Document URL to which the Name above resolves:
http://id.myopenlink.net/about/html/http://id.myopenlink.net/about/id/entity/http/twitter.com/kidehen
    .

    

    Forced refresh:
    http://id.myopenlink.net/about/html/http://id.myopenlink.net/about/id/entity/http/twitter.com/kidehen?@Lookup@=&refresh=clean
    .

    

    Then retest and it will work, as long as you can see the fingerprint
    in the page (human readable descriptor) returned to the browser. 

    

    

    -- 

Regards,

Kingsley Idehen	      
Founder & CEO 
OpenLink Software     
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen