pdfdocument c#: Add a link to a pdf application SDK cloud windows wpf winforms class vol_II

April 2016

5-31

EDGAR Filer Manual (Volume II)

encapsulates these documents. Simply put, valid entries for the xlink:href and

schemaLocation attributes are file names (e.g. usgaapins-20040815_calc.xml) without

any additional path information. Remember that these file names are subject to the

EDGARLink Online file naming conventions that are described in Section 5.1.1 of

this document. Also note that references to company extension taxonomies require

the referenced taxonomy file(s) to be present in the submission package that is

submitted to EDGAR and should assume that all files reside at the same level, not

hierarchically.

•

Since XBRL documents must be contained in an official SEC submission, EDGAR will

suspend any submission that contains only XBRL documents.

•

XBRL instance, schema, and linkbase support documents must be attached to an EDGAR

submission using the EX-100.* document type. Specific XBRL document types are as

follows:

Document

Type

Description

File name

Extension

EX-100.INS

XBRL Instance document (Required)

*.xml

EX-100.SCH

XBRL Taxonomy Extension Schema document

*.xsd

EX-100.CAL

XBRL Taxonomy Extension Calculation Linkbase document *.xml

EX-100.DEF

XBRL Taxonomy Extension Definition Linkbase document

*.xml

EX-100.LAB

XBRL Taxonomy Extension Labels Linkbase document

*.xml

EX-100.PRE

XBRL Taxonomy Extension Presentation Linkbase

document

*.xml

EX-100.REF

XBRL Taxonomy Extension Reference Linkbase document

*.xml

Note: Although the Reference Linkbase file is a valid attachment type, at the

moment it is not used.

All EDGARLink Online submissions, except for CORRESP and BULK submissions, will

support the attachment of the Document Types listed above. If EDGAR detects a syntactical,

semantic, or content problem within an attached XBRL instance, schema, or linkbase document,

EDGAR will raise a general warning but will NOT automatically suspend the filing. EDGAR

will remove the unofficial XBRL document from the official live/test filing and will accept and

disseminate (if live) the remainder of the filing normally. If this situation occurs, a notification

will be sent to the filer containing a warning that all the XBRL documents were removed before

dissemination.

EDGARLink Online attaches an XBRL document to a filing in a similar manner as they attach

an ASCII/SGML or HTML document. Only *.xml or *.xsd files may be used for XBRL file

name extensions.

Below are some EDGAR-specific XBRL validations that will be performed, which will cause the

XBRL content to be stripped from the submission:

•

Warn the filer if the XBRL document contains any invalid or extended ASCII characters

(e.g. foreign language characters).

•

Warn the filer if an inconsistent instance document is attached.

Add a link to a pdf - insert, remove PDF links in C#.net, ASP.NET, MVC, Ajax, WinForms, WPF

Free C# example code is offered for users to edit PDF document hyperlink (url), like inserting and deleting

adding a link to a pdf; adding links to pdf

Add a link to a pdf - VB.NET PDF url edit library: insert, remove PDF links in vb.net, ASP.NET, MVC, Ajax, WinForms, WPF

Help to Insert a Hyperlink to Specified PDF Document Page

chrome pdf from link; pdf email link

EDGAR Filer Manual (Volume II)

5-32

April 2016

