@@ -154,10 +154,12 @@ This standard focuses on browsers, both standalone and embedded. Browsers are so
Within the context of an operating system, browsers are user-applications with a primary function and probable daily use. They are often leveraged as means of accessing remote authentication (single-sign-on) or even as a bridge (deep-link) to another application that has already been installed. In both cases, all systems have the notion of a “default browser” that can then be instrumented by other applications to navigate to a website or perform such an activity.
The activity of browsing can be defined in the following steps:
1. A machine acquires source code, such as HTML, JavaScript, and CSS.
1. A machine accesses remote resources and source code, such as HTML, JavaScript, and CSS.
2. This source is represented visually, acoustically, or in some other form.
3. The user interacts with this representation by looking, reading, entering data, clicking, etc.
## 1.1 Browser
### 1.1.1 Standalone
@@ -198,6 +200,24 @@ The following referenced documents may be useful in implementing an ETSI deliver
For the purposes of the present document, the [following] terms [given in ... and the following] apply:
/// THIS IS THE DEFINITION MADE BY THE EXPERT GROUP DO NOT EDIT
Browsers: In the context of this category of products, browsers are software products with digital elements that enable end users to access and interact with web content hosted on servers that are connected to networks such as the Internet.
///
End Users
Access
Interact <- this is the critical activity that defines browsing
Raw Content - XML, JSON, JS, etc.
Web Content - Displayed, rendered, etc. Representation of source code or data
Servers
Networks
Browser Extensions
Progessive Web Apps???
Custom Protocol???
Accessing Webcontent
Secondary functionalities: provide access to updates, installation scripts, validity of certificates
Browsers: In the context of this category of products, browsers are software products with digital elements that enable end users to access and interact with web content hosted on servers that are
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
