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 that ttp:profile@combine and ttp:[*]ProfileCombination are the same. #1045

Open
nigelmegitt opened this issue Feb 21, 2019 · 0 comments
Milestone

Comments

@nigelmegitt
Copy link
Contributor

There are currently two ways to define the combination of profiles:

  1. The profile element's @combine attribute.
  2. The tt element's @ttp:processorProfileCombination and @ttp:contentProfileCombination attributes.

The value sets of all three attributes are the same modulo #1028 and the combination algorithms are the same regardless of which source of "combine" semantics is applicable.

However the treatment of that combination semantic in the specification is in text in the section on the profile element and in a helpful table in each of @contentProfileCombination and @processorProfileCombination (and those tables are different because "prohibited" is not allowed in a processor profile but is allowed in a content profile).

It would be helpful to clarify that those tables are in fact the result of applying the combination logic specified in prose under profile element, and maybe move the tables under that prose and reference them from the @...ProfileCombination attribute sections.

@skynavga skynavga changed the title Clarify that ttp:profile@combine and ttp:[*]ProfileCombination are the same Clarify that ttp:profile@combine and ttp:[*]ProfileCombination are the same. Mar 25, 2019
@skynavga skynavga added this to the 3ED milestone Sep 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants