DataStandardizer.BCP47 0.7.0

.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher. .NET Standard 1.0 This package targets .NET Standard 1.0. The package is compatible with this framework or higher. 
dotnet add package DataStandardizer.BCP47 --version 0.7.0
                    


                    

                
NuGet\Install-Package DataStandardizer.BCP47 -Version 0.7.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="DataStandardizer.BCP47" Version="0.7.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="DataStandardizer.BCP47" Version="0.7.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="DataStandardizer.BCP47" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add DataStandardizer.BCP47 --version 0.7.0
                    


                    

                
#r "nuget: DataStandardizer.BCP47, 0.7.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package DataStandardizer.BCP47@0.7.0
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=DataStandardizer.BCP47&version=0.7.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=DataStandardizer.BCP47&version=0.7.0
                    


                            Install as a Cake Tool

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.

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.Core Common types used to implement standards in the other packages. You should not need to link to this package directly.
DataStandardizer.BCP47 Supports IETF BCP 47 language tags.
DataStandardizer.ISO15924 Supports ISO 15924, Codes for the representation of names of scripts.
DataStandardizer.ISO3166 Supports ISO 3166, Codes for the representation of names of countries and their subdivisions parts 1 & 2.
DataStandardizer.ISO4217 Supports ISO 4217, Codes for the representation of currencies and funds.
DataStandardizer.ISO639 Supports ISO 639, Codes for the representation of names of languages parts 1, 2, 3 & 5.
DataStandardizer.UNM49 Supports UN M49 or the Standard Country or Area Codes for Statistical Use (Series M, No. 49).

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.

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.

The repository includes a number of PowerShell scripts with names starting with Generate. These scripts are used to re-generate the enums that comprise the implementations of each corresponding standard and require the use of a PowerShell shell prompt to execute as well as access to the official flat-file data sources provided by the relevant standards body or designated maintainer. Some scripts may also require a minimum version of PowerShell to run.

Other scripts and YAML files are included to support the infrastructure (IaC) used by the Data Standardizer project for functions such as pipelines, package hosting, etc. These files are not intended to be used by the end-user.

Latest releases

Package Release version Release status Build status (preview) Test status (preview)
DataStandardizer.Core DataStandardizer.Core package in DataStandardizer@Release feed in Azure Artifacts Build Status Build Status Build Status
DataStandardizer.BCP47 DataStandardizer.BCP47 package in DataStandardizer@Release feed in Azure Artifacts Build Status Build Status Build Status
DataStandardizer.ISO15924 DataStandardizer.ISO15924 package in DataStandardizer@Release feed in Azure Artifacts Build Status Build Status Build Status
DataStandardizer.ISO3166 DataStandardizer.ISO3166 package in DataStandardizer@Release feed in Azure Artifacts Build Status Build Status Build Status
DataStandardizer.ISO4217 DataStandardizer.ISO4217 package in DataStandardizer@Release feed in Azure Artifacts Build Status Build Status Build Status
DataStandardizer.ISO639 DataStandardizer.ISO639 package in DataStandardizer@Release feed in Azure Artifacts Build Status Build Status Build Status
DataStandardizer.UNM49 DataStandardizer.UNM49 package in DataStandardizer@Release feed in Azure Artifacts Build Status Build Status Build Status

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

Branching strategy

The Data Standardizer repository makes use of two "main" branches. They are:

Name Description
master Top-level branch from which all package release builds are produced. The develop branch will be merged into this branch when a new release is done.
develop Default branch and the branch from which preview package builds are produced. Changes are marshalled on this branch before being included in a release build.

Other branches that may be created from time-to-time are not relevant to non-contributors.

Build source code

To compile the source code, first you will need to clone the repository to your local machine. You can find instructions for doing so here.

With the source code, you can then open a command prompt, change the current directory to the repository root folder, and use the following command to compile the entire solution:

dotnet build DataStandardizer.sln

You can also work with the source code in IDEs such as Visual Studio or Visual Studio Code. In these cases, open the DataStandardizer.sln solution file to access the source code.

There are also solution filter files (*.slnf) for each of the projects (packages) in the repository root folder alongside the main solution file. These files narrow the scope of projects included to only those needed to build and test a single package. You can also build these solution filters if so desired, and even open them in your IDE if you only want to work with the code for one package. They are included mainly because they are used by the CI pipelines to enable the building and testing of each package individually.

