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.

Sign up for GitHub

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

Jump to bottom

Is "Indexed by URL" sufficient? #24

Open
BigBlueHat opened this issue Mar 7, 2018 · 0 comments
Open

Is "Indexed by URL" sufficient? #24

BigBlueHat opened this issue Mar 7, 2018 · 0 comments
Labels
topic:google-web-packaging Issues related to the Google Web Packaging format https://github.com/WICG/webpackage

Comments

@BigBlueHat
Copy link
Member

In #23 one of the "associated requirements" listed within the PWP section of the Web Packaging spec is...

Indexed by URL: Resources on the web are addressed by URL.

Practically, this means that:

  1. everything in the package is also independently retrievable via its URL
  2. there is no additional mechanism for pointing at things within the package (i.e. no fragment identifier)
  3. there cannot be (consequently) any "package-only" or "interior" resources

There may be other consequences (positive and negative) of this design which we should consider.
@BigBlueHat BigBlueHat added the topic:google-web-packaging Issues related to the Google Web Packaging format https://github.com/WICG/webpackage label Mar 14, 2018
@BigBlueHat BigBlueHat mentioned this issue Apr 11, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic:google-web-packaging Issues related to the Google Web Packaging format https://github.com/WICG/webpackage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BigBlueHat