The document at https://tc39.es/ecma426/ is the most accurate and up-to-date source map specification. It contains the content of the most recently published snapshot plus any modifications that will be included in the next snapshot.
Contributing to this Specification
This specification is developed on GitHub. There are a number of ways to contribute to the development of this specification:
Refer to the colophon for more information on how this document is created.
Introduction
This Ecma Standard defines the Source map format, used for mapping transpiled source code back to the original sources.
The source map format has the following goals:
Support source-level debugging allowing bidirectional mapping
Support server-side stack trace deobfuscation
The original source map format (v1) was created by Joseph Schorr for use by Closure Inspector to enable source-level debugging of optimized JavaScript code (although the format itself is language agnostic). However, as the size of the projects using source maps expanded, the verbosity of the format started to become a problem. The v2 format (Source Map Revision 2 Proposal) was created by trading some simplicity and flexibility to reduce the overall size of the source map. Even with the changes made with the v2 version of the format, the source map file size was limiting its usefulness. The v3 format is based on suggestions made by Pavel Podivilov (Google).
The source map format does not have version numbers anymore, and it is instead hard-coded to always be "3".
In 2023-2024, the source map format was developed into a more precise Ecma standard, with significant contributions from many people. Further iteration on the source map format is expected to come from TC39-TG4.
This Standard defines the source map format, used by different types of developer tools to improve the debugging experience of code compiled to JavaScript, WebAssembly, and CSS.
2 Conformance
A conforming source map document is a JSON document that conforms to the structure detailed in this specification.
A conforming source map generator should generate documents which are conforming source map documents, and can be decoded by the algorithms in this specification without reporting any errors (even those which are specified as optional).
A conforming source map consumer should implement the algorithms specified in this specification for retrieving (where applicable) and decoding source map documents. A conforming consumer is permitted to ignore errors or report them without terminating where the specification indicates that an algorithm may optionally report an error.
3 References
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
This specification follows the same notational conventions as defined by ECMA-262 (Notational conventions), with the extensions defined in this section.
An implementation can choose different behaviors for different optional errors.
5 Terms and Definitions
For the purposes of this document, the following terms and definitions apply.
generated code
code which is generated by the compiler or transpiler.
original source
source code which has not been passed through a compiler or transpiler.
base64 VLQ
a base64-encoded variable-length quantity, where the most significant bit (the 6th bit) is used as the continuation bit, and the "digits" are encoded into the string least significant first, and where the least significant bit of the first digit is used as the sign bit.
Note 1
The values that can be represented by the base64 VLQ encoding are limited to 32-bit quantities until some use case for larger values is presented. This means that values exceeding 32-bits are invalid and implementations may reject them. The sign bit is counted towards the limit, but the continuation bits are not.
Note 2
The string "iB" represents a base64 VLQ with two digits. The first digit "i" encodes the bit pattern 0x100010, which has a continuation bit of 1 (the VLQ continues), a sign bit of 0 (non-negative), and the value bits 0x0001. The second digit B encodes the bit pattern 0x000001, which has a continuation bit of 0, no sign bit, and value bits 0x00001. The decoding of this VLQ string is the number 17.
Note 3
The string "V" represents a base64 VLQ with one digit. The digit "V" encodes the bit pattern 0x010101, which has a continuation bit of 0 (no continuation), a sign bit of 1 (negative), and the value bits 0x1010. The decoding of this VLQ string is the number -10.
source map URL
URL referencing the location of a source map from the generated code.
column
zero-based indexed offset within a line of the generated code, computed as UTF-16 code units for JavaScript and CSS source maps, and as byte indexes in the binary content (represented as a single line) for WebAssembly source maps.
Note 4
That means that "A" (LATIN CAPITAL LETTER A) measures as 1 code unit, and "🔥" (FIRE) measures as 2 code units. Source maps for other content types may diverge from this.
6 JSON values utilities
While this specification's algorithms are defined on top of ECMA-262 internals, it is meant to be easily implementable by non-JavaScript platforms. This section contains utilities for working with JSON values, abstracting away ECMA-262 details from the rest of the document.
This abstract operation is in the process of being exposed by ECMA-262 itself, at tc39/ecma262#3540.
6.2 JSONObjectGet ( object, key )
The abstract operation JSONObjectGet takes arguments object (a JSON object) and key (a String) and returns a JSON value or missing. It returns the value associated with the specified key in object. It performs the following steps when called:
If object does not have an own property with key key, return missing.
Let prop be object's own property whose key is key.
Return prop's [[Value]] attribute.
6.3 JSONArrayIterate ( array )
The abstract operation JSONArrayIterate takes argument array (a JSON array) and returns a List of JSON values. It returns a List containing all elements of array, so that it can be iterated by algorithms using "For each". It performs the following steps when called:
The abstract operation StringSplit takes arguments string (a String) and separators (a List of String) and returns a List of Strings. It splits the string in substrings separated by any of the elements of separators. If multiple separators match, those appearing first in separators have higher priority. It performs the following steps when called:
The version field shall always be the number 3 as an integer. The source map may be rejected if the field has any other value.
The file field is an optional name of the generated code that this source map is associated with. It's not specified if this can be an URL, relative path name, or just a base name. Source map generators may choose the appropriate interpretation for their contexts of use.
The sourceRoot field is an optional source root string, used for relocating source files on a server or removing repeated values in the sources entry. This value is prepended to the individual entries in the sources field.
The sources field is a list of original sources used by the mappings field. Each entry is either a string that is a (potentially relative) URL or null if the source name is not known.
The sourcesContent field is an optional list of source content (i.e. the original source) strings, used when the source cannot be hosted. The contents are listed in the same order as in the sources field. Entries may be null if some original sources should be retrieved by name.
The names field is an optional list of symbol names which may be used by the mappings field.
The mappings field is a string with the encoded mapping data (see section 7.2).
The ignoreList field is an optional list of indices of files that should be considered third party code, such as framework code or bundler-generated code. This allows developer tools to avoid code that developers likely don't want to see or step through, without requiring developers to configure this beforehand. It refers to the sources field and lists the indices of all the known third-party sources in the source map. Some browsers may also use the deprecated x_google_ignoreList field if ignoreList is not present.
7.1 Decoding source maps
A Decoded Source Map Record has the following fields:
The abstract operation ParseSourceMap takes arguments string (a String) and baseURL (an URL) and returns a Decoded Source Map Record. It performs the following steps when called:
The abstract operation DecodeSourceMap takes arguments json (a JSON object) and baseURL (an URL) and returns a Decoded Source Map Record. It performs the following steps when called:
Let mappings be DecodeMappings(mappingsField, namesField, sources).
Let sourceMap be the Decoded Source Map Record { [[File]]: fileField, [[Sources]]: sources, [[Mappings]]: mappings }.
7.1.2.1 GetOptionalString ( object, key )
The abstract operation GetOptionalString takes arguments object (a JSON object) and key (a String) and returns a String or null. It performs the following steps when called:
The abstract operation GetOptionalListOfStrings takes arguments object (a JSON object) and key (a String) and returns a List of Strings. It performs the following steps when called:
The abstract operation GetOptionalListOfOptionalStrings takes arguments object (a JSON object) and key (a String) and returns a List of either Strings or null. It performs the following steps when called:
The abstract operation GetOptionalListOfArrayIndexes takes arguments object (an Object) and key (a String) and returns a List of non-negative integers. It performs the following steps when called:
each group representing a line in the generated file is separated by a semicolon (;)
each segment is separated by a comma (,)
each segment is made up of 1, 4, or 5 variable length fields.
The fields in each segment are:
The zero-based starting column of the line in the generated code that the segment represents. If this is the first field of the first segment, or the first segment following a new generated line (;), then this field holds the whole base64 VLQ. Otherwise, this field contains a base64 VLQ that is relative to the previous occurrence of this field. Note that this is different from the subsequent fields below because the previous value is reset after every generated line.
If present, the zero-based index into the sources list. This field contains a base64 VLQ relative to the previous occurrence of this field, unless it is the first occurrence of this field, in which case the whole value is represented.
If present, the zero-based starting line in the original source. This field contains a base64 VLQ relative to the previous occurrence of this field, unless it is the first occurrence of this field, in which case the whole value is represented. Shall be present if there is a source field.
If present, the zero-based starting column of the line in the original source. This field contains a base64 VLQ relative to the previous occurrence of this field, unless it is the first occurrence of this field, in which case the whole value is represented. Shall be present if there is a source field.
If present, the zero-based index into the names list associated with this segment. This field contains a base64 VLQ relative to the previous occurrence of this field, unless it is the first occurrence of this field, in which case the whole value is represented.
Note 1
The purpose of this encoding is to reduce the source map size. VLQ encoding reduced source maps by 50% relative to the Source Map Revision 2 Proposal in tests performed using Google Calendar.
Note 2
Segments with one field are intended to represent generated code that is unmapped because there is no corresponding original source code, such as code that is generated by a compiler. Segments with four fields represent mapped code where a corresponding name does not exist. Segments with five fields represent mapped code that also has a mapped name.
Note 3
Using file offsets was considered but rejected in favor of using line/column data to avoid becoming misaligned with the original due to platform-specific line endings.
A Decoded Mapping Record has the following fields:
The abstract operation DecodeMappings takes arguments mappings (a String), names (a List of Strings), and sources (a List of Decoded Source Records) and returns a List of Decoded Mapping Record. It performs the following steps when called:
The abstract operation ValidateBase64VLQGroupings takes argument groupings (a String) and returns unused. It performs the following steps when called:
If groupings contains any code unit other than:
U+002B (+), U+002C (,), U+002F (/), or U+003B (;);
U+0030 (0) to U+0039 (9);
U+0041 (A) to U+005A (Z);
U+0061 (a) to U+007A (z)
throw an error.
Return unused.
Note
These are the valid base64 characters (excluding the padding character =), together with , and ;.
7.2.1.2 DecodeBase64VLQ ( segment, position )
The abstract operation DecodeBase64VLQ takes arguments segment (a String) and position (a Record with a non-negative integer[[Value]] field) and returns an integer or null. It performs the following steps when called:
7.2.1.2.1 ConsumeBase64ValueAt ( string, position )
The abstract operation ConsumeBase64ValueAt takes arguments string (a String) and position (a Record with a non-negative integer[[Value]] field) and returns a non-negative integer. It performs the following steps when called:
Assert: position.[[Value]] is a non-negative integer smaller than the length of string.
Let char be the substring of string from position to position + 1.
Assert: char is a valid base64 character as defined by IETF RFC 4648.
Set position.[[Value]] to position.[[Value]] + 1.
Return the integer corresponding to char, according to the base64 encoding as defined by IETF RFC 4648.
Note
In addition to returning the decoded value, these algorithms update the position passed in by the caller.
Then the [[Name]] of the mapping entry should be the name of the original source language construct. A mapping with a non-null [[Name]] is called a named mapping.
Note 1
A minifier renaming functions and variables or removing function names from immediately invoked function expressions.
The following enumeration lists productions of the ECMAScript Syntactic Grammar and the respective token or non-terminal (on the right-hand side of the production) for which source map generators should emit a named mapping. The mapping entry created for such tokens shall follow section 7.2.2.
The enumeration should be understood as the "minimum". In general, source map generators are free to emit any additional named mappings.
Note 2
The enumeration also lists tokens where generators "may" emit named mappings in addition to the tokens where they "should". These reflect the reality where existing tooling emits or expects named mappings. The duplicated named mapping is comparably cheap: Indices into names are encoded relative to each other so subsequent mappings to the same name are encoded as 0 (A).
Source map generators may chose to additionally emit a named mapping on the opening parenthesis (.
Source map generators may emit named mapping for IdentifierReference| in |Expression|.
7.3 Resolving sources
If the sources are not absolute URLs after prepending the sourceRoot, the sources are resolved relative to the source map (like resolving the script src attribute in an HTML document).
The abstract operation DecodeSourceMapSources takes arguments baseURL (an URL), sourceRoot (a String or null), sources (a List of either Strings or null), sourcesContent (a List of either Strings or null), and ignoreList (a List of non-negative integers) and returns a Decoded Source Record. It performs the following steps when called:
If ignoredSources contains index, set decodedSource.[[Ignored]] to true.
If sourcesContentCount > index, set decodedSource.[[Content]] to sourcesContent[index].
Append decodedSource to decodedSources.
Return decodedSources.
Note
Implementations that support showing source contents but do not support showing multiple sources with the same URL and different content will arbitrarily choose one of the various contents corresponding to the given URL.
7.4 Extensions
Source map consumers shall ignore any additional unrecognized properties, rather than causing the source map to be rejected, so that additional features can be added to this format without breaking existing users.
8 Index source map
To support concatenating generated code and other common post-processing, an alternate representation of a source map is supported:
The index map follows the form of the standard map. Like the regular source map, the file format is JSON with a top-level object. It shares the version and file field from the regular source map, but gains a new sections field.
The sections field is an array of objects with the following fields:
offset field is an object with two fields, line and column, that represent the offset into generated code that the referenced source map represents.
map field is an embedded complete source map object. An embedded map does not inherit any values from the containing index map.
The sections shall be sorted by starting position and the represented sections shall not overlap.
8.1 DecodeIndexSourceMap ( json, baseURL )
The abstract operation DecodeIndexSourceMap takes arguments json (an Object) and baseURL (an URL) and returns a Decoded Source Map Record. It performs the following steps when called:
Let sectionsField be JSONObjectGet(json, "sections").
If offsetLine = previousLastMapping.[[GeneratedLine]] and offsetColumn < previousLastMapping.[[GeneratedColumn]], optionally report an error.
NOTE: This part of the decoding algorithm checks that entries of the sections field of index source maps are ordered and do not overlap. While it is expected that generators should not produce index source maps with overlapping sections, source map consumers may, for example, only check the simpler condition that the section offsets are ordered.
If sortedMappings is not empty, set previousLastMapping to the last element of sortedMappings.
Return sourceMap.
Note
Implementations may choose to represent index source map sections without appending the mappings together, for example, by storing each section separately and conducting a binary search.
8.1.1 GeneratedPositionLessThan ( a, b )
The abstract operation GeneratedPositionLessThan takes arguments a (a Decoded Mapping Record) and b (a Decoded Mapping Record) and returns a Boolean. It performs the following steps when called:
If a.[[GeneratedLine]] < b.[[GeneratedLine]], return true.
If a.[[GeneratedLine]] = b.[[GeneratedLine]] and a.[[GeneratedColumn]] < b.[[GeneratedColumn]], return true.
Return false.
9 Retrieving source maps
9.1 Linking generated code to source maps
While the source map format is intended to be language and platform agnostic, it is useful to define how to reference to them for the expected use-case of web server-hosted JavaScript.
There are two possible ways to link source maps to the output. The first requires server support in order to add an HTTP header and the second requires an annotation in the source.
Source maps are linked through URLs as defined in WHATWG URL; in particular, characters outside the set permitted to appear in URIs shall be percent-encoded and it may be a data URI. Using a data URI along with sourcesContent allows for a completely self-contained source map.
The HTTP sourcemap header has precedence over a source annotation, and if both are present, the header URL should be used to resolve the source map file.
Regardless of the method used to retrieve the source map URL the same process is used to resolve it, which is as follows.
If the generated source is not associated with a script element that has a src attribute and there exists a //# sourceURL comment in the generated code, that comment should be used to determine the source origin.
Note
Previously, this was //@ sourceURL, as with //@ sourceMappingURL, it is reasonable to accept both but //# is preferred.
If the generated code is associated with a script element and the script element has a src attribute, the src attribute of the script element will be the source origin.
If the generated code is associated with a script element and the script element does not have a src attribute, then the source origin will be the page's origin.
If the generated code is being evaluated as a string with the eval() function or via new Function(), then the source origin will be the page's origin.
9.1.1 Linking through HTTP headers
If a file is served through HTTP(S) with a sourcemap header, the value of the header is the URL of the linked source map.
sourcemap: <url>
Note
Previous revisions of this document recommended a header name of x-sourcemap. This is now deprecated; sourcemap is now expected.
9.1.2 Linking through inline annotations
The generated code should include a comment, or the equivalent construct depending on its language or format, named sourceMappingURL and that contains the URL of the source map. This specification defines how the comment should look like for JavaScript, CSS, and WebAssembly. Other languages should follow a similar convention.
For a given language there can be multiple ways of detecting the sourceMappingURL comment, to allow for different implementations to choose what is less complex for them. The generated code unambiguously links to a source map if the result of all the extraction methods is the same.
Having multiple ways to extract a source map URL, that can lead to different results, can have negative security and privacy implications. Implementations that need to detect which source maps are potentially going to be loaded are strongly encouraged to always apply both algorithms, rather than just assuming that they will give the same result.
A fix to this problem is being worked on, and is expected to be included in a future version of the standard. It will likely involve early returning from the below algorithms whenever there is a comment (or comment-like) that contains the characters U+0060 (`), U+0022 ("), or U+0027 ('), or the the sequence U+002A U+002F (*/).
9.1.2.1 JavaScriptExtractSourceMapURL ( source )
The abstract operation JavaScriptExtractSourceMapURL takes argument source (a String) and returns a String or null. It extracts a source map URL from a JavaScript source. It has two possible implementations: either through parsing or without parsing.
If sourceMapURLis a String, set lastURL to sourceMapURL.
Append c1 to commentCp.
Else, set lastURL to null.
Else if first is not an ECMAScript WhiteSpace, then
Set lastURL to null.
NOTE: We reset lastURL to null whenever we find a non-comment code character.
Return lastURL.
Note 1
The algorithm above has been designed so that the source lines can be iterated in reverse order, returning early after scanning through a line that contains a sourceMappingURL comment.
Note 2
The algorithm above is equivalent to the following JavaScript implementation:
constJS_NEWLINE = /^/m;
// This RegExp will always match one of the following:// - single-line comments// - "single-line" multi-line comments// - unclosed multi-line comments// - just trailing whitespaces// - a code character// The loop below differentiates between all these cases.constJS_COMMENT =
/\s*(?:\/\/(?<single>.*)|\/\*(?<multi>.*?)\*\/|\/\*.*|$|(?<code>[^\/]+))/uym;
constPATTERN = /^[@#]\s*sourceMappingURL=(\S*?)\s*$/;
let lastURL = null;
for (const line of source.split(JS_NEWLINE)) {
JS_COMMENT.lastIndex = 0;
while (JS_COMMENT.lastIndex < line.length) {
let commentMatch = JS_COMMENT.exec(line).groups;
let comment = commentMatch.single ?? commentMatch.multi;
if (comment != null) {
let match = PATTERN.exec(comment);
if (match !== null) lastURL = match[1];
} elseif (commentMatch.code != null) {
lastURL = null;
} else {
// We found either trailing whitespaces or an unclosed comment.// Assert: JS_COMMENT.lastIndex === line.length
}
}
}
return lastURL;
9.1.2.1.1 MatchSourceMapURL ( comment )
The abstract operation MatchSourceMapURL takes argument comment (a String) and returns either NONE or a String. It performs the following steps when called:
Let pattern be RegExpCreate("^[@#]\s*sourceMappingURL=(\S*?)\s*$", "").
The prefix for this annotation was initially //@, however this conflicts with Internet Explorer's Conditional Compilation and was changed to //#.
Source map generators shall only emit //#, while source map consumers shall accept both //@ and //#.
9.1.2.2 CSSExtractSourceMapURL ( source )
The abstract operation CSSExtractSourceMapURL takes argument source (a String) and returns a String or null. It extracts a source map URL from a CSS source.
Extracting source map URLs from CSS is similar to JavaScript, with the exception that CSS only supports /* ... */-style comments.
9.1.2.3 WebAssemblyExtractSourceMapURL ( bytes )
The abstract operation WebAssemblyExtractSourceMapURL takes argument bytes (a Data Block) and returns a String or null. It extracts a source map URL from a WebAssembly binary source.
Since WebAssembly is not a textual format and it does not support comments, it supports a single unambiguous extraction method. The URL is encoded as a WebAssembly name, and it's placed as the content of the custom section. It is invalid for tools that generate WebAssembly code to generate two or more custom sections with the sourceMappingURL name.
9.2 Fetching source maps
9.2.1 FetchSourceMap ( url )
The abstract operation FetchSourceMap takes argument url (an URL) and returns a Promise. It performs the following steps when called:
For historic reasons, when delivering source maps over HTTP(S), servers may prepend a line starting with the string )]}' to the source map.
)]}'garbage here
{"version":3, ...}
is interpreted as
{"version":3, ...}
A Conventions
The following conventions should be followed when working with source maps or when generating them.
A.1 Source map naming
Commonly, a source map will have the same name as the generated file but with a .map extension. For example, for page.js a source map named page.js.map would be generated.
A.2 Linking eval'd code to named generated code
There is an existing convention that should be supported for the use of source maps with eval'd code, it has the following form:
Stack tracing mapping without knowledge of the source language is not covered by this document.
B.2 Multi-level mapping
It is getting more common to have tools generate sources from some DSL (templates) or compile TypeScript → JavaScript → minified JavaScript, resulting in multiple translations before the final source map is created. This problem can be handled in one of two ways. The easy but lossy way is to ignore the intermediate steps in the process for the purposes of debugging, the source location information from the translation is either ignored (the intermediate translation is considered the “Original Source”) or the source location information is carried through (the intermediate translation hidden). The more complete way is to support multiple levels of mapping: if the Original Source also has a source map reference, the user is given the choice of using that as well.
However, it is unclear what a "source map reference" looks like in anything other than JavaScript. More specifically, what a source map reference looks like in a language that doesn't support JavaScript-style single-line comments.
C Terms defined in other specifications
This section lists all terms and algorithms used by this document defined by external specifications other than ECMA-262.
This specification is authored on GitHub in a plaintext source format called Ecmarkup. Ecmarkup is an HTML and Markdown dialect that provides a framework and toolset for authoring ECMAScript specifications in plaintext and processing the specification into a full-featured HTML rendering that follows the editorial conventions for this document. Ecmarkup builds on and integrates a number of other formats and technologies including Grammarkdown for defining syntax and Ecmarkdown for authoring algorithm steps. PDF renderings of this specification are produced by printing the HTML rendering to a PDF.
The first edition of this specification was authored using Bikeshed, a different plaintext source format based on HTML and Markdown.
Pre-standard versions of this document were authored using Google Docs.
This draft document may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to Ecma International, except as needed for the purpose of developing any document or deliverable produced by Ecma International.
This disclaimer is valid only prior to final version of this document. After approval all rights on the standard are reserved by Ecma International.
The limited permissions are granted through the standardization phase and will not be revoked by Ecma International or its successors or assigns during this time.
This document and the information contained herein is provided on an "AS IS" basis and ECMA INTERNATIONAL DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Software License
All Software contained in this document ("Software") is protected by copyright and is being made available under the "BSD License", included below. This Software may be subject to third party rights (rights from parties other than Ecma International), including patent rights, and no licenses under such third party rights are granted under this license even if the third party concerned is a member of Ecma International. SEE THE ECMA CODE OF CONDUCT IN PATENT MATTERS AVAILABLE AT https://ecma-international.org/memento/codeofconduct.htm FOR INFORMATION REGARDING THE LICENSING OF PATENT CLAIMS THAT ARE REQUIRED TO IMPLEMENT ECMA INTERNATIONAL STANDARDS.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the authors nor Ecma International may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE ECMA INTERNATIONAL "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ECMA INTERNATIONAL BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.