[marcschier]

No linked issue.

The previous mapping split the Thing identity across source and WoT
extension attributes and allowed events without a subject. Consumers could
not consistently identify the resolved Thing Description and the member
described by an event using CloudEvents core attributes.

Proposed Changes

• Define a WoT core-attribute mapping using the source query parameters
  wotid and optional wotversion, followed by any additional parameters.
  The profile does not define or require a URI scheme; wot-td is only an
  example and is not proposed for registration. The separate WoT attributes
  are removed.
• Require a URI-fragment JSON Pointer subject and a code-generation-friendly
  semantic type, with a publisher-configured override for ambiguous or invalid
  derivations.
• Retain the OPC UA Publisher, writer, message-type, sequence, and status
  information needed by the combined profile. Keep native per-writer
  sequencing separate from CloudEvents source-wide ordering.
• Replace an obsolete UNCTAD legislation link that caused verification to fail.

Release Note

The proposed WoT CloudEvents mapping identifies the Thing and optional version
in source, requires a resolved-TD subject, and uses a configurable semantic
type. The OPC UA mapping retains the native metadata needed to correlate and
order messages.

[marcschier]

Feedback from review: Try to first make due with the core header vocabulary, and source is a perfect place for wotid and version is part of it.