Re: bug in cert.n3

On 21 Mar 2013, at 12:49, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

> 
> 
> On 19 March 2013 13:56, Henry Story <henry.story@bblfish.net> wrote:
> 
> On 19 Mar 2013, at 13:20, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
> 
>> 
>> 
>> On 19 March 2013 13:17, Henry Story <henry.story@bblfish.net> wrote:
>> 
>> On 19 Mar 2013, at 13:07, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
>> 
>>> 
>>> 
>>> On 19 March 2013 13:05, Mo McRoberts <Mo.McRoberts@bbc.co.uk> wrote:
>>> I think you meant :RSAPrivateKey there…
>>> 
>>> Sorry, corrected.
>>>  
>>> 
>>> (Should it not also be subclass of RSAPublicKey, as it contains everything in the pubkey plus additional properties?)
>>> 
>>> I dont think so because the exponents are different for private and public, tho modulus is the same (as it happens) ... in truth exponent should more accurately be named public_exponent
>> 
>> the reason we called it exponent, is just that it's less typing, and the private exponent is rarely used.
>> 
>> I suppose we lost this private key in moving the rsa ontology into the cert ontology...
>> 
>> Thanks for the report.
>> 
>> np, i think there's a few things we can quickly clean up
>> 
>> from what i can see it's 3 files
>> 
>> cert.n3
>> cert.rdf
>> cert.hhml
>> 
>> Do we need to make changes in triplicate?
> 
> Just the n3 file. Then we have scripts to generate the others. I think the n3 file is in hg, if not it should be, as it is easier to track changes there.
> 
> It's here:
> 
> https://dvcs.w3.org/hg/WebID/file/99ffbed7a6b4/ontologies/cert.n3
> 
> Is there a workflow for changes?  Can I change the file and send it to someone or, should I make my own branch etc.?

Make your own branch is best. Then we can review. Then we can vote during teleconf. Then we can merge. Then I have to push the changes to CVS.

Henry

>  
> 
> 
>>  
>> 
>> Henry
>> 
>>>  
>>> 
>>> M.
>>> 
>>> On Tue 2013-Mar-19, at 12:02, Melvin Carvalho <melvincarvalho@gmail.com>
>>>  wrote:
>>> 
>>> > I think I have found a bug in the cert ontology at
>>> >
>>> > http://www.w3.org/ns/auth/cert.n3
>>> >
>>> > :privateExponent
>>> >    rdfs:domain :RSAPrivateKey;
>>> >
>>> > Is used yet :RSAPrivateKey is nowhere defined
>>> >
>>> > The correction should be:
>>> >
>>> > :RSAPublicKey a owl:Class;
>>> >     rdfs:label "RSA Private Key"@en;
>>> >     rdfs:isDefinedBy <cert#>;
>>> >     rdfs:subClassOf :PrivateKey, :RSAKey;
>>> >     vs:term_status "unstable";
>>> >     rdfs:seeAlso <http://en.wikipedia.org/wiki/RSA>;
>>> >     rdfs:comment """
>>> >     The RSA private key.  Padded message m are encrypted by applying the function
>>> >       modulus(power(m,exponent),modulus)
>>> >     """@en .
>>> >
>>> > I have raised issue 77 to address this
>>> >
>>> > https://www.w3.org/2005/Incubator/webid/track/issues/77
>>> >
>>> > Please let me know if/how I can help action this fix
>>> 
>>> 
>>> --
>>> Mo McRoberts - Analyst - BBC Archive Development,
>>> Zone 1.08, BBC Scotland, 40 Pacific Quay, Glasgow G51 1DA,
>>> MC3 D5, Media Centre, 201 Wood Lane, London W12 7TQ,
>>> 0141 422 6036 (Internal: 01-26036) - PGP key CEBCF03E
>>> 
>>> 
>>> 
>>> -----------------------------
>>> http://www.bbc.co.uk
>>> This e-mail (and any attachments) is confidential and
>>> may contain personal views which are not the views of the BBC unless specifically stated.
>>> If you have received it in
>>> error, please delete it from your system.
>>> Do not use, copy or disclose the
>>> information in any way nor act in reliance on it and notify the sender
>>> immediately.
>>> Please note that the BBC monitors e-mails
>>> sent or received.
>>> Further communication will signify your consent to
>>> this.
>>> -----------------------------
>>> 
>> 
>> Social Web Architect
>> http://bblfish.net/
>> 
>> 
> 
> 
> Social Web Architect
> http://bblfish.net/
> 
> 

Social Web Architect
http://bblfish.net/