The following data sets provide information extracted from EX-101 exhibits submitted to the Commission in a flattened data format to assist users in more easily consuming the data for analysis. The data is sourced from selected information found in the XBRL tagged financial statements and notes submitted by filers to the Commission. These data sets currently include quarterly and annual numeric data appearing in the financial statements submitted by filers. Certain additional fields (e.g. Standard Industrial Classification (SIC)) used in the Commission's EDGAR system are also included to help in supporting the use of the data. The information has been taken directly from submissions created by each registrant, and the data is "as filed" by the registrant. The information will be updated quarterly. Data contained in documents filed after 5:30pm EST on the last business day of the quarter will be included in the next quarterly posting.

DISCLAIMER: The Financial Statement and Notes Data Sets contain information derived from structured data filed with the Commission by individual registrants as well as Commission-generated filing identifiers. Because the data sets are derived from information provided by individual registrants, we cannot guarantee the accuracy of the data sets. In addition, it is possible inaccuracies or other errors were introduced into the data sets during the process of extracting the data and compiling the data sets. Finally, the data sets do not reflect all available information, including certain metadata associated with Commission filings. The data sets are intended to assist the public in analyzing data contained in Commission filings; however, they are not a substitute for such filings. Investors should review the full Commission filings before making any investment decision.

The data extracted from the XBRL submissions is organized into eight data sets containing information about submissions, numbers, taxonomy tags, presentation, and more. Each data set consists of rows and fields, and is provided as a tab-delimited TXT format file. The data sets are as follows:

· SUB – Submission data set; this includes one record for each XBRL submission. The set includes fields of information pertinent to the submission and the filing entity. Information is extracted from the Commission's EDGAR system and the filings submitted to the Commission by registrants.

· TAG – Tag data set; includes defining information about each tag. Information includes tag descriptions (documentation labels), taxonomy version information and other tag attributes.

· DIM – Dimension data set; used to provide more detail in numeric and non-numeric facts.

· NUM – Number data set; this includes one row for each distinct amount from each submission included in the SUB data set. The Number data set includes, for every submission, all line item values as rendered by the Commission Viewer/Previewer.

· TXT – Text data set; this is the plain text of all the non-numeric tagged items in the submission.

· REN – Rendering data set; this contains data from the rendering of the filing on the Commission website.

· PRE – Presentation data set; this provides information about how the tags and numbers were presented in the primary financial statements.

· CAL – Calculation data set; provides information to arithmetically relate tags in a filing.

2 Scope

The scope of the data in the financial statement data sets consists of:

· Numeric data and non-numeric "plain text" from the financial statements

· From Interactive Data exhibits (XBRL) to all forms other than 485BPOS, 497, SDR, SDR/A, SDR-A and SDR/W;

· Submitted from 4/15/2009 through the "Data Cutoff Date" inclusive (there is a file named 2009q1.zip on the Commission website that contains data sets with field headings only and no rows, merely so that all years prior to this year will consist of four zip files).

All data values are "as filed."

3 Organization

Note that this data set represents quarterly and annual uncorrected and "as filed" EDGAR document submissions containing multiple reporting periods (including amendments of prior submissions). Data in this submitted form may contain redundancies, inconsistencies, and discrepancies relative to other publication formats. There are eight data sets.

1. SUB is identifies all the EDGAR submissions in the data set, with each row having the unique (primary) key adsh, a 20 character EDGAR Accession Number with dashes in positions 11 and 14.

2. TAG is a data set of all tags used in the submissions, both standard and custom. These fields comprise a unique compound key:

1) tag – tag used by the filer

2) version – if a standard tag, the taxonomy of origin, otherwise equal to adsh.

3. DIM is a data set containing XBRL dimensional tags. The unique key of each row is a 16-byte hexadecimal value:

1) dimh - 0 representing no XBRL dimensions, otherwise the MD5 hash of the dimension tags. (The MD5 algorithm is a widely used hash function producing a 128-bit hash value, conventionally shown in human readable form as a 32-byte string.)

4. NUM is a data set of all numeric XBRL facts presented on the primary financial statements. These fields comprise a unique compound key:

1) adsh - EDGAR accession number

2) tag - tag used by the filer

3) version – if a standard tag, the taxonomy of origin, otherwise equal to adsh.

4) ddate - period end date

5) qtrs - duration in number of quarters

6) uom - unit of measure

7) dimh - 16-byte dimensional qualifier

8) iprx - a sequential integer used to distinguish otherwise identical facts

5. TXT is a data set that contains the plain (no HTML) text of each non-numeric XBRL fact. These fields comprise a unique compound key:

1) adsh - EDGAR accession number

2) tag – tag used by the filer

3) version – if a standard tag, the taxonomy of origin, otherwise equal to adsh

4) ddate - period end date

5) qtrs - duration in number of quarters

6) dimh - dimension hash value

7) iprx - a sequential integer used to distinguish otherwise identical facts

6. REN is a data set providing a summary of the filing as it would be rendered on the Commission website. These fields comprise a unique compound key:

1) adsh - EDGAR accession number

2) report - position in sequential display order

7. PRE is a data set that provides the text assigned by the filer to each line item in the primary financial statements, the order in which the line item appeared, and the tag assigned to it. These fields comprise a unique compound key:

1) adsh – EDGAR accession number

2) report – sequential number of report within the submission

3) line – sequential number of line within a report.

8. CAL is a data set that provides arithmetic relationships among the tags in a filing. These fields comprise a unique compound key:

1) adsh - EDGAR accession number

2) grp - sequential number of a group of relationships within the submission

3) arc - sequential number of relationship within the group of relationships

The relationship of the data sets is as shown in Figure 1. The Accession Number (adsh) found in the NUM data set can be used to retrieve information about the submission in SUB. Each row of data in NUM or TXT was tagged by the filer using a tag. Information about the tag used can be found in TAG. Each row of data in NUM or TXT appears on one or more lines of reports detailed in PRE.

Figure 1. Data relationships

Data set	Fields referencing other datasets	Referenced dataset	Referenced fields
REN	adsh	SUB	adsh
NUM	adsh	SUB	adsh
	tag, version	TAG	tag, version
	dimh	DIM	dimh
TXT	adsh	SUB	adsh
	tag, version	TAG	tag, version
	dimh	DIM	dimh
PRE	adsh	SUB	adsh
	tag, version	TAG	tag, version
	adsh, tag, version	NUM	adsh, tag, version
	adsh, report	REN	adsh, report
CAL	adsh	SUB	adsh
	ptag, pversion	TAG	tag, version
	ctag, cversion	TAG	tag, version

4 File Formats

Each of the four data sets is provided in a single encoding, as follows:

Tab Delimited Value (.txt): utf-8, tab-delimited, \n- terminated lines, with the first line containing the field names in lowercase.

5 Table Definitions

The fields in the figures below (figures 2 – 9) provide the following information: field name, description, source, data format, maximum field size, an indication of whether or not the field may be NULL (yes or no), and key.

The Source field has two possible values:

· EDGAR indicates that the source of the data is the filer's EDGAR submission header.

· XBRL indicates that the source of the data is the filer's EX-101 (XBRL) exhibits.

The Key field indicates whether the field is part of a unique index on the data. There are two possible values for this field:

· "*" – Indicates the field is part of the unique key for the row.

· Empty (nothing in field) – the field is not part of the unique compound key.

5.1 SUB (Submissions)

The submissions data set contains summary information about an entire EDGAR submission. Some fields were sourced directly from EDGAR submission information, while other fields of data were sourced from the Interactive Data exhibits of the submission. Note: EDGAR derived fields represent the most recent EDGAR assignment as of a given filing's submission date and do not necessarily represent the most current assignments.

Figure 2. Fields in the SUB data set

Field Name	Field Description	Source	Format	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	EDGAR	ALPHANUMERIC (nnnnnnnnnn-nn-nnnnnn)	20	No	*
cik	Central Index Key (CIK). Ten digit number assigned by the Commission to each registrant that submits filings.	EDGAR	NUMERIC	10	No
name	Name of registrant. This corresponds to the name of the legal entity as recorded in EDGAR as of the filing date.	EDGAR	ALPHANUMERIC	150	No
sic	Standard Industrial Classification (SIC). Four digit code assigned by the Commission as of the filing date, indicating the registrant's type of business.	EDGAR	NUMERIC	4	Yes
countryba	The ISO 3166-1 country of the registrant's business address.	EDGAR	ALPHANUMERIC	2	No
stprba	The state or province of the registrant's business address, if field countryba is US or CA.	EDGAR	ALPHANUMERIC	2	Yes
cityba	The city of the registrant's business address.	EDGAR	ALPHANUMERIC	30	No
zipba	The zip code of the registrant's business address.	EDGAR	ALPHANUMERIC	10	Yes
bas1	The first line of the street of the registrant's business address.	EDGAR	ALPHANUMERIC	40	Yes
bas2	The second line of the street of the registrant's business address.	EDGAR	ALPHANUMERIC	40	Yes
baph	The phone number of the registrant's business address.	EDGAR	ALPHANUMERIC	20	Yes
countryma	The ISO 3166-1 country of the registrant's mailing address.	EDGAR	ALPHANUMERIC	2	Yes
stprma	The state or province of the registrant's mailing address, if field countryma is US or CA.	EDGAR	ALPHANUMERIC	2	Yes
cityma	The city of the registrant's mailing address.	EDGAR	ALPHANUMERIC	30	Yes
zipma	The zip code of the registrant's mailing address.	EDGAR	ALPHANUMERIC	10	Yes
mas1	The first line of the street of the registrant's mailing address.	EDGAR	ALPHANUMERIC	40	Yes
mas2	The second line of the street of the registrant's mailing address.	EDGAR	ALPHANUMERIC	40	Yes
countryinc	The country of incorporation for the registrant.	EDGAR	ALPHANUMERIC, ISO 3166-1 ALPHA 2	2	No
stprinc	The state or province of incorporation for the registrant, if countryinc is US or CA, otherwise NULL.	EDGAR	ALPHANUMERIC	2	Yes
ein	Employee Identification Number, 9 digit identification number assigned by the Internal Revenue Service to business entities operating in the United States.	EDGAR	NUMERIC	10	Yes
former	Most recent former name of the registrant, if any.	EDGAR	ALPHANUMERIC	150	Yes
changed	Date of change from the former name, if any.	EDGAR	ALPHANUMERIC	8	Yes
afs	Filer status with the Commission at the time of submission: 1-LAF=Large Accelerated, 2-ACC=Accelerated, 3-SRA=Smaller Reporting Accelerated, 4-NON=Non-Accelerated, 5-SML=Smaller Reporting Filer, NULL=not assigned.	XBRL	ALPHANUMERIC	5	Yes
wksi	Well Known Seasoned Issuer (WKSI). An issuer that meets specific Commission requirements at some point during a 60-day period preceding the date the issuer satisfies its obligation to update its shelf registration statement.	XBRL	BOOLEAN (1 if true and 0 if false)	1	No
fye	Fiscal Year End Date, rounded to nearest month-end.	XBRL	ALPHANUMERIC (mmdd)	4	No
form	The submission type of the registrant's filing.	EDGAR	ALPHANUMERIC	10	No
period	Balance Sheet Date, rounded to nearest month-end.	XBRL	DATE (yymmdd)	8	No
fy	Fiscal Year Focus (as defined in EFM Ch. 6).	XBRL	YEAR (yyyy)	4	No
fp	Fiscal Period Focus (as defined in EFM Ch. 6) within Fiscal Year. The 10-Q for the 1st, 2nd and 3rd quarters would have a fiscal period focus of Q1, Q2 (or H1), and Q3 (or M9) respectively, and a 10-K would have a fiscal period focus of FY.	XBRL	ALPHANUMERIC, one of: FY, Q1, Q2, Q3, Q4, H1, H2, M9, T1, T2, T3, M8, CY (that is, Fiscal Year, 1^st-4^th Quarter, 1^st Half, 2^nd Half, 1^st through 3^rd Quarter inclusive, 1^st, 2^nd, 3^rd Trimester, 1^st through 2^nd trimester, and Calendar Year).	2	No
filed	The date of the registrant's filing with the Commission.	EDGAR	DATE (yymmdd)	8	No
accepted	The acceptance date and time of the registrant's filing with the Commission. Filings accepted after 5:30pm EST are considered filed on the following business day.	EDGAR	DATETIME (yyyy‑mm‑dd hh:mm:ss)	19	No
prevrpt	Previous Report –TRUE indicates that the submission information was subsequently amended prior to the end cutoff date of the data set.	EDGAR	BOOLEAN (1 if true and 0 if false)	1	No
detail	TRUE indicates that the XBRL submission contains quantitative disclosures within the footnotes and schedules at the required detail level (e.g., each amount).	XBRL	BOOLEAN (1 if true and 0 if false)	1	No
instance	The name of the submitted XBRL Instance Document (EX-101.INS) type data file. The name often begins with the company ticker symbol.	EDGAR	ALPHANUMERIC (example: abcd‑yyyymmdd.xml)	32	No
nciks	Number of Central Index Keys (CIK) of registrants (i.e., business units) included in the consolidating entity's submitted filing.	EDGAR	NUMERIC	4	No
aciks	Additional CIKs of co-registrants included in a consolidating entity's EDGAR submission, separated by spaces. If there are no other co-registrants (i.e., nciks = 1), the value of aciks is NULL. For a very small number of filers, the list of co-registrants is too long to fit in the field. Where this is the case, PARTIAL will appear at the end of the list indicating that not all co-registrants' CIKs are included in the field; users should refer to the complete submission file for all CIK information.	EDGAR	ALPHANUMERIC (space delimited)	120	Yes
pubfloatusd	Public float, in USD, if provided in this submission.	XBRL	NUMERIC	8	Yes
floatdate	Date on which the public float was measured by the filer.	XBRL	DATE (yyyymmdd)	8	Yes
floataxis	If the public float value was computed by summing across several tagged values, this indicates the nature of the summation.	XBRL	ALPHANUMERIC	255	Yes
floatmems	If the public float was computed, the number of terms in the summation.	XBRL	NUMERIC	1	Yes

Note: To access the complete submission files for a given filing, please see the Commission EDGAR website. The Commission website folder https://www.sec.gov/Archives/edgar/data/{cik}/{accession}/ will always contain all the data sets for a given submission. To assemble the folder address to any filing referenced in the SUB data set, simply substitute {cik} with the cik field and replace {accession} with the adsh field (after removing the dash character). The following sample SQL Query provides an example of how to generate a list of addresses for filings contained in the SUB data set:

· select name,form,period, 'https://www.sec.gov/Archives/edgar/data/' + ltrim(str(cik,10))+'/' + replace(adsh,'-','')+'/'+instance as url from sub order by period desc, name

5.2 TAG (Tags)

The TAG data set contains all standard taxonomy tags, not just those appearing in submissions to date, and also includes all custom taxonomy tags defined in the submissions. The source is the "as filed" XBRL filer submissions. The standard tags are derived from taxonomies in https://www.sec.gov/info/edgar/edgartaxonomies.shtml as of the date of the original submission.

Figure 3. Fields in the TAG data set

Field Name	Field Description	Field Type	Max Size	May be NULL	Key
tag	The unique identifier (name) for a tag in a specific taxonomy release.	ALPHANUMERIC	256	No	*
version	For a standard tag, an identifier for the taxonomy; otherwise the accession number where the tag was defined.	ALPHANUMERIC	20	No	*
custom	1 if tag is custom (version=adsh), 0 if it is standard. Note: This flag is technically redundant with the version and adsh fields.	BOOLEAN (1 if true and 0 if false)	1	No
abstract	1 if the tag is not used to represent a numeric fact.	BOOLEAN (1 if true and 0 if false)	1	No
datatype	If abstract=1, then NULL, otherwise the data type (e.g., monetary) for the tag.	ALPHANUMERIC	20	Yes
iord	If abstract=1, then NULL; otherwise, "I" if the value is a point in time, or "D" if the value is a duration.	ALPHANUMERIC	1	No
crdr	If datatype = monetary, then the tag's natural accounting balance from the perspective of the balance sheet or income statement (debit or credit); if not defined, then NULL.	ALPHANUMERIC ("C" or "D")	1	Yes
tlabel	If a standard tag, then the label text provided by the taxonomy, otherwise the text provided by the filer. A tag which had neither would have a NULL value here.	ALPHANUMERIC	512	Yes
doc	The detailed definition for the tag. If a standard tag, then the text provided by the taxonomy, otherwise the text assigned by the filer. Some tags have neither, in which case this field is NULL.	ALPHANUMERIC		Yes

5.3 DIM (Dimensions)

The DIM set contains all of the combinations of XBRL axis and member used to tag any submission. The source is the "as filed" XBRL filer submissions.

Figure 4. Fields in the DIM data set

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
dimh	MD5 hash of the segments field text. Although MD5 is unsuitable for cryptographic use, it is used here merely to limit the size of the primary key.	HEXADECIMAL	32	No	*
segments	Concatenation of tag names representing the axis and members appearing in the XBRL segments. Tag names have their first characters "Statement", last 4 characters "Axis", and last 6 characters "Member" or "Domain" truncated where they appear. Namespaces and prefixes are ignored because EDGAR validation guarantees that the local-names are unique with a submission. Each dimension is represented as the pair "{axis}={member};" and the axes concatenated in lexical order. Example: "LegalEntity=Xyz;Scenario=Restated;" represents the XBRL segment with dimension LegalEntityAxis and member XyzMember, dimension StatementScenarioAxis and member RestatedMember.	ALPHANUMERIC	1024	No
segt	TRUE if the segments field would have been longer than 1024 characters had it not been truncated, else FALSE.	BOOLEAN	1	No

5.4 NUM (Numbers)

The NUM data set contains numeric data, one row per data point in the financial statements. The source for the table is the "as filed" XBRL filer submissions.

Figure 5. Fields in the NUM data set

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
tag	The unique identifier (name) for a tag in a specific taxonomy release.	ALPHANUMERIC	256	No	*
version	For a standard tag, an identifier for the taxonomy; otherwise the accession number where the tag was defined.	ALPHANUMERIC	20	No	*
ddate	The end date for the data value, rounded to the nearest month end.	DATE (yyyymmdd)	8	No	*
qtrs	The count of the number of quarters represented by the data value, rounded to the nearest whole number. "0" indicates it is a point-in-time value.	NUMERIC	8	No	*
uom	The unit of measure for the value.	ALPHANUMERIC	20	No	*
dimh	The 32-byte hexadecimal key for the dimensional information in the DIM data set.	ALPHANUMERIC	32	No	*
iprx	A positive integer to distinguish different reported facts that otherwise would have the same primary key. For most purposes, data with iprx greater than 1 are not needed. The priority for the fact based on higher precision, closeness of the end date to a month end, and closeness of the duration to a multiple of three months. See fields dcml, durp and datp below.	NUMERIC	2	No	*
value	The value. This is not scaled, it is as found in the Interactive Data file, but is rounded to four digits to the right of the decimal point.	NUMERIC	16	Yes
footnote	The plain text of any superscripted footnotes on the value, if any, as shown on the statement page, truncated to 512 characters.	ALPHANUMERIC	512	Yes
footlen	Number of bytes in the plain text of the footnote prior to truncation; zero if no footnote.	NUMERIC	4	No
dimn	Small integer representing the number of dimensions. Note that this value is a function of the dimension segments.	NUMERIC	1	No
coreg	If specified, indicates a specific co-registrant, the parent company, or other entity (e.g., guarantor). NULL indicates the consolidated entity. Note that this value is a function of the dimension segments.	ALPHANUMERIC	256	Yes
durp	The difference between the reported fact duration and the quarter duration (qtrs), expressed as a fraction of 1. For example, a fact with duration of 120 days rounded to a 91-day quarter has a durp value of 29/91 = +0.3187.	REAL	4	No
datp	The date proximity in number of days between end date reported and month-end rounded date.	REAL	4	No
dcml	The value of the fact "decimals" attribute, with INF represented by 32767.	NUMERIC	2	No

5.5 TXT (Plain Text)

The TXT data set contains non-numeric data, one row per data point in the financial statements. The source for the table is the "as filed" XBRL filer submissions.

Figure 6. Fields in the TXT data set

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
tag	The unique identifier (name) for a tag in a specific taxonomy release.	ALPHANUMERIC	256	No	*
version	For a standard tag, an identifier for the taxonomy; otherwise the accession number where the tag was defined. For example, "invest/2013" indicates that the tag is defined in the 2013 INVEST taxonomy.	ALPHANUMERIC	20	No	*
ddate	The end date for the data value, rounded to the nearest month end.	DATE (yyyymmdd)	8	No	*
qtrs	The count of the number of quarters represented by the data value, rounded to the nearest whole number. A point in time value is represented by 0.	NUMERIC	8	No	*
iprx	A positive integer to distinguish different reported facts that otherwise would have the same primary key. For most purposes, data with iprx greater than 1 are not needed. The priority for the fact based on higher precision, closeness of the end date to a month end, and closeness of the duration to a multiple of three months. See fields dcml, durp and datp below.	NUMERIC	2	No	*
lang	The ISO language code of the fact content.	ALPHANUMERIC	5	No
dcml	The value of the fact "xml:lang" attribute, en-US represented by 32767, other "en" dialects having lower values, and other languages lower still.	NUMERIC	2	No
durp	The difference between the reported fact duration and the quarter duration (qtrs), expressed as a fraction of 1. For example, a fact with duration of 120 days rounded to a 91-day quarter has a durp value of 29/91 = +0.3187.	REAL	4	No
datp	The date proximity in number of days between end date reported and month-end rounded date.	REAL	4	No
dimh	The 32-byte hexadecimal key for the dimensional information in the DIM data set.	ALPHANUMERIC	32	No	*
dimn	Small integer representing the number of dimensions, useful for sorting. Note that this value is function of the dimension segments.	NUMERIC(1,0)	1	Yes
coreg	If specified, indicates a specific co-registrant, the parent company, or other entity (e.g., guarantor). NULL indicates the consolidated entity. Note that this value is a function of the dimension segments.	NUMERIC	256	Yes
escaped	Flag indicating whether the value has had tags removed.	BOOLEAN	1	No
srclen	Number of bytes in the original, unprocessed value. Zero indicates a NULL value.	NUMERIC(4,0)	4	No
txtlen	The original length of the whitespace normalized value, which may have been greater than 8192.	NUMERIC(4,0)	4	Yes
footnote	The plain text of any superscripted footnotes on the value, as shown on the page, truncated to 512 characters, or if there is no footnote, then this field will be blank.	ALPHANUMERIC	512	Yes
footlen	Number of bytes in the plain text of the footnote prior to truncation.	NUMERIC(4,0)	4	Yes
context	The value of the contextRef attribute in the source XBRL document, which can be used to recover the original HTML tagging if desired.	ALPHANUMERIC(255)	255	No
value	The value, with all whitespace normalized, that is, all sequences of line feeds, carriage returns, tabs, non-breaking spaces, and spaces having been collapsed to a single space, and no leading or trailing spaces. Escaped XML that appears in EDGAR "Text Block" tags is processed to remove all mark-up (comments, processing instructions, elements, attributes). The value is truncated to a maximum number of bytes. The resulting text is not intended for end user display but only for text analysis applications.	ALPHANUMERIC		Yes

5.6 REN (Rendering)

The REN data set summarizes for each filing the data provided by filers about each presentation group as defined in EDGAR Filer manual volume II section 6.24. The source for the table is the "as filed" XBRL filer submissions as processed by the renderer.

Note that in rare cases the number of reports may differ depending on the version of the EDGAR Renderer used. The numbering provided in this table is the numbering resulting as processed by the most current version of the EDGAR Renderer as of the date of data set publication; for example, if the data for the 1^st quarter of 2010 is not published on the Commission web site until 2016, the rendering will be the EDGAR Renderer version current in 2016.

Figure 7. Fields in the REN data set

Field Name	Field Description	Field Type	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
report	Represents the report grouping. The numeric value refers to the "R file" as computed by the renderer and posted on the EDGAR website. Note that in some situations the numbers skip.	NUMERIC	6	No	*
rfile	The type of interactive data file rendered on the EDGAR website, H = .htm file, X = .xml file.	ALPHANUMERIC	1	No
menucat	If available, one of the menu categories as computed by the renderer: C=Cover, S=Statements, N=Notes, P=Policies, T=Tables, D=Details, O=Other, and U=Uncategorized.	ALPHANUMERIC	2	Yes
shortname	The portion of the long name used in the renderer menu.	ALPHANUMERIC	255	No
longname	The space-normalized text of the XBRL link "definition" element content.	ALPHANUMERIC	255	No
roleuri	The XBRL "roleuri" of the role.	ALPHANUMERIC	255	No
parentroleuri	The XBRL roleuri of a role for which this role has a matching shortname prefix and a higher level menu category, as computed by the renderer.	ALPHANUMERIC	255	Yes
parentreport	The value of the report field for the role where roleuri equals this parentroleuri.	NUMERIC	6	Yes
ultparentrpt	The highest ancestor report reachable by following parentreport relationships. A note (menucat = N) is its own ultimate parent.	NUMERIC	6	Yes

5.7 PRE (Presentation)

The PRE data set contains one row for each line of the financial statements tagged by the filer. The source for the data set is the "as filed" XBRL filer submissions. Note that there may be more than one row per entry in NUM because the same tag can appear in more than one statement (the tag NetIncome, for example can appear in both the Income Statement and Cash Flows in a single financial statement, and the tag Cash may appear in both the Balance Sheet and Cash Flows).

Figure 8. Fields in the PRE data set

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
report	Represents the report grouping. The numeric value refers to the "R file" as computed by the renderer and posted on the EDGAR website. Note that in some situations the numbers skip.	NUMERIC	6	No	*
line	Represents the tag's presentation line order for a given report. Together with the statement and report field, presentation location, order and grouping can be derived.	NUMERIC	6	No	*
stmt	The financial statement location to which the value of the "report" field pertains.	ALPHANUMERIC (CP = Cover Page, BS = Balance Sheet, IS = Income Statement, CF = Cash Flow, EQ = Equity, CI = Comprehensive Income, UN = Unclassifiable Statement).	2	No
inpth	1 indicates that the value was presented "parenthetically" instead of in fields within the financial statements. For example: Receivables (net of allowance for bad debts of $200 in 2012) $700.	BOOLEAN	1	No
tag	The tag chosen by the filer for this line item.	ALPHANUMERIC	256	No
version	The taxonomy identifier if the tag is a standard tag, otherwise adsh.	ALPHANUMERIC	20	No
prole	The XBRL link "role" of the preferred label, using only the portion of the role URI after the last "/".	ALPHANUMERIC	50	No
plabel	The text presented on the line item, also known as a "preferred" label.	ALPHANUMERIC	512	No
negating	Flag to indicate whether the prole is treated as negating by the renderer.	BOOLEAN	1	No

5.8 CAL (Calculations)

The CAL data set contains one row for each calculation relationship ("arc"). Note that XBRL allows a parent element to have more than one distinct set of arcs for a given parent element, thus the rationale for distinct fields for the group and the arc. The source for the table is the "as filed" XBRL filer submissions.

Figure 9. Fields in the CAL data set

Field Name	Field Description	Field Type (format)	Max Size	May be NULL	Key
adsh	Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.	ALPHANUMERIC	20	No	*
grp	Sequential number for grouping arcs in a submission.	NUMERIC(1,0)	1	No	*
arc	Sequential number for arcs within a group in a submission.	NUMERIC(1,0)	1	No	*
negative	Indicates a weight of -1 (TRUE if the arc is negative), but typically +1 (FALSE).	BOOLEAN	1	No
ptag	The tag for the parent of the arc	ALPHANUMERIC	256	No
pversion	The version of the tag for the parent of the arc	ALPHANUMERIC	20	No
ctag	The tag for the child of the arc	ALPHANUMERIC	256	No
cversion	The version of the tag for the child of the arc	ALPHANUMERIC	20	No