Running tests

The included tests are based on the XUnit test framework. To run the tests, you will need a test runner able to work with XUnit. The test projects do include a default test runner dependency, which enables you to run the tests from the command line. With a command prompt open (as described above), you can run all tests in the solution:

dotnet test DataStandardizer.sln

Visual Studio includes the Test Explorer that enables you to discover available tests and execute those tests by various categorizations. Find out more about Test Explorer here. Testing is also supported in Visual Studio Code with use of the C# Dev Kit (learn more here).

Usage

Though each package contains many types, typically there will be only a few that you will end up using directly in your application. Listed here are the main types you are most likely to include in your source code.

DataStandardizer.BCP47

Type Description
Bcp47LanguageTag Represents an IETF language tag. May be created by using the provided static factory methods or by using the language tag builder.
Bcp47LanguageTagBuilder Can be used to construct a language tag using a fluent-style syntax.
SubtagRegistry Represents a copy of the IANA Subtag Registry. May be loaded by various means, but the source must be in the original "record-jar" format as described in RFC 5646. Used to create language tags based on the subtag registry (which defines most valid tags and subtags) as opposed to creating a language tag based just on the rules defined by RFC 5646.
SubtagRegistryFileDateRecord Represents a "File-Date" record from the subtag registry.
SubtagRegistrySubtagRecord Represents a "Subtag" record from the subtag registry.
SubtagRegistryTagRecord Represents a "Tag" record from the subtag registry.

DataStandardizer.ISO15924

Type Description
Iso15924 An enum containing script codes from ISO 15924. Includes both the four-letter alpha codes and three-digit numeric codes from the standard as the name and value of the members, respectively.

DataStandardizer.ISO3166

Type Description
Iso3166Part1Alpha2 An enum containing the country codes from ISO 3166-1 Alpha-2. Includes both the two-letter alpha codes and numeric codes from the standard as the name and value of the members, respectively.
Iso3166Part1Alpha3 An enum containing the country codes from ISO 3166-1 Alpha-3. Includes both the three-letter alpha codes and numeric codes from the standard as the name and value of the members, respectively.
Iso3166Part2 An enum containing the subdivision codes from ISO 3166-2. Given the hierarchical nature of these codes, this implementation uses a nested structure to access the codes so that each group of subdivision codes is grouped under a nested type named after the country code of the country the subdivision codes belong to.

DataStandardizer.ISO4217

Type Description
Iso4217Current An enum containing active currency codes from ISO 4217. Includes both the three-letter alpha codes and numeric codes from the standard as the name and value of each member, respectively.
Iso4217Historic An enum containing retired currency codes from ISO 4217. Includes both the three-letter alpha codes and numeric codes from the standard as the name and value of each member, respectively.

DataStandardizer.ISO639

Type Description
Iso639Part1 An enum containing the alpha-2 language codes from ISO 639-1.
Iso639Part2B An enum containing the bibliographic alpha-3 language codes from ISO 639-2.
Iso639Part2T An enum containing the terminological alpha-3 language codes from ISO 639-2.
Iso639Part3 An enum containing the alpha-3 language codes from ISO 639-3.
Iso639Part5 An enum containing the alpha-3 language family codes from ISO 639-5.

DataStandardizer.UNM49

Type Description
UnM49ByAlpha2Code An enum containing the numeric M49 codes from standard UN M49. Because of technical requirements on the naming of members, each code is keyed on its corresponding ISO 3166-1 alpha-2 code.
UnM49ByAlpha3Code An enum containing the numeric M49 codes from standard UN M49. Because of technical requirements on the naming of members, each code is keyed on its corresponding ISO 3166-1 alpha-3 code.

N.B. Because of the way the source data is arranged, the above enums only directly include members representing M.49 codes that have a corresponding alpha-2 or alpha-3 code from ISO 3166-1. There are additional M.49 codes representing supra-national regions or other areas that are included as metadata on these enum members, and can be retrieved using provided extension methods.

Product 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 was computed.  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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.7.0 239 7/27/2025

* Update symbol publishing configuration in release build pipeline (#4)
* Fix warning message produced by PublishSymbols task in CI pipeline. (#2)
* Protect access to string enum constructors with non-public scope. (#1)