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
{{ message }}
This repository has been archived by the owner on Jun 27, 2023. It is now read-only.
Though it is worth noting that we purposefully removed a reference to such APIs from our charter during drafting in an effort to trim our scope. Doesn't mean we can't expand to such APIs (Collection API, Publication object model), but it doesn't seem a required deliverable.
My preference would be to punt any talk about such an API down the road, largely because if we let it wait a bit, the odds of us being able to do an API like that well increase dramatically.
Once you have a JSON-based manifest (or any sort of manifest JS in the browser can parse) then we can start experimenting with writing JS libraries that offer such an API. And if those work, then we can use that experience to polyfill the API to see what that would work like. And if that works, and if it poses to offer an actual advantage over external libraries, then we can put together a spec based on our experience.
So, my suggestion is to put it on the back burner.
Our White Paper talks about the need for an interface and API for a collection of web resources. So really all we have to do is figure this out:
Perhaps something like this, more than anything else we are discussing, is what it means for publications to be a first-class citizen of the web.
The text was updated successfully, but these errors were encountered: