With all critics on ads and tracking in the browser and US government initiative on secure apps stack, I see no other way then create an #OSS browser as a platform. Capable of #DeclarativeWebApplication embedding, approved apps policies enforcement as on browser settings as on user level.

I doubt JS based apps could give such security layer as declarative stack would.

#w3ctag , #webdev

@vanilla,
As of now the #webcomponent state is treated as 2nd class citizen by #w3c

. For now only state which is permitted on declarative syntax is either attributes or payload DOM. Which actually meant for visual and initial state, not the heavy-duty transactional model. If WC would be able to produce and consume the state without custom serialization, it would work on all tiers.

There is a proposal to make it a part of web stack.

Working on it as part of #DeclarativeWebApplication

#DeclarativeWebApplication stack would not be complete without URL and window APIs exposed declaratively. First AC for location #webcomponents which would expose the API as data slice.

https://github.com/EPA-WG/custom-element/issues/16

Dear colleagues, next week on april 20 on WCCG conference I will be presenting the #DeclarativeWebApplication concept to the #W3C community and browser vendors. If you like the idea or find it useful for your web applications, please support it by voting up the 1st w3c proposal from DWA stack.

https://github.com/WICG/webcomponents/issues/997

🤔 #DeclarativeWebApplication needs the connection between events from elements and actions.

As an option, the event woiuld populate own data slice leading to template re-render whre the event slice would be processed.

The syntax of event binding to element and data slice is not clear to me.

<el onclick="this.getRootNode().updateSlice("el-events", event)>

Is blurring my mind. Need the idea of binding declaratively instead .

🇺🇸 ❤️ 🇺🇦

#DeclarativeWebApplication manifesto 1st draft created. It sounds too good and futuristic but some of it already covered by POC and parts of its stack are under #WICG review.

https://github.com/EPA-WG/dwa#readme

@w3c , @w3cdevs

#webdev would find the new(?) concept of data slices in scope of #DeclarativeCustomElement . local-storage and http-request are part of its stack and their data are live updating the #xslt based templates.

#DeclarativeWebApplication is one step closer.

CC @rniwa

https://unpkg.com/@epa-wg/custom-element@0.0.9/demo/http-request.html

#webdev world get used to insulation, no side effects concept. #webcomponent and react just to name if few. Besides of IFRAME the html standard have not adopted much of such significant pattern yet. HTC has given a big promise but seems to be ahead of time by the century.
Now in web 3.0 world where apps from different vendor live on same page, the insulation and coordination become a desperate need.

In the scope of #DeclarativeWebApplication

#wicg proposals are coming

The theoretical concept of data layer in #DeclarativeWebApplication materialized as `local-storage` #webcomponent which feeds string or JSON data into `@epa-wg/custom-element` template. The `live` attribute animates the shopping card updates from localStorage in real time in demo.

Following implementation of `http-request` would make the concept POC sufficient to be used in real products.

@w3cdevs , thinking how to define the data schema in #DeclarativeWebApplication, in another words inline in HTML.
Data source in #XML used XSD, in GraphQL - another weird lingo... is there a sane and simple HTML-friendly format for schema definition?

Do not propose yaml, please.
#xslt