Rob Sanderson

Initial Proposal: If the current user has permission to modify the annotation, then this can be expressed by including PUT and/or DELETE in the http `Allow` response header when the...

Who can identify appropriate security people to discuss with? And if no one, then how are we going to make progress on this issue?

+1 to Ivan's comment from Jan 11, and Nick's comment from Dec 2. Let's publish a new WD, get a quick review (sanity check rather than anything systematic) and then...

Yes, we re-use some but not all of the Activity Streams classes and properties. We also, for example, don't use their notion of a Note, or a Link. FOAF is...

We do. The range of as:generator is Object U Link. We take the Object route. So the object of the triple is an as:Object (by inference from the predicate) and...

This would be a change of functionality requiring a new version, rather than an error in the current spec. Tagging postpone (e.g. defer for future version)

Summary: Context document should use {"id": "@id"} and {"type": "@type"}

Noted that the context document can and should be fixed before any future republication of the document.

I'm fine with anonymous classes like `owl:Restriction` as a bnode. Will update the issue to clarify that this only refers to instance data, or ABox if you prefer that terminology.

I think it should be part of the EasierRDF profile that the following pattern is not allowed: ``` { "@id": "https://example.org/some/instance", "@type": {"rdfs:subClassOf": "schema:Engineer", "rdfs:subClassOf": "schema:SoftwareDeveloper"}, "rdfs:label": "Some Person" }...