using encoded cert (signed) as adjunct to unsigned mod

if you look at the cert:certificate property (not real), http://rdf-translator.appspot.com/parse?url=http%3A%2F%2Fyorkporc2.blogspot.com%2F&of=n3&html=1 doesnt it make some sense? just think about it (again). The cert is signed. Its IAN fields can point out, by fingerprint(s), the SSL cert(s) on the (_future_ certified https) endpoint(s) on which the profile is to be AUTHORIZED to be bound (by the signing user).
For no effort, you get alot of assurance. You get to prepare for the rollover of the https certs of the server supproting an https-grade webid.