Remove Script Event Type, use Represents instead #241

* Merge registry table entries for `eventType` and `<content-descriptor>` (removing the `eventType` registry) * Extract definition of Represents into the Shared Properties section * Remove Script Event Type * Make Represents an optional property of Script Event and move example that was in Script Event Type up into Script Event under the Represents bullet * Add _permitted_ `#represents-div` feature * Update class diagram to remove Script Event Type and add Represents to Script Event

Fix to be one or more, was zero or more.

Separate scriptRepresents from represents as applied to Script Events. Define usage constraints. Define the syntax of `<content-descriptor>` to allow for generic validity checking without needing to understand the contents of the values used. Update the feature extensions and examples. Update the introduction to mention represents. Update the examples. Update the profiles and dispositions. Define an inheritance model for `daptm:represents`. Make Represents required to have a non-empty and valid computed value, but don't require `daptm:represents` on every Script Event `<div>` element. Allow user-defined content-descriptor values beginning `x-`. State that ttm:desc SHOULD NOT be empty.

Move the term inside the angle brackets, which makes it harder to find in the index of terms, but fixes the Respec error.

* Fix broken reference to scriptRepresents * Explain presence of inherited `daptm:represents` on `<body>` element in example * Explain how scriptRepresents might include values not present in Script - Represents * Fix syntax references to NMToken and `<lwsp>` * Take suggestions for better term definitions for content-descriptor * Clarify that Represents is inheritable, within the Represents property aside.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Remove Script Event Type, use Represents instead #241

Remove Script Event Type, use Represents instead #241

Commits on Sep 28, 2024