also, the datatyping to xsd:string is generally unnecessary and creates more headaches for plain JSON processors, since it means that compacting against activitystreams only will NOT produce the following:
{
"https://purl.archive.org/socialweb/webfinger#webfinger": "acct:foo@bar.com"
}
but will produce this instead:
{
"https://purl.archive.org/socialweb/webfinger#webfinger": {
"@value": "acct:foo@bar.com",
"@type": "http://www.w3.org/2001/XMLSchema#string"
}
also, the prefixes wf and xsd are unused within the data graph, and can pollute the context of the JSON-LD processor.
a better context would simply be:
{
"@context": {
"webfinger": "https://purl.archive.org/socialweb/webfinger#webfinger"
}
}
cc @eprodrom