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

ESCAPE Workshop #48

Open
llemeurfr opened this issue May 10, 2019 · 4 comments
Open

ESCAPE Workshop #48

llemeurfr opened this issue May 10, 2019 · 4 comments
Labels
topic:google-web-packaging Issues related to the Google Web Packaging format https://github.com/WICG/webpackage

Comments

@llemeurfr
Copy link
Contributor

The aim of the ESCAPE workshop is to "deep dive on the ramifications of Web Packaging for the web". We are asked to express our "group's perspective and needs in case they can inform the debate".
We can also submit a position paper.

@llemeurfr llemeurfr added the topic:google-web-packaging Issues related to the Google Web Packaging format https://github.com/WICG/webpackage label May 10, 2019
@llemeurfr
Copy link
Contributor Author

A comment about the expression of what is Web Packaging about, as expressed in the introduction to the ESCAPE workshop: "Packaging allows content to be presented to users as if it were obtained from the original site, no matter where it was actually fetched from. For example, a peer-to-peer network could exchange signed packages, or a Web search engine could serve them when a user clicks on a search result."

I didn't see such a requirement in the PWP UCR. It seems important to listen to supporters of such feature before we acknowledge this and add it to the UCR a, isn't it?

@iherman
Copy link
Member

iherman commented May 11, 2019

Cc @swickr in case he is not watching this thread...

@iherman
Copy link
Member

iherman commented May 11, 2019

I didn't see such a requirement in the PWP UCR. It seems important to listen to supporters of such feature before we acknowledge this and add it to the UCR a, isn't it?

True, but we should probably come up with a use case that is based on this feature. For non-expert readers the ESCAPE workshop's formulation might be very opaque...

@BigBlueHat
Copy link
Member

@llemeurfr pretty sure that description maps to 5.1-5.4 (and the preamble in 5) of the Packaging section of the UCR. The larger unanswered questions for Web Packaging (as currently defined) seem to be around archive-ability and longevity (i.e. 5.5).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic:google-web-packaging Issues related to the Google Web Packaging format https://github.com/WICG/webpackage
Projects
None yet
Development

No branches or pull requests

3 participants