[foaf-protocols] new cert:hex proposal

Story Henry henry.story at bblfish.net
Tue Jan 19 10:06:07 CET 2010


I have checked in the change.

Try 

curl -i http://www.w3.org/ns/auth/cert 

curl -i -H "Accept: text/n3" http://www.w3.org/ns/auth/cert

Henry

On 22 Dec 2009, at 21:33, Story Henry wrote:

> @prefix <http://www.w3.org/ns/auth/cert> .
> 
> @prefix owl: <http://www.w3.org/2002/07/owl#> .
> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
> @prefix xsd:  <http://www.w3.org/2001/XMLSchema#> .
> @prefix vs: <http://www.w3.org/2003/06/sw-vocab-status/ns#> .
> @prefix dc: <http://purl.org/dc/elements/1.1/>.
> @prefix : <cert#> .
> 
> :hex a owl:DatatypeProperty, 
>       owl:InverseFunctionalProperty;
>    rdfs:label "hexadecimal"@en;  
>    rdfs:comment """
>    An encoding of a positive integer (from 0 to infintity) as a hexadecimal string that makes it easy to read and/or fun to present on the web. 
>    The purpose of this way of representing hexadecimals is to enable users to copy and paste hexadecimal notations as shown by most browsers, keychains or tools such as opensso, into their rdf representation of choice. 
>    There are a wide variety of ways in which such strings can be presented. One finds the following 
> 
>   e1 dc d5 e1 00 8f 21 5e d5 cc 7c 7e c4 9c ad 86 
>   64 aa dc 29 f2 8d d9 56 7f 31 b6 bd 1b fd b8 ee 
>   51 0d 3c 84 59 a2 45 d2 13 59 2a 14 82 1a 0f 6e 
>   d3 d1 4a 2d a9 4c 7e db 90 07 fc f1 8d a3 8e 38 
>   25 21 0a 32 c1 95 31 3c ba 56 cc 17 45 87 e1 eb 
>   fd 9f 0f 82 16 67 9f 67 fa 91 e4 0d 55 4e 52 c0 
>   66 64 2f fe 98 8f ae f8 96 21 5e ea 38 9e 5c 4f 
>   27 e2 48 ca ca f2 90 23 ad 99 4b cc 38 32 6d bf  
> 
>  Or the same as the above, with ':' instead of spaces.
>  The letters can be uppercase or lowercase, or mixed.
>  Some may have initial 00's that would be important if the number were in complement of 2 notation. As we interpret this as a hexadecimal number any number of 00s are ok. (Complement of 2 notation and hexadecimal overlap for positive numbers)
>  In order to make this fun, we allow any unicode characters in between. A parser should 
>   1. remove all not hexadecimal characters
>   2. treat the resulting as a hexadecimal representation of a number
>  This will allow people to make a ascii picture of their public key when publishing it on the web.
>    """;
>   rdfs:seeAlso <http://en.wikipedia.org/wiki/Hexadecimal>;
>   rdfs:domain :Integer;
>   rdfs:range xsd:String;
>   vs:term_status "unstable" .
> 
> By the way the hexadecimal number above was generated by virtuoso, and is in the following PEM file.
> 
> <HenryJ.Story.pem>
> 
> 
> Henry
> 
> Social Web Architect
> Sun Microsystems		
> Blog: http://blogs.sun.com/bblfish
> 
> _______________________________________________
> foaf-protocols mailing list
> foaf-protocols at lists.foaf-project.org
> http://lists.foaf-project.org/mailman/listinfo/foaf-protocols



More information about the foaf-protocols mailing list