Re: Security Vocabulary naming mis-match

Thanks, Brooks. The draft has been updated to better match the JSON-LD 
context. That draft is in need of attention in general, so there may be 
other issues -- we just haven't had the spare cycles to clean it up or 
bring it and a few other related draft specs [1][2] in line with one 
another.

[1] https://web-payments.org/specs/source/secure-messaging/
[2] https://web-payments.org/specs/source/ld-signatures/

On 04/22/2015 10:46 AM, Brooks Boyd wrote:
> As I was perusing and attempting implementation of the Security 
> Vocabulary draft, I ran into an issue with the "data" property of an 
> "EncryptedMessage" class:
>
> https://web-payments.org/specs/source/vocabs/security.html#data
>
> The draft document indicates "data" should be the property to hold an 
> EncryptedMessage's encrypted payload, while "cipherAlgorithm" holds 
> the name of the encryption used. However, the JSON-LD context document 
> hosted at https://w3id.org/security/v1 has no "data" element, though 
> it has a "cipherData" element that seems to fit the naming scheme 
> alongside "cipherAlgorithm".
>
> One of the two should probably be updated, since putting the example 
> cited in the draft document under the "data" property into the JSON-LD 
> playground (http://tinyurl.com/p2gdacw) skips over the "data" element 
> as unrecognized.
>
> Brooks


-- 
Dave Longley
CTO
Digital Bazaar, Inc.
http://digitalbazaar.com