This would not be hard for them. This link (http://www.agilewebdevelopment.com/plugins/microid) has a Ruby on Rails plugin that can be used to output a MicroID meta tag. ClaimID uses MicroID to verify sites. Theoretically, Jyte can output the meta tag on the profile pages, and then when you claim your profile page on ClaimID, you should be able to verify it just fine.
For use outside of jyte, there might be less need if the jyte profile pages were machine readable (which aren't yet).
From the perspective of having a chain of reliable claims, aggregating "upstream" at a site like ClaimID.com (with its existing API) makes a lot of sense.
There might also be a kind of "inverse-functional property" perspective: even with a ClaimID OpenID used on jyte, there may be benefits for relating claims made outside of jyte.
I think that's where the real power lies, in taking third-party claims, atomizing them, and subjecting their premises and conclusions to systematic scrutiny. This can't happen, though, without a way to assign a global identifier (similar to OpenID or XRI) to the original third-party claimant.
And just like that, it's done. From now on, people claiming their Jyte profiles will have those profiles automagically verified by ClaimID. No need for you to do anything. I've also retroactively run the verifier, so many of your Jyte profiles (claimed in ClaimID) are now verified.
Thanks to Brian Ellin for making this work in like no time at all!
Discussion (11)
This would not be hard for them. This link (http://www.agilewebdevelopment.com/plugins/microid) has a Ruby on Rails plugin that can be used to output a MicroID meta tag. ClaimID uses MicroID to verify sites. Theoretically, Jyte can output the meta tag on the profile pages, and then when you claim your profile page on ClaimID, you should be able to verify it just fine.
We'll be happy to do this. It's trivial on ClaimID's end.
That's good to hear. FWIW, here are libraries for generating MicroID in C#, Python, Java. If you need it in JavaScript or PHP those are simple too.
I think it still needs to be version 0.1 of the MicroID spec (no metadata) for compatibility with ClaimID.
If I use my ClaimID OpenID on jyte, do I even need the MicroID?
Simply in the context of jyte, no.
For use outside of jyte, there might be less need if the jyte profile pages were machine readable (which aren't yet).
From the perspective of having a chain of reliable claims, aggregating "upstream" at a site like ClaimID.com (with its existing API) makes a lot of sense.
There might also be a kind of "inverse-functional property" perspective: even with a ClaimID OpenID used on jyte, there may be benefits for relating claims made outside of jyte.
I think that's where the real power lies, in taking third-party claims, atomizing them, and subjecting their premises and conclusions to systematic scrutiny. This can't happen, though, without a way to assign a global identifier (similar to OpenID or XRI) to the original third-party claimant.
And just like that, it's done. From now on, people claiming their Jyte profiles will have those profiles automagically verified by ClaimID. No need for you to do anything. I've also retroactively run the verifier, so many of your Jyte profiles (claimed in ClaimID) are now verified.
Thanks to Brian Ellin for making this work in like no time at all!
Paco - I also took this opportunity to make our verifier .03-compliant.
Awesome, Fred! Thank you
Sweet! Now my claims are claimed, and vice versa.
So many levels of claiming going on. If only my bank got it like we do.