Rob
#1836 considers update of json-ld parser. we should also consider support for YAML-LD https://json-ld.github.io/yaml-ld/
Two implementation patterns observed in the wild seem to be within fairly easy reach, possible addressed by pyld option proposed? 1: use of a header specifiying the context for plain...
NamespaceManager has a normalizeUri method to create a CURIE (short form like foaf:Person) but no obvious way to do the inverse create a valid URIref. currently the only way seems...
JSON-LD serialisation can be done in many ways. The JSON-LD framing spec provides a basis for some control. https://www.w3.org/TR/json-ld11-framing/ JSON-schema specifications could interact with specific JSON-LD frames, but probably not...
The JSON-LD specification allows injecting a context into a json document before parsing.. https://w3c.github.io/json-ld-syntax/#interpreting-json-as-json-ld It is not obvious how PyLD supports this mode of processing - when accessing a document...
resources could gather all the known properties of a resource using the owl:sameAs semantics, deduplicating object values. In addition status highlighting for deprecated could use a (configurable) predicate value to...
as per #64, collection membership and browsing is an important viewpoint. inverse of skos:member should be displayed. ConceptSchemes should offer both hierarchy and collection views. Note that SKOS Collections are...
Provide for VocPrez to offer an existing HMTL rendering while retaining the linked data context - e.g. if a (configurable) predicate points to an URL then this is presented in...
It should be possible to configure a help link for an object type to explain more about it. If present an info icon could be added to object type links...