Standards coverage
Which internationally recognised standard is implemented by which Data Standardizer package.
Each package name links to its overview page, where you’ll find install instructions, how-to guides, and an API reference.
| Standard | Package | Description |
|---|---|---|
| TZ Database | Chronology | Standardised, named time zones (e.g. Europe/Berlin) with associated metadata. |
| Unix time | Chronology | A point in time as seconds since the Unix epoch (1 January 1970 UTC). |
| DOS date & time | Chronology | A packed date/time as used by the MS-DOS file system (1980–2107). |
| ITU-T E.164 | Communication | The international public telecommunication numbering plan (telephone numbers). |
| RFC 2045 | Communication | MIME Part One: Content-Type values, Content-Transfer-Encoding tokens, and the quoted-printable and base64 encodings. |
| RFC 2046 | Communication | MIME Part Two: top-level media types and the charset parameter. |
| RFC 2047 | Communication | MIME Part Three: encoded words, which carry text that isn’t US-ASCII in a message header. |
| RFC 2231 | Communication | MIME parameter value and encoded word extensions: character sets, languages and continuations. |
| RFC 2397 | Communication | The data: URL scheme. |
| RFC 2978 | Communication | IANA charset registration procedures: the syntax of character set names. |
| RFC 4289 | Communication | MIME Part Four: Content-Transfer-Encoding extension tokens. |
| RFC 4648 | Communication | The strict base64 of §4, used by iCalendar BINARY values and “B” encoded words. |
| RFC 6657 | Communication | The default charset of textual media types. |
| RFC 6838 | Communication | Media type naming rules and registration trees. |
| RFC 6839 | Communication | Structured syntax suffixes for media types, such as +json and +xml. |
| RFC 4180 | File.CSV | Common format and MIME type for Comma-Separated Values (CSV) files. |
| RFC 5545 | File.iCal | Internet Calendaring and Scheduling Core Object Specification (iCalendar): .ics files, their components and properties, and recurrence rules. |
| RFC 6868 | File.iCal | Parameter value encoding in iCalendar and vCard (caret encoding of quotes and line breaks in parameter values). |
| RFC 7986 | File.iCal | New properties for iCalendar, such as NAME, COLOR, IMAGE and REFRESH-INTERVAL. |
| RFC 7265 | File.iCal | jCal: the JSON format for iCalendar. |
| RFC 6321 | File.iCal | xCal: the XML format for iCalendar. |
| RFC 5322 | File.InternetMessage | Internet Message Format: header fields, addresses, date-times and message identifiers, in .eml files. |
| RFC 6532 | File.InternetMessage | Internationalized email headers: UTF-8 in field bodies. |
| RFC 6854 | File.InternetMessage | Group syntax in the From and Sender header fields. |
| RFC 2045, RFC 2046 | File.InternetMessage | MIME header fields, multipart bodies, embedded messages and transfer decoding in a message. The values and codecs come from Communication. |
| RFC 2047 | File.InternetMessage | Encoded words in display names, keyword phrases, comments and unstructured fields. |
| RFC 2183 | File.InternetMessage | The Content-Disposition header field. |
| RFC 2231 | File.InternetMessage | Extended parameters of the Content-Type and Content-Disposition fields. |
| RFC 2387 | File.InternetMessage | The multipart/related content type. |
| RFC 2392 | File.InternetMessage | cid: URIs and the parts they refer to. |
| RFC 2557 | File.InternetMessage | MHTML: web pages saved with their resources, in .mht and .mhtml files. |
| RFC 3282 | File.InternetMessage | The Content-Language header field. |
| RFC 4155 | File.InternetMessage | The mbox format, in the mboxrd, mboxo, mboxcl and mboxcl2 variants. |
| EMLX | File.InternetMessage | The message files of Apple Mail, which have no published standard. The package follows the layout that open-source readers agree on. |
| RFC 6350 | File.vCard | vCard Format Specification (vCard 4.0): .vcf files, their properties, parameters and values, and the rules a card must follow. |
| RFC 6868 | File.vCard | Parameter value encoding in iCalendar and vCard, in vCard 4.0 cards. |
| RFC 7095 | File.vCard | jCard: the JSON format for vCard. |
| RFC 6351 | File.vCard | xCard: the XML format for vCard. |
| vCard 2.1 | File.vCard | The Electronic Business Card, version 2.1, with quoted-printable, BASE64 and CHARSET. |
| RFC 2425, RFC 2426 | File.vCard | The MIME directory profile for vCard 3.0. |
| RFC 2739 | File.vCard | Calendar attributes for vCard, such as FBURL and CALURI, in vCard 3.0. |
| RFC 4770 | File.vCard | Instant messaging addresses (IMPP) in vCard 3.0. |
| RFC 9554 | File.vCard | vCard extensions for JSContact, such as PRONOUNS, SOCIALPROFILE and the PHONETIC parameter. |
| RFC 6473, RFC 6869 | File.vCard | KIND:application and KIND:device. |
| RFC 6474 | File.vCard | Place of birth, and place and date of death. |
| RFC 6715 | File.vCard | The extensions of the OMA Converged Address Book, such as EXPERTISE, HOBBY and INTEREST. |
| RFC 8605 | File.vCard | The ICANN extensions for RDAP: CONTACT-URI and the CC parameter. |
| ISO 3166-1 | Geography | Codes for the representation of names of countries — Part 1: Country code. |
| ISO 3166-2 | Geography | Codes for the representation of names of countries — Part 2: Country subdivision code. |
| UN M49 | Geography | Standard Country or Area Codes for Statistical Use (Series M, No. 49). |
| ISO 639 (Parts 1, 2, 3, 5) | Language | Codes for the representation of names of languages (alpha-2, alpha-3, comprehensive coverage, and language families/groups). |
| ISO 15924 | Language | Codes for the representation of names of scripts. |
| BCP 47 | LanguageTag | IETF language tags (as defined by RFC 5646). |
| ISO 4217 (Tables A.1–A.3) | Money | Codes for the representation of currencies and funds — current codes, funds codes, and historic denominations. |
| Money type | Money | A monetary value combining an amount with an ISO 4217 currency code, after Martin Fowler’s Patterns of Enterprise Application Architecture. |
A note on DataStandardizer.Core
DataStandardizer.Core provides common types used to implement the standards in the other packages. It is pulled in automatically as a dependency, so you should not need to reference it directly.
Where to next
- See Platform support for the .NET / .NET Standard target matrix.
- Ready to use one? Head to Get started.