Essential International Standards and Specifications

Introduction

International standards and specifications provide crucial frameworks for consistency, interoperability, and data exchange across organizations, industries, and countries. This guide covers essential standards that developers, data scientists, and technical professionals should know.

Geographic & Location Standards

ISO 3166-1 Country Codes

Description: International standardization organization standard defining three main sets of country codes for 249 countries and territories. Widely used for international data exchange and geographic identification.

Variants:

ISO 3166-1 alpha-2: Two-letter country codes (e.g., US, GB, CN) - Most commonly used
ISO 3166-1 alpha-3: Three-letter country codes (e.g., USA, GBR, CHN) - More descriptive
ISO 3166-1 numeric: Three-digit codes (e.g., 840 for USA) - Used in numeric systems

Common Use Cases:

E-commerce shipping and billing addresses
Domain names (e.g., .uk, .de, .jp)
International data interchange
Financial transactions

Resource: ISO 3166-1 on Wikipedia

ISO 3166-2 Subdivision Codes

Description: Extends ISO 3166-1 to identify principal subdivisions (provinces, states, regions) of countries using a country code plus subdivision code.

Format: Country code + hyphen + subdivision code (e.g., US-CA for California, GB-ENG for England)

Use Cases:

Regional data organization
Administrative boundary identification
Sub-national geographic information systems

ISO 4217 Currency Codes

Description: International standard defining three-letter codes (and numeric codes) for world currencies. Essential for international finance and e-commerce.

Format: Three-letter alphabetic code (e.g., USD, EUR, GBP, JPY) + numeric code

Common Currencies:

USD (840) - United States Dollar
EUR (978) - Euro
GBP (826) - British Pound
JPY (392) - Japanese Yen
CNY (156) - Chinese Yuan

Use Cases:

Financial transactions and banking
International pricing
Currency conversion systems
E-commerce platforms

Resource: ISO 4217 on Wikipedia

ISO 639 Language Codes

Description: International standard defining codes for languages. Multiple variants for different levels of detail and use cases.

Variants:

ISO 639-1: Two-letter codes (e.g., en for English, zh for Chinese, es for Spanish)
ISO 639-2: Three-letter bibliographic and terminologic codes
ISO 639-3: Three-letter codes for individual languages
ISO 639-6: Three-letter codes for extinct and ancient languages

Common Use Cases:

Website localization and language selection
Content management systems
Natural language processing
Document classification
HTML lang attribute (e.g., <html lang="en">)

Resource: ISO 639 on Wikipedia

Date, Time & Timezone Standards

ISO 8601 Date and Time Format

Description: International standard for representing dates and times, enabling unambiguous date/time representation and exchange worldwide.

Standard Formats:

Date: YYYY-MM-DD (e.g., 2025-12-07)
Time: HH:MM:SS (e.g., 14:30:00)
Combined: YYYY-MM-DDTHH:MM:SS (e.g., 2025-12-07T14:30:00)
With Timezone: YYYY-MM-DDTHH:MM:SS±HH:MM (e.g., 2025-12-07T14:30:00+08:00)

Advantages:

Removes ambiguity (no DD/MM/YYYY confusion)
Sortable as strings
Machine-readable
Internationally recognized

Use Cases:

API data exchange
Database timestamps
Log files
Configuration files
Data serialization (JSON, XML)

Resource: ISO 8601 on Wikipedia

RFC 5322 Email Format

Description: Internet standard specifying the format of text messages used in email. Essential for email validation and parsing.

Basic Format: local-part@domain

Specifications:

Local part: Letters, numbers, and special characters (. ! # $ % & ’ * + - / = ? ^ _ ` { | } ~)
Domain: Valid domain name with proper TLD
Maximum length: 254 characters

Use Cases:

Email validation systems
Email parsing and processing
SMTP implementations
Contact management systems

Resource: RFC 5322 on IETF

Web & Internet Standards

RFC 3986 URI Syntax

Description: Standard defining the syntax and semantics of Uniform Resource Identifiers (URIs), the foundation of web addresses and resource identification.

URI Components:

scheme://authority/path?query#fragment
https://www.example.com:8080/path/to/resource?key=value#section

Components:

Scheme: Protocol (http, https, ftp, etc.)
Authority: User info, host, and port
Path: Resource location
Query: Additional parameters
Fragment: Sub-resource reference

Use Cases:

Web application architecture
API endpoint design
URL validation and parsing
Hyperlink management

Resource: RFC 3986 on IETF

HTTP Status Codes (RFC 7231)

Description: Standard HTTP response status codes indicating the outcome of web requests.

Main Categories:

1xx (Informational): Request received, continuing process
2xx (Success): Request successfully received and processed
- 200 OK, 201 Created, 204 No Content
3xx (Redirection): Further action required
- 301 Moved Permanently, 302 Found, 304 Not Modified
4xx (Client Error): Request contains errors
- 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found
5xx (Server Error): Server failed to fulfill request
- 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable

Use Cases:

Web application development
API design and response handling
Error handling and user feedback
Server monitoring and debugging

Resource: RFC 7231 on IETF

REST API Design Standards

Description: Best practices for designing RESTful web services using HTTP methods and status codes for resource-oriented APIs.

Core Principles:

Resource-oriented: Model APIs around nouns (resources), not verbs (actions)
HTTP Methods: GET (retrieve), POST (create), PUT (update), DELETE (remove)
Stateless: Each request contains all needed information
Cacheable: Responses should define themselves as cacheable or not
Layered: Client doesn’t know if connected directly to end server

Naming Conventions:

Plurals for collections: /users not /user
Hierarchical: /users/123/posts/456
Lowercase with hyphens: /user-profiles not /UserProfiles
Version in URL: /api/v1/users

Resource: RESTful API Best Practices

Data Format & Encoding Standards

JSON Schema (JSON:API)

Description: Standard and specification for building APIs using JSON. Provides conventions for request and response formatting.

Key Features:

Standardized error responses
Consistent resource representation
Relationship handling
Pagination standards
Content negotiation

Basic Structure:

{
  "data": {
    "type": "articles",
    "id": "1",
    "attributes": {
      "title": "Example Article",
      "body": "Article content"
    }
  }
}

Resource: JSON:API Specification

UTF-8 Character Encoding (RFC 3629)

Description: Unicode-based character encoding standard supporting all languages and special characters. The dominant encoding for web content.

Advantages:

Supports all Unicode characters
Backward compatible with ASCII
Variable-length encoding (1-4 bytes per character)
Efficient for European languages

Use Cases:

Web page encoding
Email text encoding
Database character sets
Programming language source files

Resource: UTF-8 on Wikipedia

MIME Types (RFC 2045)

Description: Standard for specifying the nature and format of internet content. Essential for proper content handling and display.

Common MIME Types:

Text:

text/plain - Plain text
text/html - HTML documents
text/css - CSS stylesheets
application/javascript - JavaScript files

Images:

image/png - PNG images
image/jpeg - JPEG images
image/svg+xml - SVG graphics
image/webp - WebP images

Data:

application/json - JSON data
application/xml - XML data
application/pdf - PDF documents

Resource: MIME Types Reference

Identification & Classification Standards

ISBN - International Standard Book Number

Description: Unique numeric identifier for books. Essential for library systems, publishing, and book commerce.

Formats:

ISBN-10: 10-digit format (older)
ISBN-13: 13-digit format (current standard, starting with 978 or 979)

Structure: Country/Publisher-Publisher-Title-Check digit

Use Cases:

Book identification and cataloging
Library systems
E-commerce book sales
Publishing and distribution

Resource: ISBN on Wikipedia

ISSN - International Standard Serial Number

Description: Unique identifier for periodicals and serials (journals, magazines, newspapers). Similar to ISBN but for ongoing publications.

Format: 8-digit number (ISSN X XXX XXXX) with check digit

Use Cases:

Journal and magazine identification
Library cataloging
Academic citation and indexing
Periodical management

Resource: ISSN on Wikipedia

ORCID - Open Researcher and Contributor ID

Description: Free, unique identifier for researchers and scholars, addressing author disambiguation in academic publishing.

Format: 16-digit number (XXXX-XXXX-XXXX-XXXX)

Features:

Persistent identifier for researchers
Connects research outputs and activities
Facilitates researcher collaboration
Used by major academic publishers

Use Cases:

Academic publishing and citations
Research collaboration platforms
Grant applications
Institutional repositories

Resource: ORCID Official Site

Semantic & Structured Data Standards

Schema.org Microdata

Description: Collaborative vocabulary for structured data markup on web pages. Helps search engines understand page content better.

Common Schema Types:

Person, Organization, Place
Product, Article, BlogPosting
Event, CreativeWork, MediaObject
LocalBusiness, Restaurant, Movie

Implementation Methods:

JSON-LD (recommended)
Microdata (HTML attributes)
RDFa (semantic HTML)

Use Cases:

SEO optimization
Search engine rich snippets
Knowledge graph data
Social media sharing

Resource: Schema.org

Open Graph Protocol (OG)

Description: Meta tag standard for enabling rich sharing on social media platforms. Controls how content appears when shared.

Common OG Tags:

og:title - Content title
og:description - Content description
og:image - Preview image
og:url - Canonical URL
og:type - Content type

Example:

<meta property="og:title" content="Article Title">
<meta property="og:image" content="https://example.com/image.jpg">
<meta property="og:description" content="Article description">

Use Cases:

Social media optimization
Link preview customization
Content sharing enhancement
Brand control on social platforms

Resource: Open Graph Protocol

Accessibility & Internationalization

WCAG - Web Content Accessibility Guidelines

Description: Standards for making web content accessible to people with disabilities. Developed by W3C Web Accessibility Initiative.

Compliance Levels:

A: Basic accessibility
AA: Enhanced accessibility (recommended)
AAA: Advanced accessibility (optional)

Key Principles:

Perceivable: Content perceptible to all senses
Operable: Navigation without mouse
Understandable: Clear language and predictable navigation
Robust: Compatible with assistive technologies

Use Cases:

Website development
Application accessibility
Legal compliance
Inclusive design

Resource: WCAG 2.1 Guidelines

BCP 47 Language Tags (RFC 5646)

Description: Standard for language tagging combining ISO 639 language codes with ISO 3166 region codes.

Format: language-region-script

Examples:

en - English (any region)
en-US - English (United States)
en-GB - English (Great Britain)
zh-Hans-CN - Simplified Chinese (China)
zh-Hant-TW - Traditional Chinese (Taiwan)

Use Cases:

HTML language specification (<html lang="en-US">)
Content negotiation
Locale selection
Internationalization (i18n)

Resource: RFC 5646 on IETF

Security Standards

OWASP Top 10

Description: List of the most critical web application security risks, published by Open Worldwide Application Security Project.

Current Top 10 (2021):

Broken Access Control
Cryptographic Failures
Injection (SQL, NoSQL, OS)
Insecure Design
Security Misconfiguration
Vulnerable Components
Authentication Failures
Software and Data Integrity Failures
Logging and Monitoring Failures
Server-Side Request Forgery (SSRF)

Use Cases:

Application security assessment
Secure coding practices
Security testing and audits
Developer training

Resource: OWASP Top 10

Description: EU regulation regulating data protection and privacy for individuals within the European Union and internationally.

Key Principles:

Lawfulness: Data processing must have legal basis
Purpose Limitation: Data used only for stated purpose
Data Minimization: Only collect necessary data
Storage Limitation: Keep data no longer than necessary
Integrity and Confidentiality: Secure data handling
Accountability: Demonstrate compliance

User Rights:

Right to access personal data
Right to be forgotten
Right to data portability
Right to object to processing

Use Cases:

Privacy policy development
Data processing agreements
User consent management
Personal data protection

Resource: GDPR Info

Reference Resources

ISO.org - Official ISO standards organization
IETF Tools - Internet Engineering Task Force RFCs
W3C Standards - Web standards and recommendations
OASIS Standards - Organization for Advancement of Structured Information Standards
OpenStandards.net - Information about open standards

Note: Standards are continuously evolving. Always refer to official documentation for the most current versions and specifications.

Introduction

Geographic & Location Standards

Date, Time & Timezone Standards

Web & Internet Standards

Data Format & Encoding Standards

Identification & Classification Standards

Semantic & Structured Data Standards

Accessibility & Internationalization

Security Standards

Reference Resources

Comments