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

Tools for converting standard to vendor specific implementations #170

Open
MichaelWangzitao opened this issue Aug 18, 2021 · 2 comments
Open

Tools for converting standard to vendor specific implementations #170

MichaelWangzitao opened this issue Aug 18, 2021 · 2 comments

Comments

@MichaelWangzitao
Copy link

The Working Group has released two Working Group Drafts, Manifest, and Lifecycle. Meanwhile, various vendors have some pre-standard implementations. IMO, it makes sense to discuss how to develop a demo tool to implement conversion from standard to vendor deployment, such as converting standard manifest.json into manifest.json deployed by various vendors. If it goes well, we can present it at this year's TPAC.
@MichaelWangzitao MichaelWangzitao changed the title Tools for converting standard to existing implementations Tools for converting standard to vendor specific implementations Aug 19, 2021
@xfq
Copy link
Member

xfq commented Aug 20, 2021

Related discussions: https://www.w3.org/2021/08/19-miniapp-minutes.html#t03

@Sharonzd
Copy link
Contributor

It looks good to me.
But how to collaborate?
Should each vendor develop a separate tool, or should we work together to develop a tool which supports exporting different json based on different parameters

@QingAn QingAn mentioned this issue Sep 17, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xfq @Sharonzd @MichaelWangzitao