Schema.org
Every saved asset speaks a language every machine understands
Structured data makes your knowledge portable across search engines, AI agents, and any tool — without custom parsers.
What is Schema.org?
Schema.org is a collaborative vocabulary for structured data on the web. Founded in 2011 by Google, Microsoft, Yahoo, and Yandex, it defines type hierarchies and properties that let any machine — search engine, feed reader, AI assistant, knowledge graph — understand content without custom parsing.
Structured data tells machines not just what a page says, but what it is. A blog post, an article, a book review, a recipe — these are not just HTML. Schema.org provides the vocabulary to say so in a machine-readable way embedded directly in the page.
JSON-LD (JavaScript Object Notation for Linked Data) is the recommended serialization: a script tag in HTML that describes content semantically. No special libraries. No build plugins. No runtime cost. The format has been stable for over fifteen years and has never broken backward compatibility.
Why it matters
Most knowledge management tools store your data in proprietary formats. Getting it out requires vendor cooperation — an export button, an API key, a migration script. Even when data is exported, it arrives as a blob that only the original tool could interpret.
Schema.org is the opposite: a public vocabulary that any tool can read without prior knowledge of the tool that created it. When your bookmark is described with Schema.org types, it is readable by search engines for discovery, by feed readers for syndication, and by AI agents for reasoning — all without asking permission.
The vocabulary is genuinely stable. The core types that Blogmarks uses have not changed since their introduction. Your bookmarks described in Schema.org today will be machine-readable by tools that do not exist yet.
How Blogmarks uses this
Blogmarks maps its data model to three Schema.org types: BlogPosting for enriched bookmarks (headline, abstract, keywords, author, dates), BookmarkAction for the curation event itself, and DefinedTerm for the tag taxonomy.
17 of 19 data model fields map natively to Schema.org properties. The two that do not are internal operational metadata — enrichment attempt counters and processing status — that no external vocabulary should govern.
Every bookmark page rendered by Blogmarks includes a JSON-LD script tag with the full Schema.org description. Your knowledge is machine-readable by any tool that lands on the page.
Further reading
- [1]
- [2]R. V. Guha, Dan Brickley, Steve Macbeth. Schema.org: Evolution of Structured Data on the Web. Communications of the ACM, 2016(Vol. 59, No. 2)
- [3]Leslie F. Sikos. Mastering Structured Data on the Semantic Web: From HTML5 Microdata to Linked Open Data. Apress, 2015