publish branch

ABOUT THIS DOCUMENT

This is non-normative, and intended to help readers of the EN-304-617 standard to understand more about how we approached writing the document, and how you should read it.

GUIDANCE DOCUMENT

Keep minimally in scope??? (Fukami)

Only important & critical get conformity from these standards

If you aren't "important" enough, you don't have 

Generally Not in Scope (guidance):

- Electron-type apps are not browsing. The fact that they can send queries to websites is not the same thing. They are standalone application.

- Desktop apps will use an embedded webview that then show Help pages that are online. It might be using e.g. an embedded webview, but ONLY allows the user to do this.

- "dumb" retrieval tools

- Postman from a functional level, is not intended to "browse the internet", it is a tool for testing endpoints

- Intended purpose is not "browsing"

    - If there is no possibility, architecturally, that an intended use or reasonable foreseeable misuse is to "browse the world wide web" then out of scope.

Electron Analysis

    low-risk = documentation shown on the web in the embedded context / man pages as an electron app 

               curl can still be low risk...

    med-risk = javascript interpreter

    high-risk= consume remote resources