Assume that we want to sign this bit of JSON-LD:
{
"@context": "https://w3id.org/identity/v1",
"title": "Hello World!"
}
This is what the Linked Data Signature looks like:
<!DOCTYPE html> | |
<head> | |
<meta charset="UTF-8"> | |
<title>Basic Koha bib record</title> | |
</head> | |
<body> | |
<div class="record" vocab="http://schema.org/" typeof="CreativeWork Product" resource="#record"> | |
<h1 class="title" property="name">Songs of the 60's : piano, vocal, guitar. </h1> | |
<div class="results_summary series"> |
<!DOCTYPE html> | |
<head> | |
<meta charset="UTF-8"> | |
<title>Basic Koha bib record</title> | |
</head> | |
<body> | |
<div class="record" vocab="http://schema.org/" typeof="CreativeWork Product" resource="#record"> | |
<h1 class="title" property="name">Songs of the 60's : piano, vocal, guitar. </h1> | |
<div class="results_summary series"> |
{ | |
"@context":"http://api.lobid.org/context/lobid-organisations.json", | |
"@id":"http://lobid.org/organisation/DE-605", | |
"@type":"http://xmlns.com/foaf/0.1/Organization", | |
"contactqr":"http://lobid.org/media/DE-605_contactqr.png", | |
"fundertype":{ | |
"@id":"http://purl.org/lobid/fundertype#n02", | |
"@type":"http://www.w3.org/2004/02/skos/core#Concept", | |
"prefLabel":{ | |
"de":"Land", |
{ | |
id: 'https://example.com/i/manu', | |
name: 'Manu Sporny' | |
assertions: [ ... ] | |
actions: { | |
patch: { | |
url: 'https://example.com/i/manu?action=patch', | |
verb: 'POST', | |
format: 'json-patch' | |
}, |
{ | |
"@context": ["https://ietf.org/contexts/http-problem/v1", "https://example.com/contexts/my-extension/v1"], | |
"type": ["HttpProblem", "OutOfCredit"], | |
"title": "You do not have enough credit.", | |
"detail": "Your current balance is 30, but that costs 50.", | |
"instance": "http://example.net/account/12345/msgs/abc", | |
"balance": 30, | |
"accounts": ["http://example.net/account/12345", "http://example.net/account/67890"] | |
} |
curl -sL https://deb.nodesource.com/setup_0.10 | bash - | |
apt-get install -y nodejs=0.10.40-* |
Assume that we want to sign this bit of JSON-LD:
{
"@context": "https://w3id.org/identity/v1",
"title": "Hello World!"
}
This is what the Linked Data Signature looks like:
{ | |
"@context":"https://w3id.org/identity/v1", | |
"id":"did:90096afc-c232-4b96-b48c-dcdba19b7ead", | |
"type":"Identity", | |
"credential":[ | |
{ | |
"@graph":{ | |
"@context":"https://w3id.org/identity/v1", | |
"id":"https://travel.state.gov/credentials/6fc0f6d2c68a", | |
"type":[ |
<!DOCTYPE html> | |
<html> | |
<head> | |
<title>A Template for W3C Credentials Community Group Specifications</title> | |
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/> | |
<!-- | |
=== NOTA BENE === | |
For the three scripts below, if your spec resides on dev.w3 you can check them | |
out in the same tree and use relative links so that they'll work offline, | |
--> |
PROPOSAL: Existing documentation in the DID Core specification should be refined to point out that Verification Relationships are arcs in a graph of information and Verification Methods are nodes in a graph of information. That is, they provide different types of information. The first (Verification Relationship) is the expression of a relationship between a DID Subject and cryptographic information used for the purposes of verifying a proof. The second (Verification Method) is the expression of cryptographic material. An image should be provided depicting the explanation. | |
PROPOSAL: Mark all verification methods with a warning stating that there is an ongoing discussion around the naming of verification methods that may impact the final names used in the specification. | |
PROPOSAL: The DID WG urges the W3C CCG to write documentation in the Linked Data Security specifications that clarifies how public / private key terminology has been used in the past, why it is vague and leads to security issues (like key reu |