- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Sat, 14 Jan 2012 16:51:13 -0500
- To: public-xg-webid@w3.org
- Message-ID: <4F11F8D1.6040208@openlinksw.com>
On 1/14/12 4:11 PM, Henry Story wrote:
> So given that that is a question we deal with a few months ago, and xsd:hexBinary had very large support, we are now looking to see if there is something about xsd:hexBinary that we don't know or that is unclear. This is easy to work on because it is a standard so we don't have to make things up here. We could perhaps even ask that this be clarified and improved in the next version of RDF. It seems that Virtuoso for example parses xsd:hexBinary very much the way cert:hex did.
Our verifier (which leverages Virtuoso) operates on a more accommodating
philosophy based on our experience with standards. We follow the
standard, and if it fails, we try other options base on real world usage
experience.
Re. Modulus, we know users are going to make certs, and then perform cut
and paste. We know its impractical to burn precious time removing
spaces, thus, when we determine that modulus has spaces (following a
successful handshake), we execute the following instead:
-- SPARQL ASK Queries re. Public Key Components
-- When you copy and paste modulus from keystring you end up with spaces
-- This query takes care of the problem via SQL built-in function used
within SPARQL
PREFIX : <http://www.w3.org/ns/auth/cert#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
ASK {
<http://id.myopenlink.net/dataspace/person/KingsleyUyiIdehen#this> :key [
:modulus ?m ;
:exponent ?e ;
] .
filter (str (?m) = sql:FOAF_MOD ("AD C1 C3 5A 90 04 D7 48 E5 ED CA 3E 4E
58 AD 6D D6 52 20 A4 12 BE D3 4D 85 0D A4 FC 7A 93 03 6D A4 E1 E6 64 7E
04 EE 0E 5A 09 CE 37 3D 0E F1 FC 39 33 50 A2 80 DB 29 D1 08 EB BF 7F 61
03 B5 92 7C D7 0F FE 89 F5 86 BF 60 E8 10 DC 5F 11 07 AB 9B AE DF 71 E1
7A 64 8F 24 B8 88 39 DC 1D 79 26 FB 6C BA FD 94 02 77 09 E9 56 28 4F 70
07 12 29 66 9F 02 D3 1E AB F6 EF 9E B1 74 43 27 F2 BD 77 F5 CB 90 26 83
90 05 C2 56 64 C9 B8 F6 93 EA 0E 81 9F 21 82 25 59 FB 42 B5 F3 81 B8 E4
30 1C 81 4E 23 C2 B6 C9 16 09 08 A4 77 6C 1D 5F 85 19 D3 25 EB 07 5A 67
B8 81 5F 52 C0 91 89 C2 50 15 8D 41 A9 56 D0 CF 79 9B 1F 79 E3 71 3F 77
BB D6 75 0E 45 69 20 DB 38 66 99 85 29 24 0D C0 0A 55 D9 4E 98 A0 2A AD
B3 4A AF 6E D8 00 3D 05 5E 83 D6 52 D5 F6 73 66 98 D0 7B 8A 64 C7 7B AD
13 B6 61") && xsd:int(?e) = 65537)
}
--
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
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Saturday, 14 January 2012 21:52:03 UTC