Rob Sanderson

Because * member_of isn't properly specified, because part_of is hard coded * part_of goes to the end (not bad, normally) because it gets rewritten to part_of|Pxxx_bla_bla so that the documentation...

Profile level relationships between classifications

1

While the code ensures that the domain and range of the ontology level relationships are enforced, there is nothing that either describes nor checks profile level relationships between instances with...

... and error if it would be overwriting an existing name. (/ht @kasei )

Should the `list_*` functions actually be generators rather than returning a materialized list?

Describe Lists and Compaction

2

Including lists of lists. (From call on 2020-02-14)

Define a recommended context to import

14

Instead of normatively requiring an initial context, such as RDFa does, instead JSON-LD has the ability to import contexts. This approach means that the existing context rules are followed, and...

JSON-LD/RDF Round tripping?

6

As discussed on 2018-07-06 call, one aspect of the work is the extent to which JSON-LD instances can be round tripped through RDF, and vice versa. In particular, questions arose...

Alias @none as none as best practice?

2

Given the best practice to alias @id and @type, it seems valuable to also have an alias without the @ symbol for @none. This would allow javascript like: `alert(object.label.none)` In...

Consider context/frame documentation best practices

4

Consider best practices around the documentation of contexts and frames. Options include: * Content Negotiation on the context document URI to get either the JSON-LD or human readable documentations (#43)...

e.g. if target in the submitted annotation is target: uri-to-annotation, then copy salient properties from that annotation to the newly created annotation.