Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify usage of Represents and Script Represents #262

Open
andreastai opened this issue Oct 8, 2024 · 1 comment
Open

Clarify usage of Represents and Script Represents #262

andreastai opened this issue Oct 8, 2024 · 1 comment
Assignees

Comments

@andreastai
Copy link

Section 4.7 states

The Represents property is inheritable. If it is absent from an element then its computed value is the computed value of the Represents property on its parent element, or, if it has no parent element, it is the empty string. If it is present on an element then its computed value is the value specified.

Currently it is not possible that a parent element can have a @represents attribute as script events can not be nested and @represents can only be used on script events.

Note
Since there is no empty <content-descriptor>, this implies that an empty computed Represents property can never be valid; one way to construct a valid DAPT Document is to specify a Represents property on the DAPT Script so that it is inherited by all descendants that do not have a Represents property.

Only Script Represents can be specified on the DAPT Script not Represents (at least for now).

@nigelmegitt
Copy link
Contributor

Thanks, I think this either needs:

  1. a small refactor to define the inheritance on the daptm:represents attribute specifically, and note that it is permitted on <body> and <tt> as well as div OR
  2. explicit permission to permit Represents at the Script level.

I prefer the first option because the data model doesn't include script event groups, i.e. <div> elements that are not Script Events, but that would be an obvious syntactical location for specifying an inherited daptm:represents value.

@cconcolato any views?

@nigelmegitt nigelmegitt self-assigned this Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants