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

Adds customized paragraph to SoTD that mentions the Presentation API #50

Merged
merged 1 commit into from Jul 7, 2016

Conversation

tidoust
Copy link
Member

@tidoust tidoust commented Jul 7, 2016

This update intents to fulfill the following pubrules SoTD requirement:
"It MUST include at least one customized paragraph. This section SHOULD include the title page date (i.e., the one next to the maturity level at the top of the document). These paragraphs SHOULD explain the publication context, including rationale and relationships to other work."
https://www.w3.org/pubrules/doc/rules/?profile=FPWD#customParagraph

While the Remote Playback API does not depend on the Presentation API in practice, it seems important to present it in the context of the work on the Presentation API.

This update intents to fulfill the following pubrules SoTD requirement:
"It MUST include at least one customized paragraph. This section SHOULD include
the title page date (i.e., the one next to the maturity level at the top of the
document). These paragraphs SHOULD explain the publication context, including
rationale and relationships to other work."
https://www.w3.org/pubrules/doc/rules/?profile=FPWD#customParagraph

While the Remote Playback API does not depend on the Presentation API in
practice, it seems important to present it in the context of the work on the
Presentation API.
@anssiko anssiko merged commit 44ecb0a into w3c:gh-pages Jul 7, 2016
@anssiko
Copy link
Member

anssiko commented Jul 7, 2016

Thanks, this clarifies the relationship.

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

Successfully merging this pull request may close these issues.

None yet

2 participants