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

Metadata related to a script to let a runtime decide in which execution context it should run #29

Closed
h0ru5 opened this issue Jun 12, 2017 · 3 comments
Labels
Runtime Runtime-related topics Script Management How to manage/control scripts

Comments

@h0ru5
Copy link
Contributor

h0ru5 commented Jun 12, 2017

In a joint call between scripting TF an Security TF we identified that a runtime should be enabled to determine in which execution context (referring to this image) it should be run by metadata provided to it or/and by implicit rules / policies (i.e. in the absence of explicit metadata).

One prominent example from the web of pages is the origin, the same-origin-policy and cross-origin-resource-sharing.
However, this is just one example for related metadata.

We will go a twofold approach to drive this topic forward:

  • identifying examples for metadata that is/can be relevant
  • reaching out to groups / experts to discuss existing/ongoing work in this area
@h0ru5
Copy link
Contributor Author

h0ru5 commented Jun 12, 2017

@h0ru5
Copy link
Contributor Author

h0ru5 commented Jun 12, 2017

others were iot.schema.org and their work on metadata for executables / mobile code

@zolkis zolkis added Runtime Runtime-related topics Script Management How to manage/control scripts labels Sep 4, 2017
@zolkis
Copy link
Contributor

zolkis commented Aug 22, 2019

We need to postpone this to a next charter.

@zolkis zolkis closed this as completed Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Runtime Runtime-related topics Script Management How to manage/control scripts
Projects
None yet
Development

No branches or pull requests

2 participants