[An instance document must have a document type that begins with “EX-100.INS”,

must have a file extension of .xml and must include <xbrli:xbrl> tags

•

Warn the filer if an inconsistent schema document is attached.

[A schema document must have a document type that begins with “EX-100.SCH,”

must have a file extension of .xsd and must include a <schema> tag]

•

Warn the filer if an inconsistent reference linkbase document is attached.

[A reference linkbase document must have a document type that begins with

“EX-100.REF”, must have a file extension of .xml and must include <linkbase> and

<referenceLink> tags]

•

Warn the filer if an inconsistent label linkbase document is attached.

[A label linkbase document must have a document type that begins with

“EX-100.LAB”, must have a file extension of .xml and must include <linkbase> and

<labelLink> tags]

•

Warn the filer if an inconsistent presentation linkbase document is attached.

[A presentation linkbase document must have a document type that begins with

“EX-100.PRE”, must have a file extension of .xml and must include <linkbase> and

<presentationLink> tags]

•

Warn the filer if an inconsistent calculation linkbase document is attached.

[A calculation linkbase document must have a document type that begins with

“EX-100.CAL”, must have a file extension of .xml and must include <linkbase> and

<calculationLink> tags]

•

Warn the filer if an inconsistent definition linkbase document is attached.

[A definition linkbase document must have a document type that begins with

“EX-100.DEF”, must have a file extension of .xml and must include <linkbase> and

<definitionLink> tags]

The inconsistencies referred to above are not the same as inconsistencies reported by XBRL

validators. Inconsistencies discussed above refer to EDGARLink Online XBRL document

attachments that involve combinations of XBRL document type, file extension, and presence of a

particular XBRL tag. For example, a consistent XBRL instance document would have an

EX-100.INS document type, an .xml file extension for the attached document, and an <XBRL>

root element. An inconsistent instance document would have an EX-100.INS document type, an

.xsd file extension, and a <SCHEMA> root element. Such inconsistencies will generate warnings

and will result in the XBRL contents being stripped from the submission. This is not the same as

semantic inconsistencies discussed in the XBRL Specification. These inconsistencies refer to

validation of data in an XBRL instance against the semantics expressed in the taxonomies

supporting the instance and will not cause the XBRL contents to be stripped from the

submission.

5.2.4.4 EDGAR Module Processing with XBRL Taxonomy Extensions

EDGAR provides limited support for XBRL taxonomy extension documents as part of EDGAR

Module processing. EDGAR Type 1 Modules (partial documents) are not allowed in XBRL

format. Only EDGAR Type 2 Modules (complete documents) can be submitted in XBRL format.

RasterEdge .NET Document Imaging Trial Package Download Link.

Extract; C# Read: PDF Image Extract; C# Write: Insert text into PDF; C# Write: Add Image to PDF; C# Protect: Add Password to PDF; C#

add a link to a pdf file; adding hyperlinks to pdf

C# PDF Library SDK to view, edit, convert, process PDF file for C#

editing PDF document hyperlink (url) and quick navigation link in PDF bookmark. C#.NET: Edit PDF Metadata. PDF SDK for .NET allows you to read, add, edit, update

accessible links in pdf; add email link to pdf

April 2016

5-33

EDGAR Filer Manual (Volume II)

EDGAR currently supports up to 10 EDGAR Module files per CIK. These 10 Modules may be

used to store any combination of XBRL extension taxonomy files (schema and/or linkbase) and

may be managed by the filer using the EDGAR Filing Website. These taxonomy extension files

may be submitted before the official filing. Through the use of EDGAR Type 2 Module

references to these XBRL documents, EDGAR can assemble these large documents into the

filing without delaying the receipt of the entire filing.

As with any other kind of EDGAR Type 2 Module submission filed with EDGAR, filers may

include an XBRL document, or XBRL documents, as attachments to an EDGAR Module

submission. A master submission may reference the XBRL EDGAR Module in a normal Type 2

fashion by using the Documents page of EDGARLink Online.

5.2.4.5 Segment Functionality Not Supported for XBRL Documents

At this time, EDGAR does not support EDGAR segment processing of XBRL documents as

discussed in Section 5.3, “Preparing or Referencing Module and Segment Documents.”

XBRL segments can be used as described in the XBRL Specification. However, segments as

described in Section 5.3 of the EDGAR Filer Manual are not supported. In EDGARLink Online,

“segment” refers to parts of a filing that can be submitted ahead of time and later assembled in a

submission. It is this functionality that is not supported for XBRL documents. In the XBRL

Specification 2.1, “segment” also refers to an XBRL tag that is used to provide additional

information in cases where the entity identifier is insufficient. This use of segment is supported.

5.2.4.6 ASCII/SGML Functionality Not Supported Within XBRL Documents

EDGAR will NOT support any ASCII/SGML tags within the XBRL document text. These

documents will not be properly processed by EDGAR and may be removed.

EDGAR will reject any XBRL taxonomy extension that employs extended-ASCII characters

before acceptance.

5.2.4.7 Supported Versions of XBRL Standard Taxonomies

See Section 6.2, “Supported Versions of XBRL Standard Taxonomies,” for a listing of supported

schemas and refer to the SEC public web site

(http://www.sec.gov/info/edgar/edgartaxonomies.shtml) for a listing of standard taxonomies

supported for EX-100 attachments.

5.2.4.8 More XBRL Information

For more general information about XBRL:

http://www.xbrl.org/

For more information regarding the US GAAP Taxonomies:

http://www.xbrl.us/

For more information regarding the SEC’s XBRL initiatives and related rules:

http://www.sec.gov/spotlight/xbrl.shtml

For a complete set of supporting technical documents and specifications for XBRL:

C# PDF insert image Library: insert images into PDF in C#.net, ASP

C#.NET PDF SDK - Add Image to PDF Page in C#.NET. How to Insert & Add Image, Picture or Logo on PDF Page Using C#.NET. Add Image to PDF Page Using C#.NET.

add hyperlinks to pdf online; pdf link to email

VB.NET PDF insert image library: insert images into PDF in vb.net

VB.NET PDF - Add Image to PDF Page in VB.NET. Guide VB.NET Programmers How to Add Images in PDF Document Using XDoc.PDF SDK for VB.NET.

pdf links; change link in pdf

EDGAR Filer Manual (Volume II)

5-34

April 2016

http://specifications.xbrl.org

For a copy of the latest version of the Financial Reporting Taxonomy Architecture (FRTA) 1.0:

http://www.xbrl.org/guidance-xbrl-taxonomies

For a copy of the Financial Reporting Instance Standards (FRIS) 1.0:

http://www.xbrl.org/technical/guidance/FRIS-PWD-2004-11-14.htm

5.3 Preparing or Referencing Module and Segment Documents

Modules and segments are information that is stored on the non-public data storage area of

EDGAR. You may copy it into subsequent filings so you do not have to re-submit the data each

time. Both modules and segments can be part of a submission document or an entire document.

By submitting parts of a single filing to EDGAR separately, you can send them in from different

locations and under different CIKs. This is especially useful when lawyers and accountants in

addition to the company itself must assemble data. If the information in the module or segment is

part of a document, then once all of the parts have been submitted, you can include them in your

submission either by using tags to show where you want to place the data or, in the case of

modules/segments that are entire documents, referencing them in the submission.

Note: Both modules and segments must be prepared, transmitted to EDGAR, and accepted by

the system before they can be used in a filing.

There are two big differences between modules and segments:

1. Storage: Modules remain on the system until you ask for them to be removed. There

are limits to the number and size of modules you can store. You may store up to 10

modules for a single CIK. The maximum size of a module is one megabyte, but the

total for all modules for a single CIK is also one megabyte. There is no size limit on

segments, they are automatically removed by the system after six days, or after they

are used in a live filing.

2. Use of Access Codes: Modules require the filer to know the CIK and CCC of any

module that they wish to incorporate. Segments can be referenced by the master

segment filing without the CCC or CIK of the filer that transmitted the segment.

You must follow the rules outlined in the previous section of this document by constructing

modules and segments in either ASCII or HTML. In addition to those general document

construction requirements, there are additional requirements for these documents. For example,

if a transmitted Type 1 or 2 module/segment contains only white space (is blank), EDGAR will

suspend the entire submission. The following is a listing of tags that EDGAR accepts within

ASCII Type 1 modules/segments:

<PAGE>

<R>

All other allowable document tags can appear within the redlining tag nest.

</R>

<TABLE>

All other allowable document tags plus:

VB.NET PDF Password Library: add, remove, edit PDF file password

VB: Add Password to PDF with Permission Settings Applied. This VB.NET example shows how to add PDF file password with access permission setting.

add hyperlinks pdf file; add hyperlink pdf document

C# PDF Password Library: add, remove, edit PDF file password in C#

C# Sample Code: Add Password to PDF with Permission Settings Applied in C#.NET. This example shows how to add PDF file password with access permission setting.

add link to pdf acrobat; pdf link to attached file

April 2016

5-35

EDGAR Filer Manual (Volume II)

<S>

<C>

<FN>

</TABLE>

HTML modules/segments use HTML tags. All other SGML tags, except for <PAGE> and <R>

are not supported and may cause errors in HTML modules. For more information on HTML

documents, see Section 5.2.2, “HTML.”

5.3.1 Module and Segment Naming

You must send a uniquely named module/segment in a separate submission. You must name the

module/segment according to the following:

•

Must be no more than 15 characters long

•

Must begin with an uppercase letter (alpha character)

•

Characters after the beginning letter should be uppercase letters, numbers, underscores, or

hyphens (not periods)

•

Spaces are not allowed

•

EDGAR automatically converts the letters of your module name to uppercase

EDGAR treats the module/segment as your private information, and stores it on our database

according to your CIK. Another filer may reference your module/segment by providing your

CIK and in the case of modules, your CCC. This is covered in more detail in the examples in

Section 5.3.2.4, “Type 1 Module References,” and Section 5.3.2.6, “How to Reference a Type 1

Segment in a Submission Document.”

Caution: You may not include hyperlinks of any type in a module or segment; however,

modules and segments may be graphics (*.jpg or *.gif) or PDF documents.

5.3.2 Types of Modules and Segments

There are two types of modules and segments:

•

Type 1

•

Type 2

Type 1 modules or segments are portions of documents. Type 1 modules and segments are

positioned within a submission document using the <MODULE> and <SEGMENT> tags. A

Type 2 module or segment is one complete document unto itself. Both Type 1 and 2 modules and

segments should have unique file names and module and segment names.

Note: Type 1 modules or segments cannot be included in HTML, XML, PDF, or XBRL format

documents. They may be used in ASCII documents only.

5.3.2.1 How EDGAR Handles Segments

EDGAR must process a segment submission without errors before it can be indexed on the

EDGAR database. You must reference the subordinate segment in a master segment within six

business days after the subordinate segment was indexed, or the subordinate segment expires. A

subordinate segment can be referenced once only in a live submission.

How to C#: Basic SDK Concept of XDoc.PDF for .NET

You may add PDF document protection functionality into your C# of PDF document, including editing PDF url links and quick navigation link in bookmark

clickable links in pdf files; pdf link

VB.NET PDF: Basic SDK Concept of XDoc.PDF

You may add PDF document protection functionality into your VB.NET of PDF document, including editing PDF url links and quick navigation link in bookmark

change link in pdf file; adding a link to a pdf in preview

EDGAR Filer Manual (Volume II)

5-36

April 2016

Reference subordinate Type 1 segments in the master segment using the beginning segment tag

<SEGMENTS>, the segment name, and the ending segment tag </SEGMENTS>. These tags are

placed in the document where you want the Type 1 segment(s) to be inserted.

Type 2 segments are complete documents associated with a filing CIK. Type 2 segments are

referenced on the Attached Module/Segment page on the submission templates. EDGAR

automatically includes the Type 2 segment document upon receipt of the submission.

EDGAR will suspend all segments containing errors.

Note: You may not reference segments within a segment. However, you can reference modules

within a segment.

With segmented filings:

•

You identify one segment as the master segment and identify the registrant for whom the

filing is being made

•

All other segments are subordinate segments

•

The CIK used to identify the filer in the master segment is the master segment CIK and it

must be included in subordinate segments for reference

•

You must transmit the master segment to us last after all subordinate segments have been

transmitted. The master segment is the submission type that is the final assembled

submission. It must reference each subordinate submission segment submission

The following requirements apply to filings submitted in segments:

•

We must receive and accept all segments that comprise a filing within six business days

•

You must submit the master segment last

•

You cannot correct segment submissions; you must re-submit them

•

You can use segments once only; after that they are unavailable. The Master Segment

CIK field in subordinate segments must match the Filer CIK fields in the master segment

•

If the assembled master segment is suspended the subordinate segments remain available

to be used

5.3.2.2 Constructing Type 1 Modules and Segments

Type 1 modules and segments are portions of a document rather than attachments like Type 2

modules and segments and are referenced within your submission document. Creating Type 1

modules and segments is not much different from creating a submission:

1. Create your Type 1 module or segment document as HTML or ASCII. Rules are

described in Chapter 5.

2. Assemble a module or segment submission using the Module/Segment template in

EDGARLink Online as described later in Section 7.3.1, “Submission.”

3. For the Type field, select “Type 1.”

4. Transmit the Type 1 module or segment created in EDGARLink Online using the

Transmitting Modules and Segments procedures described in Section 7.6.2,

April 2016

5-37

EDGAR Filer Manual (Volume II)

“Transmitting Modules and Segments.” If your live filing is accepted, EDGAR will

index and store your module or segment.

Your modules or segments must have been created, transmitted, accepted, and indexed by

EDGAR before you are able to reference them within a submission document.

Modules and segments are stored on EDGAR and indexed by your CIK. Other CIKs can

reference your modules, but they must have the pertinent information: CIK, CCC, module name.

Segments can be referenced by other CIKs, but must be submitted by listing the CIK of the

segment creator. Modules must be removed from EDGAR by the filing CIK, while EDGAR

automatically deletes segments. Refer to Section 5.3.3, “Maintaining Modules and Segments,”

for Module and Segment maintenance. When EDGAR processes a submission referencing a

Type 1 module or segment, they are automatically included within the submission.

•

Multiple references to the same Type 1 module or segment will suspend the filing.

5.3.2.3 Type 2 Modules and Segments

Type 2 modules and segments are complete documents and when EDGAR receives your

submission they are included at the bottom of the submission. Preparation of the documents

themselves is discussed in the previous Sections. Referencing or including them in your filing is

discussed in Section 7.3.6.1, “Referencing Your Module or Segment Document.” Using the

Referenced Module/Submission List page allows you to add only Type 2 modules and segments

in your submission. Since Type 2 modules and segments are complete documents, you do not

have to modify another attached document to show where the content must be inserted like you

do for Type 1 modules or segments. The rest of this section deals with this topic.

5.3.2.4 Type 1 Module References

EDGAR treats the module as your private information, and stores it on our database according to

your CIK. Another filer may reference your module by providing your CIK and CCC, as shown

in the examples.

To include a Type 1 module in a document, you must include a reference to the Type 1 module

within a document. Type 2 modules are treated like submission documents and are included in

your submission automatically when you include them on the Attached Module/Segment page.

They are attached at the bottom of the submission. EDGAR will suspend any module with

submission headers or document headers.

5.3.2.5 How to Reference a Type 1 Module in a Submission Document

EDGAR compiles, processes, and indexes your submissions. You are still required to place Type

1 module references within the document text where you want the module to appear.

The following is an example of how to refer to a module in a subsequent submission:

Example of Referencing a TYPE 1 Module – a partial document (this reference is made within

the text of a document.):

xxxxxxxxxxxxxxx (text of submission) xxxxxxxxxxxxxxxxxxxxxxxxxxxx

<NAME> OPINION2

<CIK> 1234567890

EDGAR Filer Manual (Volume II)

5-38

April 2016

<CCC> x21234@1

</MODULE>

xxxxxxxxxxxxxxx (any additional text) xxxxxxxxxxxxxxxxxxxxxxxxxxxx

5.3.2.6 How to Reference a Type 1 Segment in a Submission Document

When your filing has Type 1 segments, you should use the segment tags in the document of your

submission, as shown below:

xxxxxxxxxxxxxxx (text of submission) xxxxxxxxxxxxxxxxxxxxxxxxxxxx

OPINION1

</SEGMENTS>

xxxxxxxxxxxxxxx (any additional text) xxxxxxxxxxxxxxxxxxxxxxxxxxxx

5.3.3 Maintaining Modules and Segments

When you are creating a submission and want to include a reference to a module or segment, you

can verify that it is residing on EDGAR by using the Retrieve Module and Segments page on the

EDGAR Filing Website:

1. Log in to EDGAR and access the Retrieve/Edit Company and Submission Data page

via the Retrieve/Edit Data menu item.

2. Click the ‘Retrieve Module/Segment Information’ link.

3. The Module/Segment Information page appears. Click one of the two links to access

the module or segment information page:



Retrieve Module Information



Retrieve Segment Information

Figure 5-3: Module/Segment Information Page

5.3.3.1 Module Information

When you access the Module Information page by clicking the ‘Retrieve Module Information’

link, EDGAR displays a list of all the modules currently residing on EDGAR for your CIK. The

list contains the names and dates the modules were posted.

April 2016

5-39

EDGAR Filer Manual (Volume II)

Figure 5-4: Module Information Page

Use your browser’s print function to print this list for future reference in your submission

documents, or reference in the Module/Segment page of EDGARLink Online.

Note: You cannot view the contents of a module or segment from this page.

5.3.3.1.1 Deleting Modules

Because modules are stored on EDGAR indefinitely, from time to time you may need to update

modules on EDGAR. To replace a module, delete the existing module, and then transmit the new

module with the same name.

1. Log in to the EDGAR Filing Website or the EDGAR OnlineForms/XML Website.

2. Click the ‘Retrieve/Edit Data’ link. Enter your CIK and CCC.

3. Click the ‘Retrieve Module/Segment Information’ link. (The Module/Segment

Information page is displayed.)

4. Click the ‘Retrieve Module Information’ link.

5. Click the [Yes] button on the bottom of this page to open the Delete Module page.

On the Delete Module page, a list of your modules is displayed in the Select Module to Delete

list.

Figure 5-5: Delete Module Page

EDGAR Filer Manual (Volume II)

5-40

April 2016

6. Select the module you wish to delete and click the [Delete Module] button.

The Module Delete Confirmation page appears listing the module name and confirming you

want to delete the listed module from EDGAR.

Figure 5-6: Module Delete Confirmation Page

7. Click the [Confirm Module Deletion] button to delete the module.

8. Click the [Cancel Changes] button to cancel the deletion, and return to the Company

and Submission Information Retrieval page.

The Delete Module Results page appears confirming your module has been deleted. Return to

the Delete Module page to remove any additional modules. Once your module has been deleted

from EDGAR, you cannot restore it. You will have to prepare and resubmit the module using the

Module/Segment submission.

Figure 5-7: Delete Module Results Page

5.3.3.2 Segment Information

Because segments are stored on EDGAR for only six (6) business days, you do not need to delete

them. However, you can check to verify that a segment is still residing on EDGAR:

1. Log in to the EDGAR Filing Website or the EDGAR OnlineForms/XML Website.

2. Click the ‘Retrieve/Edit Data’ link. Enter your CIK and CCC.

3. Click the ‘Retrieve Module/Segment Information’ link. (The Module/Segment

Information page is displayed.)

4. Click the ‘Retrieve Segment Information’ link. The Segment Information page

appears with a list of all of the segments related to your CIK.

Documents you may be interested

pdfdocument c# : Add a link to a pdf application SDK cloud windows wpf winforms class vol_II_ch53-part795