Skip to content
This repository was archived by the owner on Feb 26, 2025. It is now read-only.
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 47 additions & 0 deletions spec.bs
Original file line number Diff line number Diff line change
Expand Up @@ -569,3 +569,50 @@ Alternatively, we can add the snippet at the beginning of the following HTML spe
</div>

<p class="note">[=Validate a module script URL=] is applied to all module URLs before they start loading, even in paths where [=resolve a module specifier=] and import maps are not applied (e.g. `<script src="..." type="module">`).</p>

<hr>
<h2 id="internet-media-type-registration">Appendix A: MIME type registration</h2>

This appendix provides the provisional registration of the [=MIME type=] <dfn export>`application/importmap+json`</dfn> `application/importmap+json` in accordance with [[RFC6838]].

: Type name:
:: application
: Subtype name:
:: importmap+json
: Required parameters:
:: N/A
: Optional parameters:
:: N/A
: Encoding considerations:
:: 8bit (always UTF-8)
: Security considerations:
:: Since Import Maps have the ability to direct which module resolutions are to be provided to all module imports of a given JavaScript environment, control of the Import Map should be considered to be execution-level application access. Integration with existing policy systems, including for example CORS and CSP, can be used to mitigate and restrict unwanted target URLs from being executed. In addition, the specification states that only those Import Maps served to browsers with the `application/importmap+json` MIME type will be executed. [[FETCH]] [[CSP]]
: Interoperability considerations:
:: Backwards compatibility will be a necessity for any new features added to the format, and handling for this has been incorporated into the design of the specification.
: Published specification:
:: https://wicg.github.io/import-maps/
: Applications that use this media type:
:: This is a browser-specific MIME type but may also apply to other JavaScript environments.
: Fragment identifier considerations:
:: N/A
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove N/A sections?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since these are part of the template, we need to leave them in explicitly.

: Additional information:
<dd>
<dl>
: Deprecated alias names for this type:
:: N/A
: Magic number(s)
:: N/A
: File extension(s):
:: "importmap"
: Macintosh file type code:
:: Same as for `application/json` [[JSON]]
</dl>
</dd>
: Person & email address to contact for further information:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wseltzer / @plehegar - Thoughts on the right contact person here?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't recommend putting individual email address there since it needs to survive individuals moving on but I have no objection if you folks feels otherwise. At the end of the day, the best way to reach out is through GitHub as far as I know.
Basically, we'd need an email address that someone can see and redirect to the right person if needed. Some ideas, with various pros/cons:

:: Guy Bedford &lt;guybedford@gmail.com>.
: Intended usage:
:: Common
: Restrictions on usage:
Comment thread
guybedford marked this conversation as resolved.
:: No restrictions apply.
: Change controller:
:: WHATWG