Prefix for MerkleProof2017 attributes

I have a question following up on our discussion of the MerkleProof2017
suite.

For the attributes (e.g. proof, merkleRoot, targetHash, ...), should we use
the prefix "sec:" or "cp:"? Because we are adapting this from chainpoint
v2, I am not sure if it's customary to define these new attributes in the
security context or keep the original.

Referenced Contexts:
- https://chainpoint.org/contexts/chainpoint-v2.jsonld
- https://web-payments.org/contexts/security-v1.jsonld

Thanks,
Kim

Current draft of MerkleProof2017:


"signature": {
    "type": "MerkleProof2017",
    "proof": [
      {
        "right":
"62a1e26974f20cd38f1349a2c0975c98e3b7dbb821b7568f6790aae10c20032d"
      }
    ],
    "targetHash":
"7d5ee19584a27a9bf7d558e0128a27e18f8d11ace3c99cd72423c9db6cbc50d7",
    "merkleRoot":
"7570ad1a939b1d733668125df3e71ebbd593358e7d851eff3fdebd487462daab",
    "anchors": [
      {
        "type": "BTCOpReturn",
        "sourceId":
"3608e5e893a4edb8634e79b43ceae4bd30153b80a7e91e3b9d65b1bd16485433"
      }
    ]
  }

-- 
Kim Hamilton Duffy
Principal Engineer | Learning Machine + MIT Media Lab
Co-chair W3C Credentials Community Group
400 Main Street Building E19-732, Cambridge, MA 02139
12001 N. Central Expy, Suite 1025, Dallas, TX 75243

kim@learningmachine.com | kimhd@mit.edu
425-652-0150 | LearningMachine.com