Closed tidoust closed 1 year ago
Thanks you. During development, effective guidance on the use of WebIDL was hard to come by. With some more administrivia, we can update the ED. It seems that we’d need to publishe an edited recommendation to fix the problem in a Xref, though.
The JSON-LD Framing API specification extends interfaces of the JSON-LD API but does not use the
partial
extension keyword, meaning that interfaces from both specs cannot be automatically merged into one.The JSON-LD Framing API specification also re-defines interfaces that are already defined in the JSON-LD API for no apparent reason, which is bad practice as it creates two normative definitions of the same object.
This update makes the following changes to drop duplicate definitions and improve cross-reference links between the JSON-LD Framing API and the JSON-LD API:
JsonLd
interfaceJsonLdProcessor
aspartial
(and droppedconstructor
member since it is already defined in the JSON-LD API)JsonLdRecord
andJsonLdInput
JsonLdOptions
aspartial
(and droppedordered
since it is already defined in the JSON-LD API)data-cite
links with{{xx}}
links where possiblexref
ReSpec config array (useless, local definitions are always available)Fixes #136.
Preview | Diff