@@ -1824,6 +1824,28 @@ TODO:
1824
1824
- See other introductory sections of LCC entities. Use same structure to do the transformation
1825
1825
1826
1826
1827
+ # ## Generating Verifiable Claims
1828
+
1829
+ As the COALA IP ontology may be potentially exposed to the public, users must have a mechanism of
1830
+ proving their actions to others. To provide this with cryptographic signatures is a two part
1831
+ challenge: we not only need to ensure that user identities can be associated with cryptographic
1832
+ identities (see [requirements of `Party` s](# transformation-of-rrm-party-to-an-rdf-person), but also
1833
+ that any submitted claim can be signed by those cryptographic identities. Although no optimal
1834
+ solution currently exists for associating identities, a number of pre- existing schemata are
1835
+ available for signing RDF - compatible data:
1836
+
1837
+ - The [Web of Trust RDF ontology](http:// xmlns.com/ wot/ 0.1 / ) by the [Friend of a Friend Project](http:// www.foaf- project.org/ ),
1838
+ although this assumes the ontology is mutable; and
1839
+ - The [Linked Data Signatures schema](https:// web- payments.org/ specs/ source/ ld- signatures/ ) by the
1840
+ [Web Payments Community Group](https:// www.w3.org/ community/ webpayments/ )
1841
+
1842
+ Building on top of these two facets is the [Verifiable Claims Architecture](http:// w3c.github.io/ webpayments- ig/ VCTF / architecture/ )
1843
+ and its associated [data model](http:// opencreds.org/ specs/ source/ claims- data- model/ ) (currently
1844
+ using the Linked Data Signatures schema) that is being standardized by the [Verifiable Claims Task
1845
+ Force](http:// w3c.github.io/ vctf/ ). In the future, data from COALA IP could be used to generate, or
1846
+ even be created, in the format proposed.
1847
+
1848
+
1827
1849
# ## User Extensions
1828
1850
1829
1851
TODO :
0 commit comments