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

updates per comments in issue #103 #105

Merged
merged 1 commit into from
Nov 18, 2017
Merged

updates per comments in issue #103 #105

merged 1 commit into from
Nov 18, 2017

Conversation

mattgarrish
Copy link
Member

@mattgarrish mattgarrish commented Nov 17, 2017

I'm not sure if this capture everything given the lengthy discussion. Substantively, only the web publication resource requirement appears to change from MUST to SHOULD. I have made a couple of tweaks to the toc and default reading order to make it a little more clear that these come from publication resources.

I'm not clear why we would start talking about scripting in the entry page, so avoided that. If we want to describe interfaces, shouldn't it be a separate section with a recommendation to use the entry page if the interface can only be initiated from one page?


Preview | Diff

@mattgarrish
Copy link
Member Author

Given the lack of comment, I'm going to merge this on the premise it meets the "livable with" criteria for now.

@mattgarrish mattgarrish merged commit 670817f into master Nov 18, 2017
@mattgarrish mattgarrish deleted the address branch November 18, 2017 17:12
mattgarrish added a commit that referenced this pull request Nov 20, 2017
@mattgarrish
Copy link
Member Author

Reiterating here, current proposal is:

MUST be an HTML document
MUST include a link to the manifest
SHOULD be a publication resource

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.

2 participants