DataStandardizer.Communication
1.1.1
Prefix Reserved
See the version list below for details.
dotnet add package DataStandardizer.Communication --version 1.1.1
NuGet\Install-Package DataStandardizer.Communication -Version 1.1.1
<PackageReference Include="DataStandardizer.Communication" Version="1.1.1" />
<PackageVersion Include="DataStandardizer.Communication" Version="1.1.1" />
<PackageReference Include="DataStandardizer.Communication" />
paket add DataStandardizer.Communication --version 1.1.1
#r "nuget: DataStandardizer.Communication, 1.1.1"
#:package DataStandardizer.Communication@1.1.1
#addin nuget:?package=DataStandardizer.Communication&version=1.1.1
#tool nuget:?package=DataStandardizer.Communication&version=1.1.1
Introduction
Data Standardizer provides implementations of various internationally recognised standards in data processing, covering topics ranging from languages to currencies and geographical entities. With strongly-typed enumerations for each standard (where applicable) or other targeted data types, you can represent these elements in your code such that errors with invalid values are minimised.
Supported target platforms include (modern) .Net and .Net Standard. Data Standardizer can be used in modern application software, but is also available as an option for older codebases that are being upgraded more gradually or may remain on older frameworks indefinitely.
📚 Documentation
Full documentation — user guides, concepts, and API reference for every package — is published at matthew25187.github.io/DataStandardizer.
Supporting the project
If you derive a commercial benefit from use of Data Standardizer or feel it otherwise adds value to your project, you are asked to please consider supporting the project. You can do this by becoming a GitHub sponsor to make a financial contribution. Data Standardizer is maintained and enhanced by @matthew25187 in his personal time and made available for free for all to use.
Getting Started
Installation
Data Standardizer is available as a series of packages from NuGet.org that can be linked to your existing projects. Available packages include:
| Package | Description |
|---|---|
| DataStandardizer.Chronology | Supports the following standards:<ul><li>TZ Database</li><li>Unix time</li><li>DOS date & time</li></ul> |
| DataStandardizer.Communication | Supports the following standards:<ul><li>Recommendation ITU-T E.164, The international public telecommunication numbering plan</li></ul> |
| DataStandardizer.Core | Common types used to implement standards in the other packages. You should not need to link to this package directly. |
| DataStandardizer.File.CSV | Supports the following standards:<ul><li>RFC 4180, Common Format and MIME Type for Comma-Separated Values (CSV) Files</li></ul> |
| DataStandardizer.Geography | Supports the following standards:<ul><li>ISO 3166-1, Codes for the representation of names of countries and their subdivisions – Part 1: Country code</li><li>ISO 3166-2, Codes for the representation of names of countries and their subdivisions – Part 2: Country subdivision code</li><li>UN M49, Standard Country or Area Codes for Statistical Use (Series M, No. 49)</li></ul> |
| DataStandardizer.Language | Supports the following standards:<ul><li>ISO 639, Code for the representation of names of languages</li><ul><li>Part 1: Alpha-2 code</li><li>Part 2: Alpha-3 code</li><li>Part 3: Alpha-3 code for comprehensive coverage of languages</li><li>Part 5: Alpha-3 code for language families and groups</li></ul><li>ISO 15924, Codes for the representation of names of scripts</li></ul> |
| DataStandardizer.LanguageTag | Supports the following standards:<ul><li>Best Current Practice (BCP) 47 for IETF language tags</li></ul> |
| DataStandardizer.Money | Supports the following standards:<ul><li>ISO 4217, Codes for the representation of currencies and funds</li><ul><li>Table A.1 – Current currency & funds code list</li><li>Table A.2 – Current funds codes</li><li>Table A.3 – List of codes for historic denominations of currencies & funds</li></ul><li>Money type, as described in Patterns of Enterprise Application Architecture by Martin Fowler</li></ul> |
To use a particular standard in your application, find the corresponding package from the above list and add it as a dependency to your project. Instructions for doing so will depend on what development tooling you are using.
- Visual Studio: see Install and manage packages in Visual Studio using the NuGet Package Manager
- .Net CLI: see Install and manage NuGet packages with the dotnet CLI
- Visual Studio Code: see NuGet in Visual Studio Code
See the Get started guide for step-by-step installation and a quickstart.
Software dependencies
Depending on which .Net platform you are targeting, the above packages will also depend on various other system- and third-party packages. They will be included as static dependencies where required and should be automatically resolved, but if you are using a proxy for your package server you may need to make sure these other packages are also available.
Latest releases
The most recently produced release version (shown above) does not necessarily correspond with the latest package version published to NuGet or any other publically available source.
Build and test
Data Standardizer is open source so you can read, build, and adapt it for your own use. The project does not currently accept third-party code contributions; the instructions below are provided as a convenience for working with your own copy or fork of the repository.
After cloning the repository, you can compile the entire solution from the repository root:
dotnet build DataStandardizer.sln
and run the XUnit-based tests with:
dotnet test DataStandardizer.sln
Per-package solution filter (*.slnf) files let you build or test a single package in isolation. For the full branching strategy, per-package builds, IDE testing, and the PowerShell scripts that regenerate the standard enums, see Build from source in the documentation.
Usage
Though each package contains many types, typically there are only a few you will use directly in your application. See the project documentation for user guides, concepts, and API reference covering each package — including built-in CSV reading, writing, and normalization in DataStandardizer.File.CSV.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
| .NET Core | netcoreapp1.0 was computed. netcoreapp1.1 was computed. netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
| .NET Standard | netstandard1.0 is compatible. netstandard1.1 was computed. netstandard1.2 was computed. netstandard1.3 was computed. netstandard1.4 was computed. netstandard1.5 was computed. netstandard1.6 was computed. netstandard2.0 is compatible. netstandard2.1 was computed. |
| .NET Framework | net45 was computed. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
| MonoAndroid | monoandroid was computed. |
| MonoMac | monomac was computed. |
| MonoTouch | monotouch was computed. |
| Tizen | tizen30 was computed. tizen40 was computed. tizen60 was computed. |
| Universal Windows Platform | uap was computed. uap10.0 was computed. |
| Windows Phone | wp8 was computed. wp81 was computed. wpa81 was computed. |
| Windows Store | netcore was computed. netcore45 was computed. netcore451 was computed. |
| Xamarin.iOS | xamarinios was computed. |
| Xamarin.Mac | xamarinmac was computed. |
| Xamarin.TVOS | xamarintvos was computed. |
| Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 1.0
- DataStandardizer.LanguageTag (>= 1.1.0)
- JetBrains.Annotations (>= 2025.2.2)
- NETStandard.Library (>= 2.0.3)
- System.Text.RegularExpressions (>= 4.3.1)
- System.ValueTuple (= 4.5.0)
-
.NETStandard 2.0
- DataStandardizer.LanguageTag (>= 1.1.0)
- JetBrains.Annotations (>= 2025.2.2)
-
net10.0
- DataStandardizer.LanguageTag (>= 1.1.0)
-
net8.0
- DataStandardizer.LanguageTag (>= 1.1.0)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on DataStandardizer.Communication:
| Package | Downloads |
|---|---|
|
DataStandardizer.File.iCal
Data Standardizer provides implementations of various internationally recognised standards in data processing, covering topics ranging from languages to currencies and geographical entities. With strongly-typed enumerations for each standard (where applicable) or other targeted data types, you can represent these elements in your code such that errors with invalid values are minimised. Provides types supporting the reading and writing of iCalendar files. Includes: - Internet Calendaring and Scheduling Core Object Specification (iCalendar), RFC 5545 - Parameter Value Encoding in iCalendar and vCard, RFC 6868 - New Properties for iCalendar, RFC 7986 - jCal: The JSON Format for iCalendar, RFC 7265 - xCal: The XML Format for iCalendar, RFC 6321 |
|
|
DataStandardizer.File.InternetMessage
Data Standardizer provides implementations of various internationally recognised standards in data processing, covering topics ranging from languages to currencies and geographical entities. With strongly-typed enumerations for each standard (where applicable) or other targeted data types, you can represent these elements in your code such that errors with invalid values are minimised. Provides types supporting the reading and writing of Internet messages, including: - RFC 5322 and RFC 6532: a streaming reader of the header fields of a message, with UTF-8 in field bodies - RFC 2045 and RFC 2046: a streaming reader of the MIME entities of a message, with multipart bodies, embedded messages and transfer decoding - RFC 5322, RFC 6532, RFC 2045 and RFC 2046: streaming writers of header fields and MIME entities, with folding, transfer encoding, multipart boundaries and byte-exact copying of what has not changed - RFC 5322, RFC 6532 and RFC 6854: typed addresses, mailboxes, groups, message identifiers and keyword phrases, parsed from the modern and obsolete syntax and written in the modern form where the modern syntax can express them - RFC 5322: typed date-times, parsed from the modern and obsolete syntax and written in the modern form, which keep an unknown UTC offset (-0000), a leap second and whether a day of the week was given - RFC 2047: encoded words in display names, keyword phrases, comments and unstructured fields, decoded when read and written where text is not US-ASCII - RFC 2045, RFC 2183, RFC 2231, RFC 2392 and RFC 3282: the MIME-Version, Content-Type, Content-Transfer-Encoding, Content-ID, Content-Description, Content-Disposition and Content-Language header fields, with cid: URIs - RFC 5322 and RFC 6854: a message object model with typed accessors for the origination, destination, identification, informational, resent and trace fields, a reader and writer that keep unchanged fields byte for byte, and the conformance checks of RFC 5322 §3.6 - RFC 2045, RFC 2046, RFC 2387 and RFC 2392: a MIME entity tree with decoded content, text and HTML bodies, attachments, cid: lookup, a message builder, and a writer that rewrites only what has changed - RFC 2557 and RFC 2387: MHTML files, with Content-Location, the root of a multipart/related entity, URLs resolved to their parts, a document builder, and a reader and writer - RFC 4155: mbox files in the mboxrd, mboxo, mboxcl and mboxcl2 variants, with a reader that takes one message at a time, so a mailbox of any size can be processed, and a writer - Apple Mail EMLX files: a message with its byte count and its property list of metadata, with typed flags and dates, unknown keys kept, partial files with their parts supplied by the caller, and a reader and writer |
|
|
DataStandardizer.File.vCard
Data Standardizer provides implementations of various internationally recognised standards in data processing, covering topics ranging from languages to currencies and geographical entities. With strongly-typed enumerations for each standard (where applicable) or other targeted data types, you can represent these elements in your code such that errors with invalid values are minimised. Provides types supporting the reading and writing of vCard files. Includes: - vCard Format Specification, RFC 6350 (content lines, value types, the card object model, and reading and writing cards with conformance checks) - Parameter Value Encoding in iCalendar and vCard, RFC 6868 - jCard: The JSON Format for vCard, RFC 7095 (reading and writing cards as JSON, on .NET Standard 2.0 and later) - xCard: vCard XML Representation, RFC 6351 (reading and writing cards as XML) - vCard 2.1 (reading and writing vCard 2.1 cards, with quoted-printable, BASE64, CHARSET, parameters with no name and the card an AGENT holds) - vCard MIME Directory Profile, RFC 2426, and MIME Content-Type for Directory Information, RFC 2425 (reading and writing vCard 3.0 cards, and converting between versions) - Calendar Attributes for vCard and LDAP, RFC 2739 - vCard Extensions for Instant Messaging, RFC 4770 - vCard Format Extensions for JSContact, RFC 9554 - vCard KIND:application, RFC 6473, and vCard KIND:device, RFC 6869 - vCard Format Extensions: Place of Birth, Place and Date of Death, RFC 6474 - vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) Group, RFC 6715 - vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol, RFC 8605 |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.0.0 | 217 | 11/10/2026 |
| 1.1.1 | 1,227 | 10/8/2026 |
| 1.1.0 | 747 | 1/10/2026 |
| 1.0.0-preview.1 | 243 | 12/15/2025 |
- Synchronize the shared ITU E.164 parse expression cache.
- Parsing an ITU E.164 number from more than one thread could throw, yield a wrong result, or spin forever.
- Parse and TryParse try each of the five structure types in turn until one matches, so a single call performs up to five unsynchronized read and write cycles, and the cache is coldest at startup, when a service is most likely to be serving several requests at once.
- Guard the cache with a lock, so that the lookup and the insertion which follows it cannot be interleaved.
- Restore the contract of TryParse, which is documented never to throw and which the duplicate key exception escaped through.
- Add regression tests which reset the cache to cold and release thirty-two threads at a barrier so that they contend for the same key.