Skip to content

Tidy up language around Represents #327

@nigelmegitt

Description

@nigelmegitt

While implementing validation for Represents I noticed that the requirement for a computed value of Represents on Script Event and Text objects is unclear. The wording under Script Event and Text is slightly different, and it is not obvious why.

It also is unclear if it is acceptable to have a <span> that sets daptm:represents="" if its ancestor <p> has a computed value of daptm:represents that is valid.

Suggest tidying the language to make this less ambiguous:

  • Clarify that every part of a Text must have a valid computed Represents
  • Clarify that Script Events and Text objects must have a valid computed Represents
  • Clarify that <div> elements that are not Script Events don't need a valid computed Represents

It might be useful to specify in §4.7 Represents which objects the property applies to, as well as which is may be specified on, which is listed now.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions