{"id":1630,"date":"2020-04-02T18:00:53","date_gmt":"2020-04-02T18:00:53","guid":{"rendered":"https:\/\/prathamconsult.com\/us\/?page_id=1630"},"modified":"2023-04-24T07:22:04","modified_gmt":"2023-04-24T07:22:04","slug":"faq","status":"publish","type":"page","link":"https:\/\/prathamconsult.com\/us\/faq\/","title":{"rendered":"FAQ"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"1630\" class=\"elementor elementor-1630\">\n\t\t\t\t\t\t<div class=\"elementor-inner\">\n\t\t\t\t<div class=\"elementor-section-wrap\">\n\t\t\t\t\t\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-6efa445e elementor-section-height-min-height elementor-section-content-middle elementor-section-stretched elementor-section-boxed elementor-section-height-default elementor-section-items-middle\" data-id=\"6efa445e\" data-element_type=\"section\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;stretch_section&quot;:&quot;section-stretched&quot;}\">\n\t\t\t\t\t\t\t<div class=\"elementor-background-overlay\"><\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t\t\t<div class=\"elementor-row\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-2c0f99c4\" data-id=\"2c0f99c4\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-column-wrap elementor-element-populated\">\n\t\t\t\t\t\t\t<div class=\"elementor-widget-wrap\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-26eec28a elementor-invisible elementor-widget elementor-widget-heading\" data-id=\"26eec28a\" data-element_type=\"widget\" data-settings=\"{&quot;_animation&quot;:&quot;fadeInDown&quot;}\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">FAQ<\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-c79cf20 elementor-section-content-middle elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"c79cf20\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-no\">\n\t\t\t\t\t\t\t<div class=\"elementor-row\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-c9d7473\" data-id=\"c9d7473\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-column-wrap elementor-element-populated\">\n\t\t\t\t\t\t\t<div class=\"elementor-widget-wrap\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-55c9a6b elementor-widget elementor-widget-text-editor\" data-id=\"55c9a6b\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t<div class=\"elementor-text-editor elementor-clearfix\">\n\t\t\t\t<p><span style=\"color: #000000;\"><strong><u>UNITED STATES<\/u><\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>URL: 1 <\/strong><a style=\"color: #000000;\" href=\"https:\/\/xbrl.us\/qa-sec-ixbrl\/\">https:\/\/xbrl.us\/qa-sec-ixbrl\/<\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q&amp;A \u2013 Inline XBRL<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><em>Responses to these questions reflect the informal views of one or more members of the staff of the U.S. Securities and Exchange Commission participating in a discussion and do not constitute an official statement of the views of the Commission or of the staff of the Commission and should not be relied upon as authoritative.<\/em><\/span><\/p><p><span style=\"color: #000000;\"><strong>For issuers that early adopt Inline XBRL on 10-Qs and 10-Ks and are not yet part of the Inline XBRL phase-in period, if they file a registration statement before their mandated phase-in period, will their registration statements, or any other forms, require Inline XBRL format by virtue of the fact they previously have filed Inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Filers that early adopt Inline XBRL are allowed to go back and forth between Inline and conventional XBRL, irrespective of the form type, until they are required to use Inline XBRL.<\/span><\/p><p><span style=\"color: #000000;\"><strong>After an issuer conducts their first required Inline XBRL filing per the phase-in, is the issuer required to file Inline XBRL on subsequent filings regardless of form type, if the filing includes financial statements that are for a fiscal period after their Inline XBRL phase-in fiscal period end date? For example, a Large Accelerated Filer using US-GAAP with a 12\/31 YE submits their 10-Q with Inline XBRL for the Quarter Ended 6-30-2019 on 7-30-2019 to the EDGAR system. Are the subsequent XBRL filings regardless of form type required to be submitted with Inline XBRL as long as the financials in said filings are for a fiscal period ending on or after 6-15-2019? Additionally, in this example, if the filing includes two sets of financials, one set with fiscal period end date prior to 6-15-2019, and one set with fiscal period end date on or after 6-15-2019, is the issuer to submit a single Inline XBRL instance for the filing?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Yes to all of these questions. Under the compliance language in the adopting release (33-10514 (6\/28\/2018)) discussion text associated with note 151 and the text of Regulation S-T Rule 405(~(1)(i), once a large accelerated filer that reports in US GAAP on 10-Q is required to file such a 10-Q using Inline XBRL, all subsequent filings that contain any financial statement for which an Interactive Data File is required for a period that ends on or after 6\/15\/19 must be filed in Inline XBRL. Financial statements for which an Interactive Data File is required for all periods included in the filing would need to be in Inline XBRL in the same Inline XBRL instance.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Can issuers immediately stop posting the XBRL data files on their web site, regardless of their Inline XBRL phase-in date?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Yes. The SEC states in the adopting release that the amendments eliminating the website posting requirement are effective September 17, 2018. As a result, as of that date, companies do NOT have to post their XBRL files on their web site.<\/span><\/p><p><span style=\"color: #000000;\"><strong>For a company that has never filed financial statements in conventional or Inline XBRL and is filing them in XBRL for the first time using Inline XBRL, is it able to take advantage of the 30-day grace period on its XBRL submission as stated in the original (2009) final rule?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Yes, under Regulation S-T Rule 405(a)(3)(i)(B), it can file the HTML-only version first, and then within the 30-day grace period amend that filing to add the Inline XBRL document which will contain the combined HTML and XBRL. Assuming the financial statements are unchanged and the sole purpose of the amendment is to add the Inline XBRL document, in the case of an amendment to a periodic report, the filer should include the cover page, an explanatory note, the combined HTML\/XBRL financials, an exhibit index and exhibit 101.<\/span><\/p><p>\u00a0<\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>URL: 2 <\/strong><a style=\"color: #000000;\" href=\"https:\/\/xbrl.us\/home\/filers\/sec-reporting\/best-practice\/qa-sec-fast-act\/\">https:\/\/xbrl.us\/home\/filers\/sec-reporting\/best-practice\/qa-sec-fast-act\/<\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q&amp;A \u2013 SEC Cover Page Tagging<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><em>This Q&amp;A is intended as general guidance and should not be relied upon as authoritative. Filers are encouraged to consult with their own legal and\/or with the SEC directly.<\/em><\/span><\/p><p><span style=\"color: #000000;\"><strong>Early Adoption\/Timing<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Are early adopters of Inline XBRL (public companies that have already begun submitting financials using Inline XBRL, but that are not yet subject to Inline XBRL compliance because the compliance date for their category of company, e.g., non-accelerated filer, has not yet occurred), required to continue tagging their cover pages?\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\">No, they can start and stop up until their filing compliance date. Filers do not need to begin tagging the cover page of their 10-Ks, 8-Ks, 10-Qs, 20-Fs and 40-Fs, until they become subject to Inline XBRL per their Inline XBRL filing date (Large Accelerated Filers (US-GAAP) \u2013 Fiscal periods ending after June 15, 2019, accelerated Filers (US-GAAP) \u2013 Fiscal periods ending after June 15, 2020, all Others \u2013 Fiscal periods ending after June 15, 2021)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Can a public company elect to tag the cover page on their 8-K using Inline XBRL before they file the first 10-Q? Or is it required to file a 10-Q using Inline XBRL first, before they can publish a form 8-K using Inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Yes, filers can early adopt and tag a Form 8-K.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>If a calendar year-end filer, files an 8-K, after June 15, but before they file their second quarter 10-Q, is that 8-K not required to have the cover page data tagged with Inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Yes, that is correct. This filer would not need to tag their cover page until they have filed their first 10-Q using Inline XBRL per their compliance date.<\/span><\/p><p><span style=\"color: #000000;\"><strong>What Should Be Tagged?<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Do all Form 8-K cover pages have to be tagged, regardless of whether they contain financial data? Is it required to tag cover pages of Form 8-Ks of earnings releases?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Any Form 8-K that is submitted by a reporting entity that is subject to Inline XBRL, must have the cover page tagged, once that company\u2019s compliance date occurs.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Does the rule require companies to tag cover pages for ALL 8-K, 10-K, and 10-Q filings from operating companies? For all 20-F and 40-F cover pages that are annual reports? Or just those with financials in them?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Cover page tagging applies to all Forms 10-K, 8-K, 10-Q, 20-F and 40-F (for the last two forms, only if they are being used for annual reports and not registration statements). \u00a0The only exception is for filers that are not subject to Inline XBRL (i.e. ABS filers). Specifically, once a filer becomes subject to submitting any of its filings in Inline XBRL, it must begin tagging the cover page of its 10-Ks, 8-Ks, 10-Qs, 20-Fs and 40-Fs.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Is tagging of the 6-K cover page required?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">No, it is not required.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Clarification on Exhibits<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>What is Exhibit 101?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">The exhibit required to be filed with your Inline XBRL submission.<\/span><\/p><p><span style=\"color: #000000;\"><strong>What is Exhibit 104?\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Exhibit 104 is the document cover page tagged in Inline XBRL. It describes the required content in the Inline XBRL document. Exhibit 104 must be included as part of Exhibit 101.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Do I need to reference Exhibit 104 anywhere in my EDGAR submission?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Yes, if the filing document contains an exhibit index. Forms that do not include an exhibit index do not need to reference Exhibit 104.<\/span><\/p><p><span style=\"color: #000000;\">For example, Form 10-Q requires the inclusion of \u201cItem 6. Exhibits\u201d. Some Form 8-Ks require the inclusion of an exhibit index and some Form 8-Ks do not require the inclusion of an exhibit index.<\/span><\/p><p><span style=\"color: #000000;\"><strong>How do I reference Exhibit 104 in my submission?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Exhibit 104 should be included in the exhibit index, if the filing document includes an exhibit index. An example of this is shown below.<\/span><\/p><p><span style=\"color: #000000;\"><strong>IMAGE FORM DOES NOT SUPPORTED HERE.<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>What if I\u2019ve already submitted my Inline XBRL document and it does not include the Exhibit 104 reference in the exhibit index?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Just add the Exhibit 104 reference in your next Inline XBRL filing.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Please provide an example of a Form 8-K with cover page tagged using Inline XBRL.<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>IMAGE FORM DOES NOT SUPPORTED HERE.<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Example Inline XBRL documents:<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/ix?doc=\/Archives\/edgar\/data\/16875\/000095014219001585\/eh1900909_8k.htm\">Example 1<\/a><\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/ix?doc=\/Archives\/edgar\/data\/4904\/000000490419000037\/a2q20198-kpressrelease.htm\">Example 2<\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>DEI Taxonomy<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Can you provide a link to the DEI 2019 Taxonomy?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Link to all SEC US GAAP Taxonomies:\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/info\/edgar\/edgartaxonomies.shtml#USGAAP2019\">https:\/\/www.sec.gov\/info\/edgar\/edgartaxonomies.shtml#USGAAP2019<\/a><\/span><\/p><p><span style=\"color: #000000;\">Link to the DEI 2019 Taxonomy:\u00a0<a style=\"color: #000000;\" href=\"https:\/\/xbrl.sec.gov\/dei\/2019\/dei-2019-01-31.xsd\">https:\/\/xbrl.sec.gov\/dei\/2019\/dei-2019-01-31.xsd<\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Can new elements in the DEI Taxonomy be viewed in the FASB \u201cyeti\u201d viewer?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Yes.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Can you comply by creating custom tags rather than using the new elements in the 2019 DEI Taxonomy?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">No, you are required to use the new tags.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>Can we use the 2019 DEI Taxonomy with the 2018 US GAAP Taxonomy?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Yes, you can use these two taxonomies together.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Other Topics<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>For \u201crequired visible facts\u201d that are listed as \u201cdei\u201d (not as \u201ccover\u201d), are they also required to be visible?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Most, but not all DEI facts defined in EFM 5.2.5.14, are required to be visible (note that CIK and Amendment Flag, for example, should be hidden).<\/span><\/p><p><span style=\"color: #000000;\"><strong>In the SEC\u2019s Inline XBRL viewer, there is a drop down menu \u201cMore Filters\u201d which includes an option for \u201cSource documents\u201d. Under what situation would a filing have more than one source document?\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\">If there is more than one document in a single filing that contains XBRL, there will be multiple sources.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>If a company has multiple debts, do we use one standard tag and then dimensionalize?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">If multiple securities are included in the securities table, they should be dimensionalized.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>What is recommended if the registrant name on the cover of a 10-Q or 10-K is different from the registrant name associated with the CIK?\u00a0 Do you use the registrant name associated with the CIK?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">You can either use the registrant name associated with the CIK, or you could use a hidden fact and include a reference to the hidden fact in the document.\u00a0<\/span><\/p><p>\u00a0<\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>URL-3:<\/strong><a style=\"color: #000000;\" href=\"https:\/\/xbrl.us\/qa-sec-inline-xbrl-funds\/\">https:\/\/xbrl.us\/qa-sec-inline-xbrl-funds\/<\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q&amp;A: Funds and Inline XBRL<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><em>Responses to these questions were developed through an informal discussion with staff from the U.S. Securities and Exchange Commission.<\/em><\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0What is the Commission\u2019s position on data points in bar charts? We assume that would require hidden facts such as DEI information. Today the risk\/return summary charts must be tagged in table format in the detail view \u2013 how would the individual facts in the bar chart be represented using inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0Tags in charts should be put in the hidden section. Validation has or will be modified so it will not give you a warning. The data does not have to be tied to an image, but it certainly can be.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question: Could the Commission create one or more sample Inline XBRL documents for funds as they did with operating companies? It would be helpful to see a sample registration statement amendment (485BPOS) and a sample (or samples) of a supplement (497).<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0In the most recently published test suite(<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/osdinteractivedatatestsuite\">https:\/\/www.sec.gov\/structureddata\/osdinteractivedatatestsuite<\/a>), i23007gd (test case), there is a specimen filing, an anonymized N1A filing summary. This shows what must and what doesn\u2019t have to be tagged.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0Are there plans for the SEC to release an update of the technical specification document for Risk Return based on inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0It is not clear that this is needed. Much that is in the current EDGAR Filer Manual (<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/info\/edgar\/edmanuals.htm\">https:\/\/www.sec.gov\/info\/edgar\/edmanuals.htm<\/a>) and Preparer\u2019s Guide is still applicable, under EDGAR Filer manual section 6.13, Inline XBRL only relieves the filer of the need to approximate the original filing layout; nothing else changes.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0For the 485BPOS, funds sometimes pull content from multiple sources and in multiple formats, e.g., Quark, Excel, etc. which takes time to aggregate into a single format. Are there any suggestions on how best to handle this?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0The goal is to move to HTML format that allows you to aggregate to a common file. How you aggregate HTML for EDGAR today will be essentially the same.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0Will there be any rendering options like the SEC previewer? How will a filer be able to view the XBRL prior to filing? If there is a rendering option, will the rendering agent create bar charts?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0Every product has its own previewer, or vendors can also use the SEC EDGAR Renderer through the Arelle GUI. Bar charts are viewable in Arelle also.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0Will a new Risk\/Return Taxonomy be released for the transition to Inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0There\u2019s no need to create a new taxonomy for the move to Inline XBRL. If items 2, 3, or 4 in N-1A change, the taxonomy will be modified.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Question: Does the Commission envision any changes in the applicability of the calculation linkbase for Risk\/Return or will it continue to be a \u201cnull\u201d linkbase for the majority of mutual fund filings?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0The Commission sees no reason to change the way the calculation linkbase is used. But XBRL International now has a proposal out for Calc Linkbase 2 which is meant to address issues that arise in financial statements. The Calc linkbase associated with the risk\/return has no such issues. You can import the standard one into your filing.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0Does the SEC anticipate that a test filing system for inline risk\/return will be made available?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0The EDGAR test filing system is the test filing system. This is already available. When EDGAR was updated on March 11, 2019, it allowed for Risk\/Return Summary Inline filings in the test system.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0Will the Table TextBlock elements and associated Embedded Text used to render the summary section tables be eliminated? Will they be maintained for a period of time to accommodate XBRL rendering which may not be inline XBRL enabled?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0This is up to the filer. If the filer wants to include these as hidden items, they can. However, with inline XBRL, the need for this goes away, but they are not necessary once you\u2019re using inline XBRL.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0Are there any developments on the merge functionality process documented at the end of the preparers guide?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0There are no developments on the merge functionality process. The merge process is based on only looking at the data, not the presentation.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0With respect to linkbases, will these be the same going forward?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer: The default presentation linkbase can be used.\u00a0<\/span><\/p><p><span style=\"color: #000000;\"><strong>Question:\u00a0How does the SEC intend to support redlining (track changes) in the inline tagged html?\u00a0 There is a conflict between the inline code and the redline coding that would potentially cause an error or issue in the filing. Does the SEC have thoughts on how this could be resolved?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Answer:\u00a0The Commission is aware of this issue and there will be a method available in EDGAR prior to the compliance date for Mutual Funds.<\/span><\/p><p>\u00a0<\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>URL-4:<\/strong><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/osd-inline-xbrl.html\"><strong>https:\/\/www.sec.gov\/structureddata\/osd-inline-xbrl.html<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Inline XBRL<\/strong><\/span><\/p><p><span style=\"color: #000000;\">On June 28, 2018, the Commission adopted amendments requiring the use, on a phased in basis, of Inline XBRL for operating company financial statement information and fund risk\/return summary information. See\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/rules\/final\/2018\/33-10514.pdf\">Release No. 33-10514<\/a>\u00a0for details.<\/span><\/p><p><span style=\"color: #000000;\"><strong>What is Inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Inline XBRL is a format that allows filers to embed XBRL data directly into a HyperText Markup Language (HTML) document so that filers need only prepare one Inline XBRL document rather than generate an HTML document of their financial statement information or risk\/return summary information and then tag a copy of the data to create a separate XBRL exhibit.<\/span><\/p><p><span style=\"color: #000000;\">For data users, Inline XBRL provides an easier way to view, access, and explore the contextual information of the underlying data. For example, users can hover over values in the filing to find more information about the data, such as citations and hyperlinks to the relevant accounting guidance, narrative definitions for the values, and reporting period information associated with each value.<\/span><\/p><p><span style=\"color: #000000;\"><strong>How are Inline XBRL filings viewed?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">Viewing Inline XBRL filings is simple and does not require any specialized software because the Commission has incorporated an Inline XBRL Viewer into the Commission\u2019s Electronic Data Gathering, Analysis, and Retrieval (EDGAR) system. Anyone using a recent standard internet browser can view an Inline XBRL filing on EDGAR. (Recent standard internet browsers are ones that fully support HTML 5 and JavaScript, such as Chrome 68 and later, Firefox 60 and later, Safari IOS 11 and later, Microsoft Edge Windows 10, and Internet Explorer 11.)<\/span><\/p><p><span style=\"color: #000000;\">The short video below describes some of the features and capabilities of the open source Inline XBRL Viewer.<\/span><\/p><p><span style=\"color: #000000;\"><strong>VIDEO FORMAT DOESN\u2019T SUPPORTED HERE.<\/strong><\/span><\/p><p><span style=\"color: #000000;\">You can access a transcript of the video\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/files\/InlineXBRL_Transcript.pdf\">here<\/a>.<\/span><\/p><p><span style=\"color: #000000;\"><strong>When must filers begin filing using Inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><u>Operating Company Financial Statement Information<\/u><\/span><\/p><p><span style=\"color: #000000;\">U.S. GAAP filers have a three-year phase-in to comply with the Inline XBRL requirements as follows, beginning with fiscal periods ending on or after:<\/span><\/p><ul><li><span style=\"color: #000000;\">June 15, 2019 for large accelerated filers<\/span><\/li><li><span style=\"color: #000000;\">June 15, 2020 for accelerated filers<\/span><\/li><li><span style=\"color: #000000;\">June 15, 2021 for all other filers<\/span><\/li><\/ul><p><span style=\"color: #000000;\">IFRS filers will be required to comply with Inline XBRL beginning with fiscal periods ending on or after June 15, 2021.<\/span><\/p><p><span style=\"color: #000000;\">Domestic form filers, however, will not become subject to the requirement until their first Form 10-Q filed for a fiscal period ending on or after the applicable compliance date, as opposed to the first filing for a fiscal period ending on or after that date.<\/span><\/p><p><span style=\"color: #000000;\"><strong><u>Fund Risk\/Return Summary Information<\/u><\/strong><\/span><\/p><p><span style=\"color: #000000;\">Funds have a two-year phase-in to comply with the Inline XBRL requirements as follows, beginning with any initial registration statement (or post-effective amendment that is an annual update to an effective registration statement) that becomes effective on or after:<\/span><\/p><ul><li><span style=\"color: #000000;\">September 17, 2020 for large fund groups (with assets of $1 billion or more as of the end of the most recent fiscal year)<\/span><\/li><li><span style=\"color: #000000;\">September 17, 2021 for small fund groups (with assets of less than $1 billion as of the end of the most recent fiscal year)<\/span><\/li><\/ul><p><span style=\"color: #000000;\"><strong>Can all forms subject to the Inline XBRL requirements be voluntarily filed using Inline XBRL in the EDGAR system now?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">The EDGAR system was modified on March 11, 2019 to accept in Inline XBRL all forms subject to the Inline XBRL requirements.<\/span><\/p><p><span style=\"color: #000000;\">Operating companies that are not currently subject to the Inline XBRL requirements may voluntarily file in Inline XBRL the forms that will be subject to the Inline XBRL requirements.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Where can I find filings submitted using Inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">The most recent 200 Inline XBRL filings are displayed\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/Archives\/edgar\/xbrl-inline.rss.xml\">here<\/a>\u00a0for ease of reference.<\/span><\/p><p><span style=\"color: #000000;\">Alternatively, when searching the documents of a particular company, any filing submitted using Inline XBRL will display an \u201ciXBRL\u201d indicator as below:<\/span><\/p><p><span style=\"color: #000000;\"><strong>Is the Inline Viewer software source code available for download?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">The Inline Viewer software is freely\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/edgarvalandrender\">available<\/a>\u00a0to the public in an effort to facilitate the creation of cost effective Inline XBRL viewers and analytical products.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Where can I find the technical requirements related to filing using Inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">The\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/info\/edgar\/edmanuals.htm\">EDGAR Filer Manual<\/a>\u00a0provides the technical requirements needed for filers to use Inline XBRL.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Who should I contact for questions on Inline XBRL?<\/strong><\/span><\/p><p><span style=\"color: #000000;\">For questions on Inline XBRL rule requirements and compliance related to operating company financial statement information, please contact the Office of Chief Counsel in the Division of Corporation Finance at 202-551-3500 or using the form at\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/forms\/corp_fin_interpretive\">https:\/\/www.sec.gov\/forms\/corp_fin_interpretive<\/a>. Please select \u201cOffice of Chief Counsel\u201d in the form.<\/span><\/p><p><span style=\"color: #000000;\">For questions on Inline XBRL rule requirements and compliance related to fund risk\/return summary information, please contact the Office of Chief Counsel in Division of Investment Management at 202-551-6825 or\u00a0<a style=\"color: #000000;\" href=\"mailto:IMOCC@sec.gov.\">IMOCC@sec.gov<\/a>.<\/span><\/p><p><span style=\"color: #000000;\">For questions on structured data or other technical questions such as XBRL validation, taxonomies, and data quality, please contact the Office of Structured Disclosure in the Division of Economic and Risk Analysis at 202-551-5494 or\u00a0<a style=\"color: #000000;\" href=\"mailto:StructuredData@sec.gov\">StructuredData@sec.gov<\/a>.<\/span><\/p><p><span style=\"color: #000000;\">For questions on submitting forms through EDGAR and other submission questions, please contact EDGAR Filer Support at 202-551-8900<\/span><\/p><p><span style=\"color: #000000;\">Small entities may also be interested in reviewing the following compliance guides:<\/span><\/p><ul><li><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/corpfin\/operating-company-inline-xbrl-filing-tagged-dataoperating-company-inline-xbrl-filing\">Operating Company Inline XBRL Filing of Tagged Data: A Small Entity Compliance Guide for Issuers<\/a><\/span><\/li><li><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/investment\/open-end-management-investment-company-inline-xbrl-filing-tagged-data\">Open-End Management Investment Company Inline XBRL Filing of Tagged Data: A Small Entity Compliance Guide for Issuers<\/a><\/span><\/li><\/ul><p>\u00a0<\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>URL-5:<\/strong><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs\"><strong>https:\/\/www.sec.gov\/structureddata\/FAQs<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Staff Interpretations and FAQs Related to Interactive Data Disclosure<\/strong><\/span><\/p><p><span style=\"color: #000000;\">From time to time, the staff of the Division of Economic and Risk Analysis will publish interpretations and FAQs to help filers understand how to comply with the Commission&#8217;s interactive data disclosure rules.<\/span><\/p><p><span style=\"color: #000000;\">The answers to these frequently asked questions represent the views of the Staff of the Division of Economic and Risk Analysis. They are not rules, regulations or statements of the Securities and Exchange Commission. Further, the Commission has neither approved nor disapproved them.<\/span><\/p><p><span style=\"color: #000000;\">For further information please also review the Division of Corporation Finance&#8217;s\u00a0Compliance and Disclosure Interpretations for Release 33-9002.<\/span><\/p><ol><li><span style=\"color: #000000;\">Validation<\/span><\/li><li><span style=\"color: #000000;\">Presentation and Rendering \u2014 All Submissions<\/span><\/li><li><span style=\"color: #000000;\">Presentation and Rendering \u2014 Risk\/Return Summaries<\/span><\/li><li><span style=\"color: #000000;\">Standard Taxonomies<\/span><\/li><li><span style=\"color: #000000;\">Company Extensions and Instances<\/span><\/li><li><span style=\"color: #000000;\">Detail Tagging<\/span><\/li><li><span style=\"color: #000000;\">Element Selection<\/span><\/li><\/ol><p><span style=\"color: #000000;\"><strong>FAQ&#8217;s<\/strong><\/span><\/p><ol><li><span style=\"color: #000000;\"><strong> Validation<\/strong><\/span><\/li><\/ol><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.A.1\"><strong>Question A.1<\/strong><\/a>\u00a0(formerly Question 1)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Are submissions under the Voluntary Filing Program (VFP) validated the same way as those under the mandatory program adopted in Release 33-9002?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0No. Interactive Data submissions are EX-101 attachments validated according to EDGAR Filer Manual Chapter 6. VFP Data submissions are EX-100 attachments validated as in EDGAR Filer Manual Chapter 5.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.A.2\"><strong>Question A.2<\/strong><\/a>\u00a0(formerly Question 2)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0How does the EDGAR validator validate HTML embedded into Block Text?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0In all SEC submissions and attachments (other than Ex. 100 and Ex. 101), EDGAR rejects HTML that does not conform to a restriction of HTML 3.2 DTD, in particular rejecting anything that could pose a security threat to a recipient. On that general principle, the EDGAR Validator will analyze Interactive Data content that, when un-escaped, may be interpreted as HTML, and will reject it if it contains content that the existing DTD would reject. EDGAR Filer Manual Rules 6.5.15 and 6.5.16 address this currently. Note that Block Text content must also be well formed XML. This is a stronger requirement than validating against the EDGAR HTML 3.2 DTD.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.A.3\"><strong>Question A.3<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0How can I tell whether a warning or an error from my test filing validation is related to XBRL and what would have happened if the filing had been live?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0An EDGAR filing can be accepted with \u2018Warnings\u2019 even if some of its attached exhibits have errors. Exhibits that have errors are stripped from the filing before it is accepted into EDGAR. XBRL files are exhibits. Therefore, an error message that looks like this \u201cWRN: XBRL Error\u2026\u201d means that the XBRL files will be stripped from a live filing, but the rest of the filing will be accepted into EDGAR. If this happens the filer must submit an Amendment with the corrected XBRL.<\/span><\/p><p><span style=\"color: #000000;\">A message that looks like this \u201cWRN: XBRL Warning\u2026\u201d means that there is a minor error in the XBRL exhibit, but the XBRL file will not be stripped. We encourage filers to fix these errors in their subsequent filings. A message that looks like \u201cERR:\u201d or \u201cWRN:\u201d but does not mention XBRL is not an XBRLproblem, and is due to some other aspect of the submission.<\/span><\/p><ol><li><span style=\"color: #000000;\"><strong> Presentation and Rendering \u2014 All Submissions<\/strong><\/span><\/li><\/ol><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.1\"><strong>Question B.1<\/strong><\/a>\u00a0(formerly Question 4)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Can I still view submissions made under the Voluntary Filing Program?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0No. The older Voluntary Filing Program Data Viewers are separate from the Interactive Data Viewer and are currently not supported by the SEC.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.2\"><strong>Question B.2<\/strong><\/a>\u00a0(formerly Question 5)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0If a filer uses the Interactive Data Previewer, is there any guarantee that end users will see the same rendering?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes. If Interactive Data pursuant to the rules in Release No. 33-9002 is previewed using the Interactive Data Previewer, then the rendering will be the same.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.3\"><strong>Question B.3<\/strong><\/a>\u00a0(formerly Question 6)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0How do I ensure that a statement renders with periods as rows rather than as columns, with a specific axis as columns, ignoring some axis, or other arrangements?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>There are some rules in the EDGAR Filer Manual oriented toward rendering. For example, EDGAR Filer Manual rule 6.7.12 explains how to order the pages to be rendered from a submission by manipulating the link:description element of link:roleType declarations, rule 6.13.4 describes how parentheticals should be arranged in the presentation linkbase, etc.<\/span><\/p><p><span style=\"color: #000000;\">The general approach of the rendering engine is to infer layout from the contents of the instance first, then use the presentation linkbase to adjust it, then use key words in the role definition to further adjust it. Here are the basic rendering strategies:<\/span><\/p><ol><li><span style=\"color: #000000;\">Facts are arranged into columns with descending periods from left to right without regard to anything in the taxonomy.<\/span><\/li><li><span style=\"color: #000000;\">Facts are shown in the same column if their end date and instant are the same, again without regard to anything in the taxonomy.<\/span><\/li><li><span style=\"color: #000000;\">Facts are then shifted one column to the left if there is a &#8220;period start&#8221; preferred label, but only if the role definition contains the phrase &#8220;cash&#8221; followed by &#8220;flow&#8221;. If the role definition contains the word \u201ccash\u201d or \u201cflow\u201d then adjacent columns containing duration facts and instant facts at the beginning and end of that duration may be merged together.<\/span><\/li><li><span style=\"color: #000000;\">Rows are grouped together according to the axes and domain members that appear in the facts. Groups of facts that all share the same set of axes and domain members appeartogether, and are ordered according to the order in which the domain members appear in the presentation linkbase as direct children of the axes. The axes are then ordered according to their order in the presentation.<\/span><\/li><li><span style=\"color: #000000;\">If the role definition contains these word combinations, then the periods become rows and the Equity Components Class axis are the columns, ordered as they appear in the presentation linkbase: (a) &#8220;stockholder&#8221; and &#8220;equity&#8221; or &#8220;deficit&#8221; but not &#8220;parenthetical&#8221; (b) &#8220;shareholder&#8221; and &#8220;equity&#8221; or &#8220;deficit&#8221; but not &#8220;parenthetical&#8221; (c) &#8220;partners&#8221; and &#8220;capital&#8221; but not &#8220;parenthetical&#8221; (d) &#8220;changes&#8221; and &#8220;equity&#8221; but not &#8220;parenthetical&#8221;.<\/span><\/li><\/ol><p><span style=\"color: #000000;\">The personal renderer, which can be downloaded from\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/edgarvalandrender\">https:\/\/www.sec.gov\/structureddata\/edgarvalandrender<\/a>, contains a document with more detailed information about the personal renderer and how it works.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.4\"><strong>Question B.4<\/strong><\/a>\u00a0(formerly Question 7)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Will Inline XBRL submissions be accepted in the future?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0The conditions under which Inline XBRL may be accepted, and how the processing may be integrated into the EDGAR validation and the Interactive Data Viewer processes have not yet been determined.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.5\"><strong>Question B.5<\/strong><\/a>\u00a0(formerly Question 8)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What does the Interactive Data Previewer do with filings that do not pass validation?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0The previewer does not test the validity of the filing; you must do this separately either by submitting it as an EDGAR test filing or using a commercial validation software product that tests filings against the Commission&#8217;s rules. The previewer renders invalid filings as best it can, but may fail in a way that does not identify the root cause. Additionally, the previewer may produce results that \u201clook\u201d right, even if the filing has errors that could cause the XBRL to be removed from a live filing if submitted For these reasons, we encourage the use of a test filing prior to final submission.(See A.3).<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.6\"><strong>Question B.6<\/strong><\/a><strong>\u00a0<\/strong>(formerly Question 9)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0How do I arrange for facts with different types to appear on the same row?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>For the most part, the viewer cannot render facts of different types on the same row.<\/span><\/p><p><span style=\"color: #000000;\">The rendering engine does have the ability to render complex dimensional data layouts, including rows with a mix of data types, by \u201cembedding\u201d table layout commands into text blocks; this is described in the Risk\/Return Rendering guide (see C.1).<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.7\"><strong>Question B.7<\/strong><\/a>\u00a0(formerly Question 11)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0I got some of the label linkbases for my submission from a site that used xml:lang=&#8221;en&#8221; instead of xml:lang=&#8221;en-US&#8221;, will they render correctly?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0It does not matter whether they render correctly in the previewer or not, the submission should be rejected by the Validator if facts use a mix of &#8220;en&#8221; and &#8220;en-US&#8221; labels. (See B.5).<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.8\"><strong>Question B.8<\/strong><\/a>\u00a0(formerly Question 12)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Why is some of my escaped HTML rendering as raw HTML?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Make sure that the embedded HTML appears inside of elements whose type is nonnum:textBlockItemType. It is not enough for the element name to end with &#8220;TextBlock&#8221;. Different versions of the XBRL US GAAP Taxonomy may have more or less consistent element naming conventions, but it is the element type that is important, not the element name. See EFM 6.5.16 for examples of correct escaping.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.9\"><strong>Question B.9<\/strong><\/a>\u00a0(Reserved)<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.10\"><strong>Question B.10<\/strong><\/a>\u00a0(formerly Question 21)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What does it mean for the presentation to &#8220;match&#8221; the original HTML\/ASCII document?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0EDGAR Filer Manual rule 6.13.1 states this requirement more precisely. The presentation relationships within a given role (for a statement, say) must be the same as the original ordering. Also, the indentation of real financial statements is much &#8220;flatter&#8221; than the deep nesting of a typical standard taxonomy, and the presentation linkbase should reflect that. Also, EDGAR Filer Manual rule 6.13.4 forces parentheticals out of the main statement roles, and into separate roles specifically for parentheticals.<\/span><\/p><p><span style=\"color: #000000;\">This is why standard presentation linkbases are usually not in the list of taxonomies on the SEC website. Consider: the element order must match the order of the Original HTML\/ASCII file. If a standard presentation linkbase (for a statement or a disclosure) were included in the DTS of an instance, then any change of order (due to a difference in materiality, for example) would require both a prohibiting relationship as well as the new label. In the case of the XBRL US GAAP Taxonomies 1.0 standard presentation linkbases, only a small percentage of those presentation relationships even in the smaller statements and disclosures are likely to be a match to the ordering of a filer&#8217;s financial statements. The EDGAR Validator lets the filer construct the presentation order appropriate for the instance, and requires no other presentation relationships. A filer should expect their company presentation linkbase to change in some way with every new filing, though perhaps not as much as the instance and labels change.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.11\"><strong>Question B.11<\/strong><\/a>\u00a0(formerly Question 32)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0How do I make a text block appear by itself in a presentation link role as 6.12.3 seems to require? Do I have to provide a heading?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0The way to satisfy these rules is to use an abstract to be the parent of the text block, in each of the separate roles. For example,<\/span><\/p><p><span style=\"color: #000000;\">&#8211; 06100 &#8211; Disclosure &#8211; Business Segments (Level i)\u00a0<strong>Segment Disclosure [Abstract] + Segment Disclosure [Text Block]<\/strong><\/span><\/p><p><span style=\"color: #000000;\">&#8211; 06101 &#8211; Disclosure &#8211; Oil Reserves (Level i)\u00a0<strong>Oil Reserves Disclosure [Abstract] + Oil Reserves Disclosure [Text Block]<\/strong><\/span><\/p><p><span style=\"color: #000000;\">And so on.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.12\"><strong>Question B.12<\/strong><\/a>\u00a0(formerly Question 41)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Should filers use a certain naming convention for presentation group titles?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0As noted in B.3 above, EFM section 6.7.12 describes the technical format of the presentation group \u201cdescription\u201d field, of which the \u201cTitle\u201d is one part. While there is no requirement to follow a standard naming convention for the Title, we encourage filers to use the presentation group titles described below:<\/span><\/p><ul><li><span style=\"color: #000000;\">Title Document and Entity Information &#8220;Document and Entity Information.&#8221;<\/span><\/li><li><span style=\"color: #000000;\">Title Level I presentation groups in a manner consistent with the title of the financial statements and footnotes appearing in the original HTML\/ASCII version. For example, a title for the balance sheet presentation group might be &#8220;Condensed Consolidated Balance Sheets,&#8221; and a text-blocked footnote title might be &#8220;Commitments and Contingencies.&#8221; Also, parenthetical disclosures should follow the naming convention of the financial statement to which they relate, such as, for example, &#8220;Condensed Consolidated Balance Sheets (Parenthetical).&#8221;<\/span><\/li><li><span style=\"color: #000000;\">Title Level II significant accounting policies as one presentation group titled &#8220;Official HTML\/ASCII Documents&#8217; Note Label (Policies),&#8221; such as, for example, &#8220;Significant Accounting Policies Note (Policies).&#8221;<\/span><\/li><li><span style=\"color: #000000;\">Title Level III text-blocked tables &#8220;Official HTML\/ASCII Documents&#8217; Note Label (Table).&#8221; We suggest that all Level III text-blocked tables relating to tables appearing within a single footnote in the original HTML\/ASCII version be included in a single presentation group. For example, all tables appearing in the &#8220;Cash and Cash Equivalents&#8221; footnote would be in the presentation group titled, &#8220;Cash and Cash Equivalents (Tables).&#8221;<\/span><\/li><li><span style=\"color: #000000;\">Title Level IV detail tagged groups \u201cOfficial HTML\/ASCII Documents\u2019 Note Label 1st Table Name (Details),\u201d \u201cOfficial HTML\/ASCII Documents\u2019 Note Label 2nd Table Name (Details),\u201d and so forth.<\/span><\/li><\/ul><p><span style=\"color: #000000;\">Also, EFM section 6.7.9 defines the technical format of the presentation group\u2019s \u2018roleURI\u2019 attribute which ends with a \u201cmnemonic name in LC3 format\u201d. It is not necessary for that mnemonic name to match the group title word-for-word.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.13\"><strong>Question B.13<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Should filers use a certain ordering convention for presentation groups?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0The rendering engine has been updated to allow users to more easily navigate through the rendered interactive data. Hyperlinks to sections of the filing are now grouped under expandable standard headings. This navigation structure is based on the presentation group ordering currently in use by virtually all filers, so filers should not need to change their existing presentation group ordering to use this structure. Information is provided here to show the standard headings and give examples of presentation groups found under each heading, and for troubleshooting purposes if filers experience an unexpected result with this structure.<\/span><\/p><ul><li><span style=\"color: #000000;\">To take advantage of this navigation structure, presentation groups should appear in the following order:<\/span><\/li><li><span style=\"color: #000000;\">Document and entity information<\/span><\/li><li><span style=\"color: #000000;\">Financial statements and parenthetical disclosures<\/span><\/li><li><span style=\"color: #000000;\">Notes to the financial statements<\/span><\/li><li><span style=\"color: #000000;\">Significant accounting policies<\/span><\/li><li><span style=\"color: #000000;\">Table text blocks<\/span><\/li><li><span style=\"color: #000000;\">Detail tagged information<\/span><\/li><\/ul><p><span style=\"color: #000000;\">The following table shows the standard headings in the navigation structure and the presentation groups that appear under each of the standard headings. If the presentation groups are in a different order, groups may inadvertently appear under the Uncategorized heading. For example, if \u201cPolicy\u201d appears after \u201cTable\u201d, all groups after \u201cPolicy\u201d will appear under the Uncategorized heading. Note that using the plural form in a presentation group name, for example \u201cStatements\u201d or \u201cPolicies\u201d, will not affect whether the group appears under its designated standard heading.<\/span><\/p><table><tbody><tr><td width=\"200\"><p><span style=\"color: #000000;\"><strong>Standard heading appearing in rendering navigation structure<\/strong><\/span><\/p><\/td><td width=\"215\"><p><span style=\"color: #000000;\"><strong>Standard heading will contain these presentation groups<\/strong><\/span><\/p><\/td><td width=\"186\"><p><span style=\"color: #000000;\"><strong>Example<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"200\"><p><span style=\"color: #000000;\">Cover<\/span><\/p><\/td><td width=\"215\"><p><span style=\"color: #000000;\">Any group appearing before first group name containing the words \u201cStatement\u201d or \u201cParenthetical\u201d<\/span><\/p><\/td><td width=\"186\"><p><span style=\"color: #000000;\">Document and Entity Information<\/span><\/p><\/td><\/tr><tr><td width=\"200\"><p><span style=\"color: #000000;\">Financial Statement<\/span><\/p><\/td><td width=\"215\"><p><span style=\"color: #000000;\">Any group name containing the words \u201cStatement\u201d or \u201cParenthetical\u201d<\/span><\/p><\/td><td width=\"186\"><p><span style=\"color: #000000;\">Statement of Income statement of Income (Parentheticals)<\/span><\/p><\/td><\/tr><tr><td width=\"200\"><p><span style=\"color: #000000;\">Notes to Financial Statement<\/span><\/p><\/td><td width=\"215\"><p><span style=\"color: #000000;\">Any group name not containing the words \u201cStatement\u201d or \u201cParenthetical\u201d<\/span><\/p><\/td><td width=\"186\"><p><span style=\"color: #000000;\">Inventories Income Taxes<\/span><\/p><\/td><\/tr><tr><td width=\"200\"><p><span style=\"color: #000000;\">Accounting Policies<\/span><\/p><\/td><td width=\"215\"><p><span style=\"color: #000000;\">Any group name containing the word \u201cPolicy\u201d and not containing the words \u201cStatement\u201d or \u201cParenthetical\u201d<\/span><\/p><\/td><td width=\"186\"><p><span style=\"color: #000000;\">Inventory (Policy) Income Tax (Policy)<\/span><\/p><\/td><\/tr><tr><td width=\"200\"><p><span style=\"color: #000000;\">Notes Tables<\/span><\/p><\/td><td width=\"215\"><p><span style=\"color: #000000;\">Any group name containing the word \u201cTable\u201d and not containing the words \u201cStatement\u201d or \u201cParenthetical\u201d<\/span><\/p><\/td><td width=\"186\"><p><span style=\"color: #000000;\">Inventories (Tables) Income Tax (Tables)<\/span><\/p><\/td><\/tr><tr><td width=\"200\"><p><span style=\"color: #000000;\">Notes Details<\/span><\/p><\/td><td width=\"215\"><p><span style=\"color: #000000;\">Any group name containing the word \u201cDetail\u201d and not containing the words \u201cStatement\u201d or \u201cParenthetical\u201d<\/span><\/p><\/td><td width=\"186\"><p><span style=\"color: #000000;\">Inventories (Details) Income Tax (Details)<\/span><\/p><\/td><\/tr><tr><td width=\"200\"><p><span style=\"color: #000000;\">Uncategorized<\/span><\/p><\/td><td width=\"215\"><p><span style=\"color: #000000;\">Any group appearing after the groups listed above<\/span><\/p><\/td><td width=\"186\"><p>\u00a0<\/p><\/td><\/tr><tr><td width=\"200\"><p><span style=\"color: #000000;\">All Reports<\/span><\/p><\/td><td width=\"215\"><p><span style=\"color: #000000;\">All Presentation Groups<\/span><\/p><\/td><td width=\"186\"><p>\u00a0<\/p><\/td><\/tr><\/tbody><\/table><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.15\"><strong>Question B.1<\/strong><\/a><strong>4<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0How should EFM 6.6.7, 6.6.8, 6.6.9, 6.6.10, and 6.13.3 be considered when modeling dimensions on the face financial statements?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0When applying dimensional modeling to the face financial statements, the XBRL viewer is programmed to render line items with an Axis (dimensions) after those without an Axis (dimension). Due to this rendering programming, it will not be possible to satisfy the requirements of EFM 6.6.7 through 6.6.10 and 6.13.3. Therefore, when using dimensions on the face financial statements, one should apply EFM 6.6.7 through 6.6.10 rather than EFM 6.13.3<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.B.15\"><strong>Question B.15<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0When tagging a line item with multiple text descriptions in the original HTML presented in a roll forward for 3 years, the line item element requires three different negating labels which limit the available label roles, does rule 6.11.1 still apply?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes, to accommodate this scenario, merge the text from the three periods in a way that is readable and does not lose any information.<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><ol><li><span style=\"color: #000000;\"><strong> Presentation and Rendering \u2014 Risk\/Return Summaries<\/strong><\/span><\/li><\/ol><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.C.1\"><strong>Question C.1<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Is there any guidance published by the SEC on XBRL for risk return summary filings?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes. Please click on the following link to find the Mutual Fund Risk Return Summary Preparers Guide:\u00a0<a style=\"color: #000000;\" href=\"https:\/\/xbrl.sec.gov\/rr\/2018\/rr-preparers-guide-2018-03-12.pdf\">https:\/\/xbrl.sec.gov\/rr\/2018\/rr-preparers-guide-2018-03-12.pdf<\/a>.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">Also please click on the following link to access the Mutual Fund Risk Return Summary rendering guide,\u00a0<a style=\"color: #000000;\" href=\"http:\/\/xbrl.sec.gov\/rr\/2010\/rr-rendering-2010-02-28.pdf\">http:\/\/xbrl.sec.gov\/rr\/2010\/rr-rendering-2010-02-28.pdf<\/a>.<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><ol><li><span style=\"color: #000000;\"><strong> Standard Taxonomies<\/strong><\/span><\/li><\/ol><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.D.1\"><strong>Question D.1<\/strong><\/a>\u00a0(formerly Question 15)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Which files from a standard taxonomy can an Interactive Data submission refer to?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0The schema files of a taxonomy that define elements, types or roles are listed on the SEC website\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/info\/edgar\/edgartaxonomies.shtml\">https:\/\/www.sec.gov\/info\/edgar\/edgartaxonomies.shtml<\/a>\u00a0as soon as the taxonomy is available for use in EDGAR.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">Linkbase files of a taxonomy cannot generally be used except in specific circumstances, in which case the linkbase will appear in the list. Specific circumstances may include:<\/span><\/p><p>\u00a0<\/p><ol><li><span style=\"color: #000000;\">The linkbase defines a form, such as the Form N-1A, that mandates a particularpresentation order, and the element labels need not be modified by the filer;<\/span><\/li><li><span style=\"color: #000000;\">The linkbase contains definition relationships that cannot be overridden because they define a table of data structured in a way mandated by a Commission Rule.<\/span><\/li><\/ol><p><span style=\"color: #000000;\">Entry point schemas (schemas with no elements or types but only linkbase references) will generally not be allowed, except where they support exceptions (a) and (b) above.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.D.2\"><strong>Question D.2<\/strong><\/a>\u00a0(formerly Question 16)<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What does it mean to &#8220;use the US GAAP Taxonomy&#8221; if EFM 6.3.6 prohibits a filing from referring to the US GAAP Taxonomy schema files?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0US GAAP Taxonomy linkbases are to be used as templates to copy from during the preparation process, but their inclusion in an EDGAR filing tends to load unused linkbases and therefore introduces unwarranted complications such as unused extended links and a need for many prohibiting relationships. Reducing the amount of content in the DTS of the instance to its essentials frees users to more easily link the submitted documents to the linkbases of their particular interest for analysis.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.D.3\"><strong>Question D.3<\/strong><\/a>\u00a0(formerly Question 17)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What does it mean to &#8220;use the C&amp;I Industry Taxonomy&#8221; if the filing cannot refer to C&amp;I Taxonomy linkbases?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0As EDGAR Filer Manual rule 6.6.29 says:<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">The calculation, definition, and presentation linkbases published along with standard taxonomies schemas are extremely useful ways to communicate how elements are related to each other, but these linkbases are to be used as templates by preparers to build their own linkbases to communicate their own intended relationships. Also, any element in a standard taxonomy schema may be used in an instance that has the schema in its DTS independently of which &#8220;industry&#8221; linkbases it might have appeared in. Therefore it is the elements standing by themselves with their definitions, references and attributes that are definitive.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.D.4\"><strong>Question D.4<\/strong><\/a>\u00a0(formerly Question 18)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Do all the rules in EDGAR Filer Manual chapter 6 apply to the standard taxonomies?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0No. The rules in EDGAR Filer Manual chapter 6 apply to company extensions and instances. Although the standard taxonomies are consistent with many of the EDGAR Filer Manual rules, here are some exceptions:<\/span><\/p><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">File names, namespaces, schemaLocation and xlink:href attributes of a standardtaxonomy are not restricted by any of the EDGAR Filer Manual rules.<\/span><\/li><li><span style=\"color: #000000;\">Element declarations: A standard taxonomy might include elements that do not follow the LC3 convention.<\/span><\/li><li><span style=\"color: #000000;\">Role declarations: A linkbase xlink:role might be defined as being used on only one type of linkbase instead of all three.<\/span><\/li><li><span style=\"color: #000000;\">Linkbases: Since these linkbases will not be in the submission&#8217;s DTS anyway, there may be any number of EDGAR Filer Manual violations.<\/span><\/li><\/ul><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.D.5\"><strong>Question D.5<\/strong><\/a>\u00a0(formerly Question 19)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Does 6.9.3 forbid the use of &#8216;prohibited&#8217; arcs because such an arc would then cause some arc to be &#8216;ineffectual&#8217;?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0The rule applies only to arcs in the company extension taxonomy. If the company extension taxonomy has a &#8216;prohibiting&#8217; arc that prohibits an arc in a standard taxonomy, then it&#8217;s the standard taxonomy that has the &#8216;ineffectual&#8217; arc, not the company extension.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.D.6\"><strong>Question D.6<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0EDGAR Filer Manual rule 6.5.21 requires some forms to contain a \u201cDocument Fiscal Period Focus\u201d entity information element in the Required Context. What values should filers use for this element?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Filers should use the following values:<\/span><\/p><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">FY &#8211; Fiscal Year, used for annual filing<\/span><\/li><li><span style=\"color: #000000;\">Q1 &#8211; First Quarter of the fiscal year, used for Form 10-Q filings<\/span><\/li><li><span style=\"color: #000000;\">Q2 &#8211; Second Quarter of the fiscal year, used for Form 10-Q filings<\/span><\/li><li><span style=\"color: #000000;\">Q3 &#8211; Third Quarter of the fiscal year, used for Form 10-Q filings<\/span><\/li><\/ul><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.D.6.1\"><strong>Question D.6.1<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0I am preparing a FORM 10-KT for a period other than 12 months (e.g., 1\/1\/2012 thru 8\/31\/2012), should I use \u201cFY\u201d for the DocumentFiscalPeriodFocus?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.D.7\"><strong>Question D.7<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0I am preparing a company&#8217;s FORM S-4 that also includes XBRL for the acquiring company. Should I include the EntityCentralIndexKey element with our CIK number for the acquiring company?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0You must provide one EntityCentralIndexKey element in the required context and it should be for the parent (consolidated) company. Note that required contexts are distinguished by having no xbrli:segment elements (e.g., dimension members).<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.D.8\"><strong>Question D.8<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Once a new taxonomy (e.g., US GAAP taxonomy) is approved and available for use, when should a filer make the transition to the new version?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0The U.S. GAAP taxonomy is subject to accounting standards and changes. In general, we only support two versions of the U.S. GAAP taxonomy at one time. Indication that the updated taxonomy is available for use will be made via the standard taxonomies page at\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/info\/edgar\/edgartaxonomies.shtml\">https:\/\/www.sec.gov\/info\/edgar\/edgartaxonomies.shtml<\/a>. The SEC staff strongly encourages filers to use the most recent version of the US GAAP taxonomy release for their Interactive Data submissions to take advantage of the most up to date tags related to new accounting standards and other improvements.<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><ol><li><span style=\"color: #000000;\"><strong> Company Extensions and Instances<\/strong><\/span><\/li><\/ol><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.1\"><strong>Question E.1<\/strong><\/a>\u00a0(formerly Question 3)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Characters that are &#8220;special&#8221; are forbidden by EDGAR Filer Manual 6.10.6 but they appear in the Original HTML\/ASCII, so how do I get them into labels?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Use the XML numeric character codes from the column titled Character Reference (Dec) of the table in section 5.2.2.6.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.2\"><strong>Question E.2<\/strong><\/a>\u00a0(formerly Question 20)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What does it mean for an element label to be &#8220;the same&#8221; as the original HTML\/ASCII document?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0EDGAR Filer Manual rule 6.11.1 states this more precisely. Roughly speaking, all the contents of the Original HTML\/ASCII Document must appear somewhere in the EX-101 attachments, and all contents of the EX-101 attachments must appear somewhere in the Original. The rules adopted in Release 33-9002 do not require identical appearance, and neither does the EDGAR Filer Manual. Achieving adequate correspondence is the source of many of the &#8220;semantic&#8221; rules in EDGAR Filer Manual Chapter 6.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">This is why standard label linkbases are usually not in the list of taxonomies on the SEC website. Consider: all element labels must match the exact wording in the Original HTML\/ASCII file. If a standard label link base were included in the DTS of an instance, then any label that would be different would require both a prohibiting relationship as well as the new label. In the case of the XBRL US GAAP Taxonomies 1.0 us-gaap standard label linkbase, the file is 9MB, containing some 12,000 element labels, yet a very small percentage of those are ever likely to be an exact match to the line item of a filer&#8217;s financial statement. The EDGAR Validator lets the filer assign a label to each element that is used in the instance, and requires no other labels. A filer should expect their company label linkbase to change in some way with every new filing, just as the instance will change.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.3\"><strong>Question E.3<\/strong><\/a>\u00a0(formerly Question 22)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Am I required to use existing linkbase roles or make up my own? Can they change with every submission?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0EDGAR Filer Manual rule 6.7.12 explains that filers should develop an ordering and naming scheme that is appropriate to the organization of their Original HTML\/ASCII Document while supporting a sensible (though obviously not identical) rendering. That implies filer-specific roles. Changing the roles frequently is akin to frequently changing the elements used in the instance: there is no rule against it, but given such freedom to define the roles at the outset, a reasonable amount of forethought should lead to a stable arrangement.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.4\"><strong>Question E.4<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong><br \/><\/strong>(Reserved)<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.5\"><strong>Question E.5<\/strong><\/a><\/span><\/p><p><br \/><span style=\"color: #000000;\">(Reserved)<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.6\"><strong>Question E.6<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0The submission I am tagging requires the public float, so what context should I use?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Please refer to the EDGAR Filer Manual section 6.5.21 for examples of the required context.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.7\"><strong>Question E.7<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Am I required to put in a value for AmendmentDescription when I set the value to true for the AmendmentFlag?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes. AmendmentDescription should be a nonempty fact if and only if the AmendmentFlag is set to true (EFM 6.5.20)<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.8\"><strong>Question E.8<\/strong><\/a><\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">(Reserved)<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.9\"><strong>Question E.9<\/strong><\/a>\u00a0(formerly Question 28)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Can the content of a text block be in a language other than US English (\u201cen-US\u201d)?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes. Starting with the 2009 US-GAAP taxonomy, a filer may use a language other than US English; Please see EFM 6.5.14 for conditions.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.10\"><strong>Question E.10<\/strong><\/a>\u00a0(formerly Question 29)<\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Since the target of the dimension-default and dimension-domain relationships must be a domain or member, why not also the domain-member relationship?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0That restriction would not work because the domain-member relationship also represents the hierarchy of primary items.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.11\"><strong>Question E.11<\/strong><\/a>\u00a0(formerly Question 30)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Does 6.16.2 allow for multiple dimension-default effective arcs as long as they all have the same source and target?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Note that XBRL Dimensions 1.0 specification would require a validation error to be signaled if the targets were different, no matter in which link role they appeared. Furthermore, if the duplicated arcs had the same link role and priority one of them would be ineffectual and thus forbidden by rule 6.9.3.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.12\"><strong>Question E.12<\/strong><\/a><\/span><\/p><p><br \/><span style=\"color: #000000;\">(Reserved)<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.13\"><strong>Question E.13<\/strong><\/a>\u00a0(formerly Question 33)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0EDGAR Filer Manual 6.7.10 seems redundant with XBRL 2.1&#8217;s prohibition on duplicate role declarations.<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0XBRL 2.1 forbids duplicate role declarations in a schema file; 6.7.10 applies to the entire DTS.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.14\"><strong>Question E.14<\/strong><\/a>\u00a0(formerly Question 34)<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0EDGAR Filer Manual 6.8.1 seems to contradict Section 405(c)(1) of Regulation S-T (17 CFR \u00a7232.405(c)(1)), which requires each data element and label contained in the Interactive Data File to reflect the same information in the corresponding data in the Related Official Filing.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Section 405(c)(1) of Regulation S-T (17 CFR \u00a7232.405(c)(1)) takes precedence.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.15\"><strong>Question E.15<\/strong><\/a>\u00a0(formerly Question 36)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Should elements for line items appearing with a dash (&#8220;-&#8220;) in the original HTML\/ASCII version be tagged with a &#8220;0&#8221;?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0A filer may simply not tag the element for line items appearing as an empty field or a dash. For example, if &#8220;Notes Receivable&#8221; appears on the balance sheet with a $1,000 balance this year-end and a dash last year-end, the filer can simply not tag the &#8220;Notes Receivable&#8221; element for last year&#8217;s balance. Taking this action will render an empty field by our rendering engine for last year&#8217;s balance. Our rendering engine will not currently render dashes. If the filer wants to tag one or more line items that appear with an empty field or a dash with a zero value because that&#8217;s what management believes the item represents, and they think the distinction is useful, they can choose to do so. This guidance applies to all the financial statements, including the statement of shareholder&#8217;s equity, the financial statement schedules, as well as to footnote data tagged at Level IV.<\/span><\/p><p><span style=\"color: #000000;\">For the Commitments and Contingencies line item on the balance sheet where all columns are either blank or have dashes, the filer should set the NIL attribute to true without tagging the element with any information. This guidance is described under Edgar Filer Manual Section 6.6.15. Taking this action will render an empty field under all columns by our rendering engine.<\/span><\/p><p><span style=\"color: #000000;\">Also, a filer may have a line item such as Preferred Stock on the balance sheet where all columns are either blank or have dashes. This could be the case when there are authorized shares, but none are issued. To tag monetary items such as this, the filer can set the NIL attribute to true without tagging any information, similar to the Commitments and Contingencies line item as described above. Taking this action will render an empty field under all columns by our rendering engine. Alternatively, the filer can tag the element with zeros if they believe the distinction is useful.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.16\"><strong>Question E.16<\/strong><\/a>\u00a0<strong>(Updated 02\/05\/2013)<\/strong>\u00a0(formerly Question 38)<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Should filers use the pre-defined table structures and axes in the US GAAP Taxonomies?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0We strongly recommend that filers utilize the pre-defined table structures and axes as they exist in the US GAAP Taxonomies. Creating new hypercubes (tables) and dimensions (axes) should generally be avoided. Custom tables and axes have a negative impact on analysis of the financial information affecting comparability and should be avoided wherever possible. In addition, filers should also avoid creating new domains or changing default member elements for pre-defined dimensions.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">For example, when filers are tagging a Property, Plant and Equipment note at Level 4, they should use the pre-defined dimensional Schedule of Property Plant and Equipment [Table], and axes; extending members or line items only when necessary. Similarly, filers tagging components of inventory presented with columns for each balance sheet period should use the pre-defined non-dimensional elements for that disclosure.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.17\"><strong>Question E.17<\/strong><\/a>\u00a0(formerly Question 43)<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What are some of the nuances associated with preparing an interactive data file in situations involving separate entities filing a single set of financial statements, where multiple CIKs are concerned\u2014such as by a filer who is a consolidated parent company with wholly-owned subsidiaries (which have their own CIKs), or by dual listed companies with their own CIKs?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0The Division of Corporation Finance&#8217;s Compliance and Disclosure Interpretation for Exchange Act Forms 104.16 explains that, in cases of dual listed companies the filer may choose which CIK to use but should continue to use that CIK in every filing as long as the companies continue to be dual listed and file joint reports. Though not addressed in a CDI, in the consolidated parent company case, the CIK of the consolidated parent company must be used. In either of the aforementioned cases, that CIK must then be used uniformly throughout all the XBRL &#8220;identifier&#8221; elements in each filing, and the same CIK must be used in the identifier element consistently in every filing thereafter. This entity is referred to as the Consolidated Entity and is the &#8220;default legal entity,&#8221; as described in EDGAR Filer Manual rule 6.6.3. When the facts about more than one entity are contained in a single instance document, it is known as a &#8220;consolidating instance&#8221; (see EDGAR Filer Manual rule 6.6.4). EDGAR Filer Manual rules 6.6.3 through 6.6.8 detail how to model a consolidating instance, and while they have been summarized in the table below, filers should consult the EDGAR Filer Manual for complete details.<\/span><\/p><p>\u00a0<\/p><table><tbody><tr><td width=\"278\"><p><span style=\"color: #000000;\"><strong>For a Consolidated Registrant with Subsidiaries:<\/strong><\/span><\/p><\/td><td width=\"297\"><p><span style=\"color: #000000;\"><strong>For Dual (or Multiple) Registrants:<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"278\"><p><span style=\"color: #000000;\">Use the CIK of the Consolidated Entity in the instance; this is the result of complying with EFM rules 6.6.4, 6.6.3, and 6.5.2.<\/span><\/p><\/td><td width=\"297\"><p><span style=\"color: #000000;\">The CIK of any of the registrants can be used as the &#8220;consolidated&#8221; entity, but it must be used consistently in subsequent filings (EFM 6.6.4, 6.6.3, and 6.5.2).<\/span><\/p><\/td><\/tr><tr><td width=\"278\"><p><span style=\"color: #000000;\">Create a separate domain member element for each subsidiary. Typically, the element name for subsidiary Abcd would be &#8220;AbcdMember&#8221;. Use the dimension us gaap:LegalEntityAxis for subsidiaries (EFM 6.6.5).<\/span><\/p><\/td><td width=\"297\"><p><span style=\"color: #000000;\">Create a separate domain member element for each company other than the Consolidated Entity. Typically, the element name for Abcd would be &#8220;AbcdMember&#8221;. Use the dimension dei:LegalEntityAxis for each entity that is not the Consolidated Entity (EFM 6.6.5).<\/span><\/p><\/td><\/tr><tr><td width=\"278\"><p><span style=\"color: #000000;\">For facts that apply to the Consolidated Entity, do not provide any value for dei:LegalEntityAxis. It is the &#8220;default&#8221; member, in XBRL terminology (EFM 6.6.3).<\/span><\/p><\/td><td width=\"297\"><p><span style=\"color: #000000;\">For facts that apply to the Consolidated Entity, do not provide any value for dei:LegalEntityAxis. It is the &#8220;default&#8221; member, in XBRL terminology (EFM 6.6.3).<\/span><\/p><\/td><\/tr><tr><td width=\"278\"><p><span style=\"color: #000000;\">Use domain member element us-gaap:ParentCompanyMember for facts that apply only to the parent holding company, corporate headquarters, or similar legal entity not associated with any specific subsidiary (EFM 6.6.7).<\/span><\/p><\/td><td width=\"297\"><p><span style=\"color: #000000;\">There is no need to use the us-gaap:ParentCompanyMember element.<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p><span style=\"color: #000000;\">EDGAR Filer Manual rules 6.6.3 through 6.6.8 contain examples and detail the technical structure of the dei:LegalEntityAxis, domain, and members. Additional information can also be found on the\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/spotlight\/xbrl\/xbrl-webcasts.shtml\">Public Seminar on Interactive Data Reporting Requirements Webcast<\/a>, held Wednesday, June 10, 2009. Part 2 of the archived webcast, at approximately the 20-minute mark, provides additional detail about the multiple-registrant reporting scenario. Slide numbers 38-41 from the\u00a0<a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/spotlight\/xbrl\/idreportingseminar061009slides-2.pdf\">Panel 2 Slides<\/a>\u00a0(the slide deck which accompanies the webcast) specifically pertain to this portion of the webcast.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.18\"><strong>Question E.18<\/strong><\/a>\u00a0(formerly Question 44)<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Can I report the CIKs associated with the various subsidiaries as referred to in Question E.17?<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Currently, the CIKs of subsidiaries are not required to be reported within the single set of financial statements that satisfy the reporting obligations of reports such as Form 10-K. Because of that, the CIKs associated with the various subsidiaries are not required in the respective dei:EntityCentralIndexKey. The EDGAR system allows their inclusion but does not require them. For example, suppose the consolidated entity has a (hypothetical) CIK 9876543210. Then all of the &#8220;identifier&#8221; elements in the instance must contain 9876543210, and the value of dei:EntityCentralIndexKey in the Required Context must be 9876543210, and the value of dei:RegistrantName in the required context must be the name of the entity with CIK 9876543210. But suppose another (hypothetical) CIK, 8765432109, is reported in the same instance for subsidiary Abcd. In that case the filer may, but is not required to, include facts for dei:EntityCentralIndexKey and dei:RegistrantName that are in a context for which the dei:LegalEntityAxis has the member AbcdMember.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.19\"><strong>Question E.19<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What context period should be used for an event that occurred during the second quarter for a 12\/31 fiscal year end registrant?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0For an element with period type \u2018instant\u2019, if the disclosure includes the actual date, then use the date on which the event occurred. If the disclosure mentions that the event occurred in the month of May, then use the last day of the month, e.g. 5\/31. If the disclosure only mentions that it occurred in the second quarter, then use the second quarter reporting end date of 6\/30. For an element with period type \u2018duration\u2019, if the disclosure mentions that the event occurred in the month of May, then use the duration period 5\/1 to 5\/31. If the disclosure only mentions that it occurred in the second quarter, then use the second quarter period of 4\/1 to 6\/30.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.19.1\"><strong>Question E.19.1<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What context period should be used for a duration element when the actual date is specified (e.g., &#8220;on Sep 14, 2012&#8221;)?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0A duration period may use any period that EDGAR validation will allow and whose end date reflects the specified date.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.20\"><strong>Question E.20<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0EDGAR Filer Manual rule 6.8.6 prohibits the use of company-specific or period-specific information in element names. Does this apply to all item types?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0EFM 6.8.6 applies to elements with item types other than \u2018domainItemType\u2019. Elements with other item types, including (but not limited to) monetary, percent, integer, shares, per share, string, or text block item types, should not include company-specific or period-specific information in the element name. Domain members may include company-specific or period-specific information in the element name.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">For example, filers should not create a monetary element with the name &#8220;AcquisitionOfDefCo&#8221; or FourthQuarterAdjustment&#8221;. However, they may create a domain member with the name &#8220;AbcSegmentMember&#8221;.<\/span><\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.21\"><strong>Question E.21<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0How are units (units of measure) used in an interactive data filing?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Every amount in an XBRL submission is associated with an XBRL item type, an underlying data type, and a unit (short for \u201cunit of measure\u201d), determined by the element selected and the nature of the amount being reported. Common XBRL item types include Monetary, Shares, Decimal, Integer and Pure. These may be further distinguished as to data type, which could be the same as the item type or a specialization of it; for example, the Monetary data type allows any number to appear; the Non-Negative Monetary data type excludes negative amounts. The US GAAP taxonomy and SEC taxonomies mainly use data types defined in XBRL 2.1 itself or in the standard Data Type Registry (DTR).<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">The XBRL item type and data type are still not enough in most cases to completely define an amount, and so XBRL 2.1 requires every amount to have a unit. In this way, XBRL item types, particularly Decimal or Integer item types, use units to further distinguish the nature of the amount. For example, the unit used for earnings per share amounts reported in US dollars is \u201cUSD per Share\u201d. Specialized units also are used to report nonmonetary measurements. For example, amounts may be reported in units of measure such as megawatts, millions of barrels, millions of bushels, or employees.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">The Pure XBRL item type is used with elements that describe percentages, rates, and ratios, and typically use the Pure unit. However, the staff has observed some filings to date in which the Pure unit has been used for other item types. The staff recommends as a best practice and to promote consistency and comparability that the Pure unit only be used with the Pure XBRL item type, and not with other item types. Additionally, the staff recommends that the Pure unit be used only for amounts which are percentages, rates or ratios.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">Under EFM 6.5.35, if a standard numeric data type registry namespace is in the DTS of an instance, then the unit used for an item type must be the unit listed in the registry for that item type. Currently, the standard units registry is not yet available. The Staff expects that it eventually will be included in a future version of the DEI (Document and Entity Information) Taxonomy and notice will be provided of its inclusion. Until it becomes available, the staff recommends as a best practice that filers select the unit type that most closely fits with the item and data type. The following table gives examples of commonly used XBRL item types, data types and corresponding units:<\/span><\/p><p>\u00a0<\/p><table width=\"623\"><tbody><tr><td width=\"94\"><p><span style=\"color: #000000;\"><strong>XBRL Item Type<\/strong><\/span><\/p><\/td><td width=\"113\"><p><span style=\"color: #000000;\"><strong>Data Type<\/strong><\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\"><strong>Typical Element<\/strong><\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\"><strong>Typical Unit<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"94\"><p><span style=\"color: #000000;\">Monetary<\/span><\/p><\/td><td width=\"113\"><p><span style=\"color: #000000;\">Monetary<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Assets, Net<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">USD<\/span><\/p><\/td><\/tr><tr><td width=\"94\">\u00a0<\/td><td width=\"113\">\u00a0<\/td><td width=\"189\">\u00a0<\/td><td width=\"227\"><p><span style=\"color: #000000;\">GBP<\/span><\/p><\/td><\/tr><tr><td width=\"94\">\u00a0<\/td><td width=\"113\"><p><span style=\"color: #000000;\">Non-Negative Monetary<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Exchange Fee<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">USD<\/span><\/p><\/td><\/tr><tr><td width=\"94\"><p><span style=\"color: #000000;\">Shares<\/span><\/p><\/td><td width=\"113\"><p><span style=\"color: #000000;\">Shares<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Common Shares Outstanding<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">Share<\/span><\/p><\/td><\/tr><tr><td width=\"94\"><p><span style=\"color: #000000;\">Pure<\/span><\/p><\/td><td width=\"113\"><p><span style=\"color: #000000;\">Percent<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Debt Instrument Interest Rate, Stated Percentage<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">Pure<\/span><\/p><\/td><\/tr><tr><td width=\"94\">\u00a0<\/td><td width=\"113\"><p><span style=\"color: #000000;\">Pure<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Entity Listing, Depository Receipt Ratio<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">Pure<\/span><\/p><\/td><\/tr><tr><td width=\"94\">\u00a0<\/td><td width=\"113\"><p><span style=\"color: #000000;\">Non-Negative Pure4<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Net Expenses over Assets<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">Pure<\/span><\/p><\/td><\/tr><tr><td width=\"94\">\u00a0<\/td><td width=\"113\"><p><span style=\"color: #000000;\">Pure<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Derivative, Forward Exchange Rate<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">USD per GBP<\/span><\/p><\/td><\/tr><tr><td width=\"94\"><p><span style=\"color: #000000;\">Decimal<\/span><\/p><\/td><td width=\"113\"><p><span style=\"color: #000000;\">Decimal<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Derivative Nonmonetary Notional Amount<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">Bushels, tons, or other notional units as stated in the derivative contract<\/span><\/p><\/td><\/tr><tr><td width=\"94\">\u00a0<\/td><td width=\"113\"><p><span style=\"color: #000000;\">Per Share<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Earnings Per Share, Basic<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">USD per Share<\/span><\/p><\/td><\/tr><tr><td width=\"94\">\u00a0<\/td><td width=\"113\">\u00a0<\/td><td width=\"189\">\u00a0<\/td><td width=\"227\"><p><span style=\"color: #000000;\">GBP per Share<\/span><\/p><\/td><\/tr><tr><td width=\"94\">\u00a0<\/td><td width=\"113\"><p><span style=\"color: #000000;\">Volume<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Proved Oil Reserves<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">Millions of Barrels (MMbbl)<\/span><\/p><\/td><\/tr><tr><td width=\"94\">\u00a0<\/td><td width=\"113\"><p><span style=\"color: #000000;\">Area<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Area Of Land Held For Developmen<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">Acre<\/span><\/p><\/td><\/tr><tr><td width=\"94\"><p><span style=\"color: #000000;\">Integer<\/span><\/p><\/td><td width=\"113\"><p><span style=\"color: #000000;\">Integer<\/span><\/p><\/td><td width=\"189\"><p><span style=\"color: #000000;\">Number Of Employees<\/span><\/p><\/td><td width=\"227\"><p><span style=\"color: #000000;\">Employee<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.22\"><strong>Question E.22<\/strong><\/a><\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Can an interactive data submission contain more than one EX-101.* attachment of any given type?<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0It depends on the type. Only one EX-101.INS (instance) is required and allowed. However, as EFM 6.3.10 implies, the submission must contain at least one EX-101.SCH (schema) but may contain more. In general there can be any number of EX-101.PRE (presentation linkbase), EX-101.LAB (label linkbase), or EX-101.DEF (definition linkbase) attachments (EFM 6.8.2). The total number of attachments is subject to any overall limit on attachments imposed by EDGARLink Online.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">Additionally, EFM 6.7.4 and 6.7.5 together allow the target name space attribute of each schema to have formats such as \u201chttp:\/\/example.com\/20111231\u201d, \u201chttp:\/\/x.example.com\/20111231\u201d, \u201chttp:\/\/y.example.com\/20111231\u201d and so forth.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.23\"><strong>Question E.23<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Can a company extension schema contain unused elements and their linkbase relationships (e.g., presentation, calculation)?<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes. Unused elements (i.e., those elements which do not appear in the current instance document exhibit) and their linkbase relationships may be contained in the extension schema to simplify maintenance and reuse (e.g., between quarterly and annual reports) of the extension schema. However, it is recommended that unused elements and relationships that serve no further purpose be removed from the extension schema.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.24\"><strong>Question E.24<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Are calculations allowable for elements with amounts outside of a \u201crequired context\u201d?<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes, calculations that meet the EDGAR Filer Manual rules for calculation linkbases (see EDGAR Filer Manual rules in sections 6.14 and 6.15) outside of a required context are optional. Note that required contexts are distinguished by having no xbrli:segment elements (axes and dimension members).<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.25\"><strong>Question E.25<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0My FORM 10-K includes line items in the original HTML\/ASCII that come under the EDGAR Filer Manual calculation rules in sections 6.14 and 6.15. However, those same line items are presented in both a primary statement and a footnote. Furthermore, the footnote contains additional line items which are not found in the primary statement. Will a single set of calculation linkbase relationships which include all required line items in the footnote satisfy the EDGAR calculations requirements for both sets of items?<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Every required calculation relationship applies to the entire filing. An element should be the source (e.g., current liabilities) of only one calculation relationship for any one target (e.g., current portion of long-term debt), without regard for base set (e.g., balance sheet, debt footnote). See EDGAR Filer Manual section 6.15 for additional detail.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.26\"><strong>Question E.26<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0If a company changes its name or ticker symbol, should the XBRL file names and recommended namespace prefix be changed to conform to the new name?<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0EDGAR Filer Manual rule 6.3.3 indicates that document names should begin with the registrant\u2019s ticker symbol or some other mnemonic abbreviation and should be the same as that used for the instance in the same submission. Although not a requirement, if a company subsequently changes names or ticker symbols, we suggest the file names and recommended namespace prefix mnemonic abbreviation be updated to reflect the change.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.E.27\"><strong>Question E.27<\/strong><\/a>\u00a0<strong>(New 01\/26\/2016)<\/strong><\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What are the conditions for determining when a calculation relationship is required?<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0The Commission&#8217;s rules require filers to include calculation relationships for certain contributing line item elements for financial statements and related footnotes. Required calculation relationships in XBRL company taxonomies provide key information that shows the relationships among elements and their corresponding numeric facts, and how they add and subtract to each other. In addition, required calculation relationships enhance data quality by:<\/span><\/p><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">Providing vital context for interpretation of custom element extensions;<\/span><\/li><li><span style=\"color: #000000;\">Supporting company data continuity; and<\/span><\/li><li><span style=\"color: #000000;\">Reducing the number of incorrect amounts.<\/span><\/li><\/ul><p><span style=\"color: #000000;\">The EDGAR Filer Manual (Volume 2), Chapter 6, Sections 6.14 and 6.15 set out specific calculation relationship requirements, including certain examples and exceptions. Section 6.14 addresses the syntax restrictions of calculation relationships. Section 6.15 addresses the content of calculation relationships.<\/span><\/p><p><span style=\"color: #000000;\"><strong>Item 6.15.2: Determining when calculation relationships are required<\/strong><\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\">Item 6.15.2 of the EDGAR Filer Manual states:<\/span><\/p><p><span style=\"color: #000000;\"><em>&#8220;If the original HTML\/ASCII document shows two or more line items along with their net or total during or at the end of the Required Context period, and the instance contains corresponding numeric facts, then the DTS of the instance must have an effective calculation relationship from the total element to each of the contributing line items.&#8221;<\/em><\/span><\/p><p><span style=\"color: #000000;\">If a line item satisfies all of the following five conditions, as set out by Item 6.15.2, the line item requires a calculation relationship:<\/span><\/p><p><span style=\"color: #000000;\"><strong><u>Condition 1.<\/u><\/strong>\u00a0In the HTML\/ASCII filing, does the line item appear in either the financial statements or the footnotes? (Note: If the line item appears in both the financial statements and the footnotes, you should answer &#8220;yes&#8221; to this question.)<\/span><\/p><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">If\u00a0<strong>yes<\/strong>, continue to Condition 2.<\/span><\/li><li><span style=\"color: #000000;\">If\u00a0<strong>no<\/strong>, then no calculation relationship is required for that line item.<\/span><\/li><\/ul><p><span style=\"color: #000000;\"><strong><u>\u00a0<\/u><\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong><u>Condition 2.<\/u><\/strong>\u00a0In the HTML\/ASCII filing, does the line item appear with at least one other line item and the net or total of those line items?<\/span><\/p><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">If\u00a0<strong>yes<\/strong>, continue to Condition 3.<\/span><\/li><li><span style=\"color: #000000;\">If\u00a0<strong>no<\/strong>, then no calculation relationship is required for that line item.<\/span><\/li><\/ul><p><span style=\"color: #000000;\"><strong><u>\u00a0<\/u><\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong><u>Condition 3.<\/u><\/strong>\u00a0Does the line item belong to a context period that represents a duration or an instant that has the same end date as the Required Context (See Item 6.5.19 of the EDGAR Filer Manual)?<\/span><\/p><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">If\u00a0<strong>yes<\/strong>, continue to Condition 4.<\/span><\/li><li><span style=\"color: #000000;\">If\u00a0<strong>no<\/strong>, then no calculation relationship is required for that line item.<\/span><\/li><\/ul><p><span style=\"color: #000000;\"><strong><u>\u00a0<\/u><\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong><u>Condition 4.<\/u><\/strong>\u00a0Does the line item have a corresponding numeric fact in the instance document?<\/span><\/p><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">If\u00a0<strong>yes<\/strong>, continue to condition 5<\/span><\/li><li><span style=\"color: #000000;\">If\u00a0<strong>no<\/strong>, then no calculation relationship is required for that line item.<\/span><\/li><\/ul><p><span style=\"color: #000000;\"><strong><u>\u00a0<\/u><\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong><u>Condition 5.<\/u><\/strong>\u00a0Does the numeric fact appear in the instance document with at least one other numeric fact other than the net or total?<\/span><\/p><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">If\u00a0<strong>yes<\/strong>, then an effective calculation relationship is required from the total element to the contributing line item.<\/span><\/li><li><span style=\"color: #000000;\">If\u00a0<strong>no<\/strong>, then no calculation relationship is required for that line item.<\/span><\/li><\/ul><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Additional questions related to Item 6.15.2:<\/strong><\/span><\/p><ol><li><span style=\"color: #000000;\"><strong>If some of the contributing line items do not contain corresponding numeric facts, but other contributing line items do, is a calculation relationship still required?<\/strong><\/span><\/li><\/ol><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">Any line item that meets all the 6.15.2 conditions requires a calculation relationship.<\/span><\/li><\/ul><ol start=\"2\"><li><span style=\"color: #000000;\"><strong>If a line item is in a context period before the Required Context, is a calculation relationship required for that line item?<\/strong><\/span><\/li><\/ol><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">A line item in a context period before the Required Context does not require a calculation relationship because the line item does not have the same end date as the Required Context (see Item 6.5.19 of the EDGAR Filer Manual).<\/span><\/li><\/ul><ol start=\"3\"><li><span style=\"color: #000000;\"><strong>If line items have corresponding numeric facts in different contexts, is a calculation relationship required between them?<\/strong><\/span><\/li><\/ol><p>\u00a0<\/p><ul><li><span style=\"color: #000000;\">Although permitted, line items with corresponding numeric facts in different contexts do not require a calculation relationship.<\/span><\/li><\/ul><ol><li><span style=\"color: #000000;\"><strong> Detail Tagging<\/strong><\/span><\/li><\/ol><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.F.1\"><strong>Question F.1<\/strong><\/a>\u00a0(formerly Question 37)<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Should the formatting of footnote tables that result from tagging at Level 4 match exactly the format presented in the original HTML\/ASCII version?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0No. There is no requirement that facts tagged at Level 4 render in such a way to ma tch the formatting in the original HTML\/ASCII version. For example, the axes may be reversed in the XBRL table structure from that presented in the original HTML\/ASCII version and there may be blank cells in the XBRL table structure where &#8220;-&#8221; appear in the HTML\/ASCII version. In addition, facts appearing within the same footnote in the original HTML\/ASCII version may be incorporated into the table structure for tagging purposes.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.F.2\"><strong>Question F.2<\/strong><\/a>\u00a0(formerly Question 40)<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Does the EDGAR Filer Manual rule 6.8.6 limiting the use of company-specific elements apply to tagging at Levels 2, 3, and 4?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes, but see the clarification in Question E.20.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.F.3\"><strong>Question F.3<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0Outside of the primary financial statements, is superscripted text at the bottom of a footnote table allowed to be included in an XBRL footnote link element?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Yes, including the superscripted text at the bottom of a footnote table in an XBRL footnote link is optional. Note that any required amounts in superscripted text must be separately tagged as part of Level 4 tagging requirements.<\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.F.4\"><strong>Question F.4<\/strong><\/a>\u00a0<strong>(02\/05\/2013)<\/strong><\/span><\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0When tagging a narrative disclosure using &#8220;no&#8221; or &#8220;none&#8221; such as &#8220;There were no impairment losses for the years ended December 31, 2012, 2011, and 2010, respectively should a value of zero be tagged for each of the disclosed periods\u201d?<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0In general, if you can replace the word &#8220;no&#8221; or &#8220;none&#8221; with a zero and it does not change the meaning of the sentence, then you are disclosing an amount. From Compliance and Disclosure Interpretations &#8211; Regulation S-T Question 130.04 &#8211; \u201cEach amount, whether expressed numerically or textually, must be tagged separately under Rule 405(d)(4)(i). This guidance also applies to tagging each amount within the financial statement schedules under Rule 405(e)(2)(i) of Regulation S-T. Each tagged amount must be mapped to the applicable monetary, decimal, percent, integer or shares data type element\u201d.<\/span><\/p><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><ol><li><span style=\"color: #000000;\"><strong> Element Selection<\/strong><\/span><\/li><\/ol><p><span style=\"color: #000000;\"><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/structureddata\/FAQs#Q.G.1\"><strong>Question G.1<\/strong><\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>Q:<\/strong>\u00a0What are some considerations for selecting the most appropriate element from the U.S. GAAP Taxonomy among similar elements?<\/span><\/p><p><span style=\"color: #000000;\"><strong>A:<\/strong>\u00a0Selection of an appropriate element (or \u201ctag\u201d) from the U.S. GAAP Taxonomy for a particular disclosure facilitates the effective communication, access, and disclosures analysis by the Commission, investors, analysts, filers, data aggregators, and other market participants. Before you file, be sure to consider whether the taxonomy element you have selected is appropriate for the specific disclosure. Filers should carefully review the accounting standards disclosure requirements and the U.S. GAAP Taxonomy before mapping their disclosures to the U.S. GAAP Taxonomy elements. In particular, filers should review the element definitions in the U.S. GAAP Taxonomy and verify that they are consistent with the reported disclosure.<\/span><\/p><p><span style=\"color: #000000;\">The tables below provide some illustrative examples where reviewing element definitions provided within the U.S. GAAP Taxonomy can help filers determine to which taxonomy element they should map their disclosure.<\/span><\/p><p>\u00a0<\/p><table width=\"604\"><tbody><tr><td width=\"113\"><p><span style=\"color: #000000;\"><strong>Disclosure<\/strong><\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Property, Plant, and Equipment (PPE), Net (balance sheet)<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\">\u00a0<\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Should Be<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>Should Not Be<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Element<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">us-gaap: Property Plant And EquipmentNet<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">us-gaap: Assets Noncurrent<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Definition<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">Amount after accumulated depreciation, depletion and amortization of physical assets used in the normal conduct of business to produce goods and services and not intended for resale. Examples include, but are not limited to, land, buildings, machinery and equipment, office equipment, and furniture and fixtures.<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">Sum of the carrying amounts as of the balance sheet date of\u00a0<strong>all assets<\/strong>\u00a0that are expected to be realized in cash, sold or consumed after one year or beyond the normal operating cycle, if longer.<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Explanation<\/span><\/p><\/td><td width=\"208\">\u00a0<\/td><td width=\"283\"><p><span style=\"color: #000000;\">This element represents total long-term assets that\u00a0<strong>may include assets other than PPE<\/strong>\u00a0and provides no accommodation for the specific concept of accumulated depreciation, depletion and amortization. Because the disclosure consists only of PPE, Net, us-gaap:AssetsNoncurrent element is not appropriate.<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p>\u00a0<\/p><table width=\"604\"><tbody><tr><td width=\"113\"><p><span style=\"color: #000000;\"><strong>Disclosure<\/strong><\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Total operating expenses, consisting of general expenses. No revenue recorded. (income statement)<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\">\u00a0<\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Should Be<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>Should Not Be<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Element<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">us-gaap: Operating Expenses<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">us-gaap: Operating Costs And Expenses<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Definition<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">Generally recurring costs associated with normal operations except for the portion of these expenses which can be clearly related to production and included in cost of sales or services.\u00a0<strong>Includes<\/strong>\u00a0selling,\u00a0<strong>general<\/strong>\u00a0and administrative expenses.<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">Generally recurring costs associated with normal operations except for the portion of these expenses which can be clearly related to production and included in cost of sales or services.\u00a0<strong>Excludes<\/strong>\u00a0selling,\u00a0<strong>general<\/strong>\u00a0and administrative expense.<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Explanation<\/span><\/p><\/td><td width=\"208\">\u00a0<\/td><td width=\"283\"><p><span style=\"color: #000000;\">This element represents a total of generally recurring costs associated with normal operations such as professional and contract services and legal fees, but\u00a0<strong>excludes<\/strong>\u00a0selling,\u00a0<strong>general<\/strong>, and administrative expenses. Because the disclosure includes general expenses, the us-gaap: Operating Costs And Expenses element is not appropriate.<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p>\u00a0<\/p><table width=\"604\"><tbody><tr><td width=\"113\"><p><span style=\"color: #000000;\"><strong>Disclosure<\/strong><\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Total provision for income taxes (includes both current and deferred income tax) (income tax footnote)<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\">\u00a0<\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Should Be<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>Should Not Be<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Element<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">us-gaap:IncomeTaxExpenseBenefit<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">us-gaap:CurrentIncomeTaxExpenseBenefit<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Definition<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">Amount of\u00a0<strong>current<\/strong>\u00a0income tax expense (benefit)\u00a0<strong>and deferred<\/strong>\u00a0income tax expense (benefit) pertaining to continuing operations.<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">Amount of current income tax expense (benefit) pertaining to taxable income (loss) from continuing operations.<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Explanation<\/span><\/p><\/td><td width=\"208\">\u00a0<\/td><td width=\"283\"><p><span style=\"color: #000000;\">This element includes\u00a0<strong>only current<\/strong>\u00a0income tax expense. Because the disclosure includes both current and deferred income tax expenses the us-gaap:CurrentIncomeTaxExpenseBenefit element is not appropriate.<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p>\u00a0<\/p><table width=\"604\"><tbody><tr><td width=\"113\"><p><span style=\"color: #000000;\"><strong>Disclosure<\/strong><\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Net cash provided by investing activities-discontinued operations (cashflow statement)<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\">\u00a0<\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Should Be<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>Should Not Be<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Element<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">us-gaap:CashProvidedByUsedInInvestingActivitiesDiscontinuedOperations<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">us-gaap:ProceedsFromPaymentsForOtherFinancingActivities<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Definition<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">Amount of cash inflow (outflow) of\u00a0<strong>investing<\/strong>\u00a0activities of discontinued operations. Investing activity cash flows include making and collecting loans and acquiring and disposing of debt or equity instruments and property, plant, and equipment and other productive assets.<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">Amount of cash inflow (outflow) from\u00a0<strong>financing activities<\/strong>\u00a0classified as other.<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Explanation<\/span><\/p><\/td><td width=\"208\">\u00a0<\/td><td width=\"283\"><p><span style=\"color: #000000;\">This element represents proceeds and payments from other\u00a0<strong>financing<\/strong>\u00a0activities. Because this disclosure is about investing activities related to discontinued operations and not financing activities, the us-gaap:ProceedsFromPaymentsForOtherFinancingActivities element is not appropriate.<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p>\u00a0<\/p><table width=\"604\"><tbody><tr><td width=\"113\"><p><span style=\"color: #000000;\"><strong>Disclosure<\/strong><\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Prepaid rent expense classified as a current asset (balance sheet)<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\">\u00a0<\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Should Be<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>Should Not Be<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Element<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">us-gaap:PrepaidRent<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">us-gaap:PrepaidExpenseNoncurrent<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Definition<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">Amount of asset related to consideration paid in advance for\u00a0<strong>rent<\/strong>\u00a0that provides economic benefits\u00a0<strong>within<\/strong>\u00a0a future period of\u00a0<strong>one year<\/strong>.<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">Sum of the carrying amounts as of the balance sheet date of amounts paid in advance for expenses which will be charged against earnings\u00a0<strong>in periods after one year<\/strong>\u00a0or beyond the operating cycle, if longer.<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Explanation<\/span><\/p><\/td><td width=\"208\">\u00a0<\/td><td width=\"283\"><p><span style=\"color: #000000;\">This element represents\u00a0<strong>a sum of non-current<\/strong>\u00a0prepaid expenses. Because the disclosure only includes a prepaid rent expense, classified as a current asset, the us-gaap:PrepaidExpenseNoncurrent element is not appropriate due to its \u2018non-current\u2019 nature.<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p>\u00a0<\/p><table width=\"604\"><tbody><tr><td width=\"113\"><p><span style=\"color: #000000;\"><strong>Disclosure<\/strong><\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Net cash used in operating activities (cashflow statement)<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\">\u00a0<\/td><td width=\"208\"><p><span style=\"color: #000000;\"><strong>Should Be<\/strong><\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\"><strong>Should Not Be<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Element<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">us-gaap:NetCashProvidedByUsedInOperatingActivities<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">us-gaap:NetCashProvidedByUsedInContinuingOperations<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Taxonomy Definition<\/span><\/p><\/td><td width=\"208\"><p><span style=\"color: #000000;\">Amount of cash inflow (outflow) from\u00a0<strong>operating<\/strong>\u00a0activities. Operating activity cash flows include transactions, adjustments, and changes in value not defined as investing or financing activities.<\/span><\/p><\/td><td width=\"283\"><p><span style=\"color: #000000;\">The increase (decrease) in cash associated with the entity&#8217;s continuing\u00a0<strong>operating, investing, and financing activities<\/strong>.<\/span><\/p><\/td><\/tr><tr><td width=\"113\"><p><span style=\"color: #000000;\">Explanation<\/span><\/p><\/td><td width=\"208\">\u00a0<\/td><td width=\"283\"><p><span style=\"color: #000000;\">This element represents a total of net cash provided by (used in)\u00a0<strong>all three activities: operating, investing, and financing<\/strong>\u00a0activities from continuing operations. Because the disclosure includes only operating activities, the us-gaap:NetCashProvidedByUsedInContinuingOperations is not appropriate.<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p>\u00a0<\/p><table width=\"607\"><tbody><tr><td width=\"104\"><p><span style=\"color: #000000;\"><strong>Disclosure<\/strong><\/span><\/p><\/td><td width=\"217\"><p><span style=\"color: #000000;\"><strong>Loss from operations. No discontinued operations during the year. (income statement)<\/strong><\/span><\/p><\/td><td width=\"286\"><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"104\">\u00a0<\/td><td width=\"217\"><p><span style=\"color: #000000;\"><strong>Should Be\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/strong><\/span><\/p><\/td><td width=\"286\"><p><span style=\"color: #000000;\"><strong>Should Not Be<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"104\"><p><span style=\"color: #000000;\">Taxonomy Element<\/span><\/p><\/td><td width=\"217\"><p><span style=\"color: #000000;\">us-gaap:Operating IncomeLoss<\/span><\/p><\/td><td width=\"286\"><p><span style=\"color: #000000;\">us-gaap:IncomeLossFromContinuingOperations<\/span><\/p><\/td><\/tr><tr><td width=\"104\"><p><span style=\"color: #000000;\">Taxonomy Definition<\/span><\/p><\/td><td width=\"217\"><p><span style=\"color: #000000;\">The net result for the period of deducting operating expenses from operating revenues.<\/span><\/p><\/td><td width=\"286\"><p><span style=\"color: #000000;\">Amount after tax of income (loss) from continuing operations attributable to the parent.<\/span><\/p><\/td><\/tr><tr><td width=\"104\"><p><span style=\"color: #000000;\">Explanation<\/span><\/p><\/td><td width=\"217\">\u00a0<\/td><td width=\"286\"><p><span style=\"color: #000000;\">In this example, there were no discontinued operations. Therefore, using a tag, specifically assigned for income (loss) from continuing operations in the event of a discontinued operation is not appropriate as it incorrectly implies reporting of discontinued and continuing operations.<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p>\u00a0<\/p><table width=\"604\"><tbody><tr><td width=\"103\"><p><span style=\"color: #000000;\"><strong>Disclosure<\/strong><\/span><\/p><\/td><td width=\"217\"><p><span style=\"color: #000000;\"><strong>Net deferred tax liabilities (income tax footnote)<\/strong><\/span><\/p><\/td><td width=\"284\"><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"103\">\u00a0<\/td><td width=\"217\"><p><span style=\"color: #000000;\"><strong>Should Be<\/strong><\/span><\/p><\/td><td width=\"284\"><p><span style=\"color: #000000;\"><strong>Should Not Be<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"103\"><p><span style=\"color: #000000;\">Taxonomy Element<\/span><\/p><\/td><td width=\"217\"><p><span style=\"color: #000000;\">us-gaap:DeferredTaxLiabilities<\/span><\/p><\/td><td width=\"284\"><p><span style=\"color: #000000;\">us-gaap:DeferredTaxAssetsLiabilitiesNet<\/span><\/p><\/td><\/tr><tr><td width=\"103\"><p><span style=\"color: #000000;\">Taxonomy Definition<\/span><\/p><\/td><td width=\"217\"><p><span style=\"color: #000000;\">Amount, after deferred tax asset, of deferred tax\u00a0<strong>liability<\/strong>\u00a0attributable to taxable differences without jurisdictional netting.<\/span><\/p><\/td><td width=\"284\"><p><span style=\"color: #000000;\">Amount, after allocation of valuation allowances and deferred tax liability, of\u00a0<strong>deferred tax asset<\/strong>\u00a0attributable to deductible differences and carryforwards, without jurisdictional netting.<\/span><\/p><\/td><\/tr><tr><td width=\"103\"><p><span style=\"color: #000000;\">Explanation<\/span><\/p><\/td><td width=\"217\">\u00a0<\/td><td width=\"284\"><p><span style=\"color: #000000;\">This element represents net deferred tax\u00a0<strong>assets<\/strong>. Because this disclosure is about liabilities and not assets, the us-gaap:DeferredTaxAssetsLiabilitiesNet is not appropriate.<\/span><\/p><\/td><\/tr><\/tbody><\/table><p>\u00a0<\/p><p>\u00a0<\/p><p>\u00a0<\/p><p>\u00a0<\/p><p><span style=\"color: #000000;\"><strong>URL-6:<\/strong><a style=\"color: #000000;\" href=\"https:\/\/www.sec.gov\/info\/edgar\/specifications\/edgarfm-vol2-v53.pdf\">https:\/\/www.sec.gov\/info\/edgar\/specifications\/edgarfm-vol2-v53.pdf<\/a><\/span><\/p><p><span style=\"color: #000000;\"><strong>APPENDIX B. FREQUENTLY ASKED QUESTIONS<\/strong><\/span><\/p><p><span style=\"color: #000000;\">The Filer Support Branch in your subject matter division helps filers with general filing andtechnical information or assistance. You can reach Filer Support Staff during the hours of 9:00A.M. to 5:30 P.M. on business days. The phone number is (202) 551-8900. Many of thequestions that Filer Support staff answer daily involve similar issues. We have summarized themost frequently asked questions and their answers in this section. Please review this sectionbefore calling Filer Support. Filer Support voicemail will be available during off hours.<\/span><\/p><table width=\"642\"><tbody><tr><td width=\"160\"><p><span style=\"color: #000000;\"><strong>Questions<\/strong><\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\"><strong>Answers<\/strong><\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How do I reachthe EDGARFiling Website?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">You can reach this site by using the EDGAR Filing Website:https:\/\/www.edgarfiling.sec.gov. Please bookmark this site the next time youvisit it.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How do I reachthe EDGARFilerManagement website?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">You can reach this site by using the EDGAR Filer Management WebsiteURL, which is https:\/\/www.filermanagement.edgarfiling.sec.gov. Pleasebookmark this site the next time you visit it.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">Which web browser shall I use for EDGAR link Online?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">For EDGARLink Online, we recommend using a recent version of MicrosoftInternet Explorer or Google Chrome which is still supported by the vendor.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">Which web browser shall I use for other EDGARwebsite?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">For other EDGAR websites, we recommend that you use a recent version ofMicrosoft Internet Explorer or Google Chrome which is still supported bythe vendor.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">Can I use a webbrowser such as Safari to access EDGAR website?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">Safari does not perform consistently with EDGAR and so we do notrecommend the use of this browser.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">Why may filingagents have morethan one CIK?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">Filing agents may have several CIKs for accounting and managementpurposes. For example, a filing agent may use a different CIK for eachoperating office, each industry group, or for certain categories of filers onwhose behalf they make an SEC filing(s). However, the filing agent mustuse a separate and distinct CIK for any filing(s) they make on their ownbehalf.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">What happens if I submit a filing by mistake?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">This could be a very serious problem if the filing does not contain errors thatwould cause EDGAR to suspend the filing. Once EDGAR accepts a publicfiling, it is immediately disseminated. We cannot intercept a filing after itsacceptance and prevent its dissemination, nor can we retrieve the filing.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How quickly can I determine whether my filing was accepted?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">The quickest way for you to find out if your filing was accepted orsuspended is to use the EDGAR Filing Website. You can also read themessages EDGAR will send to your Internet e-mail address.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How do I usedigital signature?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">Digital signatures increase the privacy protection of information transmittedover the Internet.<\/span><\/p><p><span style=\"color: #000000;\">Note: EDGARLink Online does not currently support Digital Signatures.<\/span><\/p><p><span style=\"color: #000000;\">This support will be addressed in a future release.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How do I namemy attacheddocuments forfilings sent viathe EDGARFiling Website?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">All document file names must be upper or lower case and no longer than 32characters in length. The names must start with a letter (a-z) or a number (0-9) and may not contain spaces. File names may contain any number ofperiods (.), hyphens (-), and underscore (_) characters and must end with*.htm, *.txt, *.pdf, *.fil, *.jpg, *.gif, *.xsd, or *.xml extensions.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How do I checkthe status of asubmission?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">You can check the status of filings using the EDGAR Filing Website. Onceyou have logged into EDGAR and accessed the Company and SubmissionInformation Retrieval page, you can access submission information for yourCIK. You must provide the CCC for the Login CIK or the PrimaryFiler\/Filed-By CIK before you can access any submission information.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">Can I submit myfiling in PDFformat?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">You may submit the PDF version of your filing as an unofficial documentattachment to the assembled submission. EDGAR must receive all officialdocuments in either ASCII\/SGML format or HTML format (with optionalJPG or GIF Graphic support files) or the submission will be suspended.<\/span><\/p><p><span style=\"color: #000000;\">However, the following exceptions apply:<\/span><\/p><p><span style=\"color: #000000;\">&#8211; The PDF authentication documents that accompany the applicationsfor EDGAR access, update passphrase, convert paper only filer toelectronic filer, and access for new serial companies are consideredofficial documents.<\/span><\/p><p><span style=\"color: #000000;\">&#8211; An official PDF document is considered acceptable for the followingsubmission form types and their variants: 13H, 40-33, 497AD,40-17G, 40-17GCS, 40-24B2, MA, MA-I, NRSRO-UPD, NRSRO-CE, NRSRO-FR, NRSRO-WCLS, NRSRO-WREG, and X-17A-5.<\/span><\/p><p><span style=\"color: #000000;\">EDGAR will continue to allow ASCII and HTML as the primarydocument for submission form types 40-33, 40-33\/A, 497AD, 40-17G, 40-17G\/A, 40-17GCS, 40-17GCS\/A, 40-24B2, 40-24B2\/A, X-17A-5 and X-17A-5\/A.<\/span><\/p><p><span style=\"color: #000000;\">&#8211; An official PDF document is considered acceptable for the followingexhibits of submission form types DOS, 1-A, 1-K, 1-SA, 1-U, andtheir variants: EX1A-13 TST WTRS, EX1K-13 TST WTRS,EX1SA-13 TST WTRS, and EX1U-13 TST WTRS.<\/span><\/p><p><span style=\"color: #000000;\">&#8211; An official PDF document is considered acceptable for the followingRegulation Crowdfunding submission form types: C, C\/A, C-AR, C-AR\/A, C-TR, CFPORTAL, CFPORTAL\/A, and CFPORTAL-W.<\/span><\/p><p><span style=\"color: #000000;\">&#8211; An official PDF document is considered acceptable for exhibitsATS-N EX-1 SCHD A BD, ATS-N EX-2 SCHD B BD, ATS-N EX-3 REDLINE, ATS-N EX-4 AGG STATS, and ATS-N EX-5 CATGMTRC for Form ATS-N.<\/span><\/p><p><span style=\"color: #000000;\">In addition, official documents for these exhibits are accepted in HTML andASCII formats.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How do I view anassembledsubmission orindividualdocument prior totransmitting it tothe SEC?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">You may view an individual document by selecting \u201cView Document\u201d onthe Documents page of the EDGARLink Online submission. We recognize aneed for filers to view or print a submission in its entirety prior totransmission, but given the variety of document formats (ASCII, HTML,JPG, GIF, PDF, etc.) that are supported, this functionality is not likely to beincorporated into EDGARLink Online.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How do I namemodules\/segments with theEDGARLinkOnline software?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">You should submit modules\/segments (via the Modules\/Segmentssubmission) using uppercase letters and numerals. You should subsequentlyreference these modules and segments in the same uppercase format asinitially submitted. A module\/segment can be used either as a Type 1reference within a document or as a Type 2 reference listed on theModules\/Segments page of the EDGARLink Online submissions.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">Why does mybrowserconnection failduring large filetransfers to theFWS?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">The browser may not allocate enough cache for the current transmission.You may need to make more cache available to the browser (therecommended minimum is 20 MB) before transmitting large filings toEDGAR.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">Can I downloadCopy ReturnCopies more thanonce?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">Return copies are no longer available for download.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How will I knowif you havechanged theEDGARLinkOnline softwareor the FilerManual?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">The EDGAR Filing Website will notify you of upgrades to the software. Wewill post a current version of the Filer Manual on the SEC\u2019s Public Website(<em>https:\/\/www.sec.gov\/info\/edgar.shtml<\/em>). Because we provide the updatedFiler Manual in electronic format on the website, you can download thecomplete document and print the entire manual or specific chapters. TheFiler Manual is also available for Web site viewing and printing in theCommission&#8217;s Public Reference Room, 100 F Street NE., Washington, DC20549, on official business days between the hours of 10:00 a.m. and 3:00p.m.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">Where do I findthe Form ID?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">The current version of Form ID is available on the EDGAR FilerManagement Website, and can be accessed at:<a style=\"color: #000000;\" href=\"https:\/\/www.filermanagement.edgarfiling.sec.gov\/filermgmt\/selectFormId.html\"><em>https:\/\/www.filermanagement.edgarfiling.sec.gov\/filermgmt\/selectFormId.html<\/em><\/a><\/span><\/p><p><span style=\"color: #000000;\">You must submit Form ID applications electronically as the SEC does notaccept these applications in paper format.<\/span><\/p><p><span style=\"color: #000000;\">To apply for EDGAR access, use the EDGAR Filer Management Website<\/span><\/p><p><span style=\"color: #000000;\">URL: <em>https:\/\/www.filermanagement.edgarfiling.sec.gov<\/em>.<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">Why dostrikeouts appearin my documenton the SEC\u2019sPublic Website?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">This is a browser issue and only appears in documents viewed using theInternet Explorer browser. Make sure you are viewing the correct format ofthe document submitted. The HTML filter used to display filings submittedin html will interpret the internal stub tag &lt;s&gt; as the html strikeout code ifthe tag appears within approximately 30 lines from the top of the document.<\/span><\/p><p><span style=\"color: #000000;\">For suggestions contact Filer Technical Support(202-551-8900).<\/span><\/p><\/td><\/tr><tr><td width=\"160\"><p><span style=\"color: #000000;\">How do I accessthe EDGARQuick ReferenceGuides from theEDGAR FilingWebsite?<\/span><\/p><\/td><td width=\"482\"><p><span style=\"color: #000000;\">Navigate to the Frequently Asked Questions screen on the EDGAR FilingWebsite, and click the \u201cEDGAR Quick Reference Guides\u201d hyperlinkdisplayed under \u201cOther Filer Management FAQ Topics.\u201d The followingEDGAR Quick Reference Guides will be displayed as hyperlinks:<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 Authentication Document \u2014 Save as a PDF File in Adobe Acrobat<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 Authentication Document \u2014 Save as a PDF File in Adobe Reader<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 Browser Quick Reference Guide<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 Filings \u2014 Attaching and Submitting<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 Form 13F \u2014 Create a 13F XML Information Table using Excel 2010 or 2007<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 Form ID \u2014 How to Obtain EDGAR Access Codes to Access EDGAR<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 HTML \u2014 Creating Simple HTML Files<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 Organizational Chart \u2014 Save using ADOBE Acrobat<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 SC 13D Blank Form Instructions<\/span><\/p><p><span style=\"color: #000000;\">\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0 SC 13G Blank Form Instructions<\/span><\/p><\/td><\/tr><\/tbody><\/table><p><span style=\"color: #000000;\"><strong>\u00a0<\/strong><\/span><\/p>\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>FAQ UNITED STATES URL: 1 https:\/\/xbrl.us\/qa-sec-ixbrl\/ Q&amp;A \u2013 Inline XBRL Responses to these questions reflect the informal views of one [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"elementor_header_footer","meta":{"footnotes":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>FAQ - Pratham Consultants United States<\/title>\n<meta name=\"description\" content=\"FAQ - Pratham Consultants United States - For any question, please contact us.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/prathamconsult.com\/us\/faq\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"FAQ - Pratham Consultants United States\" \/>\n<meta property=\"og:description\" content=\"FAQ - Pratham Consultants United States - For any question, please contact us.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/prathamconsult.com\/us\/faq\/\" \/>\n<meta property=\"og:site_name\" content=\"Pratham Consultants United States\" \/>\n<meta property=\"article:modified_time\" content=\"2023-04-24T07:22:04+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"60 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/prathamconsult.com\/us\/faq\/\",\"url\":\"https:\/\/prathamconsult.com\/us\/faq\/\",\"name\":\"FAQ - Pratham Consultants United States\",\"isPartOf\":{\"@id\":\"https:\/\/prathamconsult.com\/us\/#website\"},\"datePublished\":\"2020-04-02T18:00:53+00:00\",\"dateModified\":\"2023-04-24T07:22:04+00:00\",\"description\":\"FAQ - Pratham Consultants United States - For any question, please contact us.\",\"breadcrumb\":{\"@id\":\"https:\/\/prathamconsult.com\/us\/faq\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/prathamconsult.com\/us\/faq\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/prathamconsult.com\/us\/faq\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/prathamconsult.com\/us\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"FAQ\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/prathamconsult.com\/us\/#website\",\"url\":\"https:\/\/prathamconsult.com\/us\/\",\"name\":\"Pratham Consultants United States\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/prathamconsult.com\/us\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/prathamconsult.com\/us\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/prathamconsult.com\/us\/#organization\",\"name\":\"Pratham Consultants United States\",\"url\":\"https:\/\/prathamconsult.com\/us\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/prathamconsult.com\/us\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/prathamconsult.com\/us\/wp-content\/uploads\/sites\/29\/2022\/04\/pratham-logo-png-120-80.png\",\"contentUrl\":\"https:\/\/prathamconsult.com\/us\/wp-content\/uploads\/sites\/29\/2022\/04\/pratham-logo-png-120-80.png\",\"width\":120,\"height\":40,\"caption\":\"Pratham Consultants United States\"},\"image\":{\"@id\":\"https:\/\/prathamconsult.com\/us\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"FAQ - Pratham Consultants United States","description":"FAQ - Pratham Consultants United States - For any question, please contact us.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/prathamconsult.com\/us\/faq\/","og_locale":"en_US","og_type":"article","og_title":"FAQ - Pratham Consultants United States","og_description":"FAQ - Pratham Consultants United States - For any question, please contact us.","og_url":"https:\/\/prathamconsult.com\/us\/faq\/","og_site_name":"Pratham Consultants United States","article_modified_time":"2023-04-24T07:22:04+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"60 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/prathamconsult.com\/us\/faq\/","url":"https:\/\/prathamconsult.com\/us\/faq\/","name":"FAQ - Pratham Consultants United States","isPartOf":{"@id":"https:\/\/prathamconsult.com\/us\/#website"},"datePublished":"2020-04-02T18:00:53+00:00","dateModified":"2023-04-24T07:22:04+00:00","description":"FAQ - Pratham Consultants United States - For any question, please contact us.","breadcrumb":{"@id":"https:\/\/prathamconsult.com\/us\/faq\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/prathamconsult.com\/us\/faq\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/prathamconsult.com\/us\/faq\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/prathamconsult.com\/us\/"},{"@type":"ListItem","position":2,"name":"FAQ"}]},{"@type":"WebSite","@id":"https:\/\/prathamconsult.com\/us\/#website","url":"https:\/\/prathamconsult.com\/us\/","name":"Pratham Consultants United States","description":"","publisher":{"@id":"https:\/\/prathamconsult.com\/us\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/prathamconsult.com\/us\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/prathamconsult.com\/us\/#organization","name":"Pratham Consultants United States","url":"https:\/\/prathamconsult.com\/us\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/prathamconsult.com\/us\/#\/schema\/logo\/image\/","url":"https:\/\/prathamconsult.com\/us\/wp-content\/uploads\/sites\/29\/2022\/04\/pratham-logo-png-120-80.png","contentUrl":"https:\/\/prathamconsult.com\/us\/wp-content\/uploads\/sites\/29\/2022\/04\/pratham-logo-png-120-80.png","width":120,"height":40,"caption":"Pratham Consultants United States"},"image":{"@id":"https:\/\/prathamconsult.com\/us\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/prathamconsult.com\/us\/wp-json\/wp\/v2\/pages\/1630"}],"collection":[{"href":"https:\/\/prathamconsult.com\/us\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/prathamconsult.com\/us\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/prathamconsult.com\/us\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prathamconsult.com\/us\/wp-json\/wp\/v2\/comments?post=1630"}],"version-history":[{"count":31,"href":"https:\/\/prathamconsult.com\/us\/wp-json\/wp\/v2\/pages\/1630\/revisions"}],"predecessor-version":[{"id":2362,"href":"https:\/\/prathamconsult.com\/us\/wp-json\/wp\/v2\/pages\/1630\/revisions\/2362"}],"wp:attachment":[{"href":"https:\/\/prathamconsult.com\/us\/wp-json\/wp\/v2\/media?parent=1630"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}