You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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...
@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).
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.
The text was updated successfully, but these errors were encountered: