Closed VladimirAlexiev closed 1 month ago
Thanks for noticing this. I don't recall right now why we had a separate IANA considerations section in the Framing document, as it is redundant with that from the Syntax document, and as you point out, inconsistent.
I think the corrective action is the just make the Framing document consistent with the Syntax document for this particular profile parameter in an Erratum.
Summary: Update IANA considerations to make thehttp://www.w3.org/ns/json-ld#frame
parameter required and change from http://www.w3.org/ns/json-ld#frame
, which was inaccurate and inconsistent with the same definition in the with the narrative text and with the same definition in JSON-LD11.
I'm re-opening this to undo the normative change to the ReSpec source to allow for future publication without going through the CR cycle again.
The lines noted in #137 should be added back when ready for a new CR phase.
hi @gkellogg I'm closing this based on your latest commit. Please reopen if I'm wrong
https://www.w3.org/TR/json-ld11-framing/#iana-considerations:
https://w3c.github.io/json-ld-syntax/#application-ld-json
frame
notframed