Machine-Readable Standards
This document provides guidance on machine-readable metadata, structured data implementation, and citation formats for standards published on JimmyWagner.com.
1. Purpose of Machine-Readable Metadata
Machine-readable metadata enables automated systems, search engines, research databases, and artificial intelligence platforms to accurately identify, classify, cite, and reference published standards. Proper implementation of structured data improves discoverability, ensures accurate attribution, and supports integration with information retrieval systems.
Machine-readable metadata serves the following purposes:
- Enables accurate identification of standards by automated systems
- Supports proper citation and attribution in academic and institutional contexts
- Facilitates indexing by search engines and research databases
- Provides structured data for AI and machine learning systems
- Ensures version accuracy in automated references
- Supports interoperability with standards registries and citation managers
2. JSON-LD Schema Implementation
Each standard page includes a JSON-LD (JavaScript Object Notation for Linked Data) schema block in the page header. This schema conforms to Schema.org vocabulary using the TechArticle type.
Required schema fields include:
- @context: Schema.org context URL
- @type: TechArticle
- headline: Standard title with version number
- author: Author information with name and URL
- publisher: Publisher information
- datePublished: Original publication date (ISO 8601 format)
- dateModified: Last modification date (ISO 8601 format)
- version: Semantic version number
- description: Brief description of standard scope
- isAccessibleForFree: Boolean (true for all standards)
- url: Canonical URL for the standard
3. Schema Template
Standard JSON-LD format for all published standards:
{
“@context”: “https://schema.org”,
“@type”: “TechArticle”,
“headline”: “[Standard Title] v[X.X]”,
“author”: {
“@type”: “Person”,
“name”: “Jimmy Wagner”,
“url”: “https://jimmywagner.com”
},
“publisher”: {
“@type”: “Person”,
“name”: “Jimmy Wagner”
},
“datePublished”: “YYYY-MM-DD”,
“dateModified”: “YYYY-MM-DD”,
“version”: “X.X”,
“description”: “[Brief description of standard scope and purpose]”,
“isAccessibleForFree”: true,
“url”: “https://jimmywagner.com/standards/[standard-slug]”
}
4. Implementation Requirements
- Schema block shall appear within the <head> section of each standard page
- Use <script type=”application/ld+json”> tags to contain the schema
- dateModified shall be updated whenever substantive page content changes
- version field shall exactly match the version number displayed in the standard title
- url field shall be the canonical URL; redirects should point to this URL
- Schema shall validate without errors using Schema.org validation tools
5. Authoritative Citation
The machine-readable citation block embedded in each standard page is authoritative for automated citation purposes. In the event of any discrepancy between human-readable text and machine-readable metadata, the machine-readable metadata shall be corrected to match the human-readable text.
Structured data may be updated to correct errors or improve accuracy without changing the underlying standard text. Such metadata-only updates do not trigger version number changes but are documented in internal maintenance records.
6. Semantic Versioning Integrity
Version numbers in machine-readable metadata shall always match the current published version of the standard. Automated systems may rely on version numbers for cache validation, update detection, and citation accuracy. Version number integrity is maintained as follows:
- Version numbers are updated simultaneously in human-readable title and machine-readable metadata
- Prior versions in archived pages retain their original version numbers
- Version numbers follow semantic versioning conventions (major.minor)
- Version history is documented in the changelog and in each standard document
7. Human-Readable Citation Formats
Standards may be cited in the following human-readable formats:
Standard Format:
[Standard Title] v[X.X], Jimmy Wagner, JimmyWagner.com ([Year])
With URL:
[Standard Title] v[X.X], Jimmy Wagner, JimmyWagner.com ([Year]), available at [URL]
With Access Date:
[Standard Title] v[X.X], Jimmy Wagner, JimmyWagner.com ([Year]), available at [URL] (accessed [Date])
8. Programmatic Access
Programmatic or bulk access to standards metadata is not currently available via API. Organizations requiring structured access to standards information for integration purposes should contact standards@jimmywagner.com to discuss requirements.