
X.509 Certificate (DER) — Security SAMPLE
DER-encoded twin of the Wave G SAMPLE certificate for binary X.509 decoders.
- File
- DER · Pki · DER
- Use case
- Certificate & key testing· Conversion set
Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 217 of 221; 24 results per page.

DER-encoded twin of the Wave G SAMPLE certificate for binary X.509 decoders.

A self-signed X.509 v3 certificate in PEM (Base64) encoding with a SAN and key-usage extensions — published sample material for testing certificate and TLS parsers. Not a real identity.

Self-signed X.509 SAMPLE certificate in PEM under /files/security/ — published sample material for TLS and PEM parsers.

Two-PEM-block SAMPLE chain file for multi-cert parsers and bundle importers.

Short ANSI X12 204 SAMPLE transaction for EDI parser / translator tests.

Short ANSI X12 214 SAMPLE transaction for EDI parser / translator tests.

An ANSI X12 810 invoice that references the 850 purchase order — ISA/GS/ST envelope with BIG, IT1 line items, and a total. The invoice twin of the purchase order, for testing EDI document flows.

An ANSI X12 850 purchase order — ISA/GS/ST envelope with BEG, N1, and PO1 line items. A fixture for testing EDI parsers and translators. Paired with the 810 invoice for the same order.

Short ANSI X12 855 SAMPLE transaction for EDI parser / translator tests.

Short ANSI X12 856 SAMPLE transaction for EDI parser / translator tests.

Short ANSI X12 940 SAMPLE transaction for EDI parser / translator tests.

Short ANSI X12 997 SAMPLE transaction for EDI parser / translator tests.

A 10 mm cube as X3D — the XML successor to VRML for web and interchange 3D. For testing X3D parsers and VRML↔X3D conversion.

The XLIFF 1.2 half of a version twin covering how each version represents inline markup and placeholders. XLIFF 1.2 keeps the original markup inline in <bpt>/<ept> and uses <g>, <x/> and <ph>; XLIFF 2.0 replaced all of them with <pc>, <ph/>, <sc/>/<ec/> and moved the markup into an <originalData> block referenced by id.

The XLIFF 1.2 half of a version twin covering how each version expresses a plural group. XLIFF 1.2 uses a <group restype="x-gettext-plurals"> whose trans-units are ordered by gettext form index; XLIFF 2.0 dropped restype, so the same content becomes one <unit> per CLDR category, named by category rather than by index.

The XLIFF 1.2 half of a version twin covering how each version records translation progress. XLIFF 1.2 has approved="yes|no" plus a ten-value target state; XLIFF 2.0 removed approved and cut the vocabulary to four ordered values (initial, translated, reviewed, final) with everything else pushed into a namespaced subState.

An OASIS XLIFF 1.2 file with English source and Spanish target trans-units and notes — the classic interchange format between authoring tools and translation-management systems.

The XLIFF 2.0 half of a version twin covering how each version represents inline markup and placeholders. XLIFF 1.2 keeps the original markup inline in <bpt>/<ept> and uses <g>, <x/> and <ph>; XLIFF 2.0 replaced all of them with <pc>, <ph/>, <sc/>/<ec/> and moved the markup into an <originalData> block referenced by id.

The XLIFF 2.0 half of a version twin covering how each version expresses a plural group. XLIFF 1.2 uses a <group restype="x-gettext-plurals"> whose trans-units are ordered by gettext form index; XLIFF 2.0 dropped restype, so the same content becomes one <unit> per CLDR category, named by category rather than by index.

The XLIFF 2.0 half of a version twin covering how each version records translation progress. XLIFF 1.2 has approved="yes|no" plus a ten-value target state; XLIFF 2.0 removed approved and cut the vocabulary to four ordered values (initial, translated, reviewed, final) with everything else pushed into a namespaced subState.

An OASIS XLIFF 2.0 file with the same content as its 1.2 twin, using the modern unit/segment structure — for testing XLIFF 2.0 parsers and 1.2-to-2.0 converters.

A legacy Excel 97–2003 (.xls / BIFF8) workbook holding the same tabular data as the plain XLSX and ODS — for testing legacy-format readers and XLS↔XLSX conversion.

A workbook with a data table plus a native bar chart and a line chart bound to the cells — for testing whether spreadsheet parsers and XLSX-to-PDF converters preserve and render embedded charts.

A dashboard sheet exercising the features importers miss: a merged title cell, a three-colour conditional-formatting scale, a data-validation dropdown, cell borders, and frozen panes.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.