W3C home > Mailing lists > Public > public-xg-webid@w3.org > November 2011

Re: rsa ontology in cert namespace

From: Henry Story <henry.story@bblfish.net>
Date: Mon, 21 Nov 2011 19:58:01 +0100
Cc: Dominik Tomaszuk <ddooss@wp.pl>, WebID Incubator Group WG <public-xg-webid@w3.org>
Message-Id: <3FBC2991-EC87-404F-9FA9-1CD14EBBE3E7@bblfish.net>
To: Sergio Fernández <sergio.fernandez@fundacionctic.org>

On 21 Nov 2011, at 19:16, Sergio Fernández wrote:

> IDo we plan to support modules/exponent different than RSA? If not,
> I'd suggest something like cert:modulus and cert:exponent, keeping
> names simple, but with a clear mention to RSA both in label and
> comment.
> 
> On the opposite case I'd prefer loweCamelCase syntax.

Mhh, yes. I suppose the best is to look at what the XMLSignature group have come up with, since they have both in the same namespace

  http://www.w3.org/TR/xmldsig-core/#sec-KeyValue

They use Modulus and Exponent with capitals, and for dsa they use 
 
P
Q
G
Y
J
seed
pgenCounter

They encode both in http://www.w3.org/TR/xmldsig-core/#sec-CryptoBinary

[[
This specification defines the ds:CryptoBinary simple type for representing arbitrary-length integers (e.g. "bignums") in XML as octet strings. The integer value is first converted to a "big endian" bitstring. The bitstring is then padded with leading zero bits so that the total number of bits == 0 mod 8 (so that there are an integral number of octets). If the bitstring contains entire leading octets that are zero, these are removed (so the high-order octet is always non-zero). This octet string is then base64 [MIME] encoded. (The conversion from integer to octet string is equivalent to IEEE 1363's I2OSP [1363] with minimal length).
]]

We should re-use that language to specify the byte encoding we are talking about. We can then allow people to use base64Binary or hexBinary encoding. It would not matter if the SPARQL queries were able to find identities for those. At present they are not able to, so we stick to hex encoding. (it's a bit longer, but not by much)

Now would we reuse P Q G Y J ?

btw, that is why I initially preferred putting each in its own namespace, it makes it easier to understand when one writes

:me cert:key [ dsa:p "..."^^xsd:hexBinary; 
	       dsa:q "..."
               dsa:g "..."
               dsa:y "..." 
               ] .


Now I know that rdfa allows one to import external namespaces so I am not sure if the problem of declaring them is such an issue anymore.

Btw. is rdfa available now in html5?



Henry

> 
> Kind regards,
> 
> 
> On 21 November 2011 19:12, Dominik Tomaszuk <ddooss@wp.pl> wrote:
>>> :me cert:key [ cert:rsaModulus "AE293423F23..."^^xsd:hexBinary;
>>>                cert:rsaExponent 65537 ] .
>> 
>> or rsa_modules and rsa_exponent
> 
> 
> 
> -- 
> Sergio Fernández
> CTIC - Technological Center
> Parque Científico y Tecnológico de Gijón
> C/ Ada Byron, 39 Edificio Centros Tecnológicos
> 33203 Gijón - Asturias - Spain
> Tel.: +34 984 29 12 12
> Fax: +34 984 39 06 12
> E-mail: sergio.fernandez@fundacionctic.org
> http://www.fundacionctic.org
> Privacy Policy: http://www.fundacionctic.org/privacidad

Social Web Architect
http://bblfish.net/
Received on Monday, 21 November 2011 18:58:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 21 November 2011 18:58:40 GMT