Re: struggling with ASK

On 29 Nov 2011, at 22:35, Kingsley Idehen wrote:
>> [snip]
> Henry,
> 
> This also works:
> PREFIX : <http://www.w3.org/ns/auth/cert#>
> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
> ASK {
> <http://id.myopenlink.net/about/id/entity/http/twitter.com/kidehen> :key [
> :modulus "9d25875087cb936da55dd036b89530a2d830ce72f378a3fcc2fe07174d74ef07aff2a552ef582bb57676d377daf3732ccc7cae810522dcdfce76e823cc297bad002b0d3ea42578ec00d2ae7354247420b9d708fce870679e22e5ecd49a149b41ea2f4eafdbc767bec673d088f98d1b12cd4a4997d362a4ed2ed5215c4c21072d079abdb2cc2da1a27563b86643ab6222019ae8f667a0b3548227af0ae526b13b5ecc431c11f6896e771010c959b5e6700605f95ff7f0fd3019f8e7ef2605f99a7b0095e7c9bb6e99825fda43d30a9c8baed0e35217c2cc61a81fc21dd500974f52deb6c1f784a603a989e4d5c421003d16978c23f62b4f4e027b7e4295fb6db7"^^xsd:hexBinary;
> :exponent "65537"^^xsd:integer;
> ] .
> }

yep that's as it should be. But there seems to be some things that still need to be clarified in the SPARQL spec. Because for example Jena's ARC does not do what I expected with whitespace characters coming before or after the number. 

    https://issues.apache.org/jira/browse/JENA-170


> 
> This works, but it makes specific use of Virtuoso's in-built functions. This option is useful when people copy and paste the modulus from keychain and other keystores with a UI front that leads to spaces in the modulus:
> 
> PREFIX : <http://www.w3.org/ns/auth/cert#>
> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
> ASK {
> <http://id.myopenlink.net/about/id/entity/http/twitter.com/kidehen> :key [
> :modulus ?m ;
> :exponent ?e ;
> ] .
> 
> filter (str (?m) = sql:FOAF_MOD ("9D 25 87 50 87 CB 93 6D A5 5D D0 36 B8 95 30 A2 D8 30 CE 72 F3 78 A3 FC C2 FE 07 17 4D 74 EF 07 AF F2 A5 52 EF 58 2B B5 76 76 D3 77 DA F3 73 2C CC 7C AE 81 05 22 DC DF CE 76 E8 23 CC 29 7B AD 00 2B 0D 3E A4 25 78 EC 00 D2 AE 73 54 24 74 20 B9 D7 08 FC E8 70 67 9E 22 E5 EC D4 9A 14 9B 41 EA 2F 4E AF DB C7 67 BE C6 73 D0 88 F9 8D 1B 12 CD 4A 49 97 D3 62 A4 ED 2E D5 21 5C 4C 21 07 2D 07 9A BD B2 CC 2D A1 A2 75 63 B8 66 43 AB 62 22 01 9A E8 F6 67 A0 B3 54 82 27 AF 0A E5 26 B1 3B 5E CC 43 1C 11 F6 89 6E 77 10 10 C9 59 B5 E6 70 06 05 F9 5F F7 F0 FD 30 19 F8 E7 EF 26 05 F9 9A 7B 00 95 E7 C9 BB 6E 99 82 5F DA 43 D3 0A 9C 8B AE D0 E3 52 17 C2 CC 61 A8 1F C2 1D D5 00 97 4F 52 DE B6 C1 F7 84 A6 03 A9 89 E4 D5 C4 21 00 3D 16 97 8C 23 F6 2B 4F 4E 02 7B 7E 42 95 FB 6D B7") && xsd:integer(?e) = 65537)
> }


yes, that would be useful and correct with the cert:hex scheme we were using. At present we should be working with standards as they are set, because we can then use our simple use case to drive the standards where they need to be. 

If people wrote out their modulus to fit your query there, then they would be able to be authenticated on virtuoso but not other systems, and that would not make for a good user experience. 

I had developed cert:hex to make it easy to write things out, but given that most people will have certificates created in one click, the advantage of that versus fitting into existing well defined standards was not so great.

> 
> 
> Links:
> 
> 1. http://goo.gl/hv4US -- SPARQL Protocol URL (results)
> 2. http://goo.gl/JGO6D -- SPARQL Protocol URL (query editor)
> 3. http://goo.gl/pXbQa -- SPARQL Protocol URL (results) for query using Virtuoso specific function
> 4. http://goo.gl/mlB4B -- SPARQL Protocol URL (query editor) for query using Virtuoso specific funtion.
> 
> -- 
> 
> 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
> 
> 
> 
> 
> 
> 

Social Web Architect
http://bblfish.net/

Received on Tuesday, 29 November 2011 23:09:39 UTC