Device SWD\PRINTENUM\was configured.
Driver Name: printqueue.inf
Class Guid:
Driver Date: 06/21/2006
Driver Version: 10.0.22000.1
Driver Provider: Microsoft
Driver Section: NO_DRV_LOCAL
Driver Rank: 0x0
Matching Device Id: PRINTENUM\LocalPrintQueue
Outranked Drivers: c_swdevice.inf:SWD\GenericRaw:00FF3001
Device Updated: false
Parent Device: USBPRINT\EPSONL360_Series\7&109f90d2&0&USB003
Every extension for Microsoft Edge has a JSON-formatted manifest file, named manifest.json. The manifest file is the blueprint of your extension. The manifest file includes information such as:
The format for manifest.json for extensions is moving from Manifest V2 to Manifest V3. Both formats are shown here. To migrate a Manifest V2 extension to Manifest V3, see Migrate an extension from Manifest V2 to V3.
The following code shows the fields that are supported in manifest.json for extensions, for a Manifest V3 package.
For reference information about each field, see Manifest file format (V3) and then select the links on the fields.
{
// Required
"manifest_version": 3,
"name": "My V3 Extension",
"version": "versionString",
// Recommended
"action": {...},
"default_locale": "en",
"description": "A plain-text description",
"icons": {...},
// Optional
"action": ...,
"author": ...,
"automation": ...,
"background": {
// If `background` is included, `service_ worker` is required
"service_worker": ...
},
"chrome_settings_overrides": {...},
"chrome_url_overrides": {...},
"commands": {...},
"content_capabilities": ...,
"content_scripts": [{...}],
"content_security_policy": "policyString",
"converted_from_user_script": ...,
"current_locale": ...,
"declarative_net_request": ...,
"devtools_page": "devtools.html",
"differential_fingerprint": ...,
"event_rules": [{...}],
"externally_connectable": {
"matches": ["*://*.contoso.com/*"]
},
"file_browser_handlers": [...],
"file_system_provider_capabilities": {
"configurable": true,
"multiple_mounts": true,
"source": "network"
},
"homepage_url": "http://path/to/homepage",
"host_permissions": [...],
"import": [{"id": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"}],
"incognito": "spanning, split, or not_allowed",
"input_components": ...,
"key": "publicKey",
"minimum_chrome_version": "versionString",
"nacl_modules": [...],
"natively_connectable": ...,
"oauth2": ...,
"offline_enabled": true,
"omnibox": {
"keyword": "aString"
},
"optional_permissions": ["tabs"],
"options_page": "options.html",
"options_ui": {
"chrome_style": true,
"page": "options.html"
},
"permissions": ["tabs"],
"platforms": ...,
"replacement_web_app": ...,
"requirements": {...},
"sandbox": [...],
"short_name": "Short Name",
"storage": {
"managed_schema": "schema.json"
},
"system_indicator": ...,
"tts_engine": {...},
"update_url": "http://path/to/updateInfo.xml",
"version_name": "aString",
"web_accessible_resources": [...]
}
The following code shows the fields that are supported in manifest.json for extensions, for a Manifest V2 package.
For reference information about each field, see Manifest file format (V2) and then select the links on the fields.
{
// Required
"manifest_version": 2,
"name": "My V2 Extension",
"version": "versionString",
// Recommended
"default_locale": "en",
"description": "A plain-text description",
"icons": {...},
// Pick one or none
"browser_action": {...},
"page_action": {...},
// Optional
"action": ...,
"author": ...,
"automation": ...,
"background": {
// If `background` is included, `persistent` is recommended
"persistent": false,
// If `background` is included, `service_worker` is optional
"service_worker": ...
},
"chrome_settings_overrides": {...},
"chrome_url_overrides": {...},
"commands": {...},
"content_capabilities": ...,
"content_scripts": [{...}],
"content_security_policy": "policyString",
"converted_from_user_script": ...,
"current_locale": ...,
"declarative_net_request": ...,
"devtools_page": "devtools.html",
"differential_fingerprint": ...,
"event_rules": [{...}],
"externally_connectable": {
"matches": ["*://*.contoso.com/*"]
},
"file_browser_handlers": [...],
"file_system_provider_capabilities": {
"configurable": true,
"multiple_mounts": true,
"source": "network"
},
"homepage_url": "http://path/to/homepage",
"host_permissions": ...,
"import": [{"id": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"}],
"incognito": "spanning, split, or not_allowed",
"input_components": ...,
"key": "publicKey",
"minimum_chrome_version": "versionString",
"nacl_modules": [...],
"natively_connectable": ...,
"oauth2": ...,
"offline_enabled": true,
"omnibox": {
"keyword": "aString"
},
"optional_permissions": ["tabs"],
"options_page": "options.html",
"options_ui": {
"chrome_style": true,
"page": "options.html"
},
"permissions": ["tabs"],
"platforms": ...,
"replacement_web_app": ...,
"requirements": {...},
"sandbox": [...],
"short_name": "Short Name",
"storage": {
"managed_schema": "schema.json"
},
"system_indicator": ...,
"tts_engine": {...},
"update_url": "http://path/to/updateInfo.xml",
"version_name": ...,
"web_accessible_resources": [...]
}
Note
Portions of this page are modifications based on work created and shared by Google and used according to terms described in the Creative Commons Attribution 4.0 International License. The original page is found here.
Untuk lebih lengkap silahkan hubungi link berikut di bawah ini:
Manifest file format for extensions - Microsoft Edge Development | Microsoft Docs
https://www.rfc-editor.org/rfc/rfc4287.html
The Atom Syndication Format Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document specifies Atom, an XML-based Web content and metadata syndication format. Table of Contents 1. Introduction ....................................................3 1.1. Examples ...................................................3 1.2. Namespace and Version ......................................5 1.3. Notational Conventions .....................................5 2. Atom Documents ..................................................6 3. Common Atom Constructs ..........................................7 3.1. Text Constructs ............................................7 3.1.1. The "type" Attribute ................................8 3.2. Person Constructs .........................................10 3.2.1. The "atom:name" Element ............................10 3.2.2. The "atom:uri" Element .............................10 3.2.3. The "atom:email" Element ...........................10 3.3. Date Constructs ...........................................10 4. Atom Element Definitions .......................................11 4.1. Container Elements ........................................11 4.1.1. The "atom:feed" Element ............................11 4.1.2. The "atom:entry" Element ...........................13 4.1.3. The "atom:content" Element .........................14 4.2. Metadata Elements .........................................17 4.2.1. The "atom:author" Element ..........................17 4.2.2. The "atom:category" Element ........................18 4.2.3. The "atom:contributor" Element .....................18 Nottingham & Sayre Standards Track [Page 1]
RFC 4287 Atom Format December 2005 4.2.4. The "atom:generator" Element .......................18 4.2.5. The "atom:icon" Element ............................19 4.2.6. The "atom:id" Element ..............................19 4.2.7. The "atom:link" Element ............................21 4.2.8. The "atom:logo" Element ............................23 4.2.9. The "atom:published" Element .......................23 4.2.10. The "atom:rights" Element .........................24 4.2.11. The "atom:source" Element .........................24 4.2.12. The "atom:subtitle" Element .......................25 4.2.13. The "atom:summary" Element ........................25 4.2.14. The "atom:title" Element ..........................25 4.2.15. The "atom:updated" Element ........................25 5. Securing Atom Documents ........................................26 5.1. Digital Signatures ........................................26 5.2. Encryption ................................................27 5.3. Signing and Encrypting ....................................28 6. Extending Atom .................................................28 6.1. Extensions from Non-Atom Vocabularies .....................28 6.2. Extensions to the Atom Vocabulary .........................28 6.3. Processing Foreign Markup .................................28 6.4. Extension Elements ........................................29 6.4.1. Simple Extension Elements ..........................29 6.4.2. Structured Extension Elements ......................29 7. IANA Considerations ............................................30 7.1. Registry of Link Relations ................................31 8. Security Considerations ........................................31 8.1. HTML and XHTML Content ....................................31 8.2. URIs ......................................................31 8.3. IRIs ......................................................31 8.4. Spoofing ..................................................31 8.5. Encryption and Signing ....................................32 9. References .....................................................32 9.1. Normative References ......................................32 9.2. Informative References ....................................34 Appendix A. Contributors ..........................................35 Appendix B. RELAX NG Compact Schema ...............................35 Nottingham & Sayre Standards Track [Page 2]