hasRenderedAccessLevel

property Public

Rendered Access Level

The access level THIS RENDERING was assembled at — a statement about the delivery, not about the product. A reader comparing it with oec:hasAccessLevel can tell whether they were served the whole record or a slice of it, and therefore whether an empty field is absent or withheld. Deliberately without rdfs:domain: it sits on the product node while a passport response is the product, and moves to the response envelope once responses become independently signed tier slices. That delivery model is implemented by the OpenEPCIS VC platform (module family openepcis-vc): one Verifiable Credential per access tier, hash-linked via relatedResource/digestMultibase, so which slice a caller received is a property of the signed envelope rather than of the record. Fixing a domain now would turn that move into a contract change. It must never be persisted. A stored value would claim that a past request's view is a property of the record.

URI:https://ref.openepcis.io/extensions/common/core/hasRenderedAccessLevel

Vocabulary alignment

Referenced upstream terms

Loading external vocabulary...

References

Access Level

Public by necessity: the reader who most needs to know they were served a slice is the anonymous one. Gating this behind a tier would hide the very fact that something was withheld, which is the silence it exists to break.

JSON-LD Example

{
  "type": "Thing",
  "hasRenderedAccessLevel": "..."
}