By this point, the webpage has become a surprisingly capable expression of a Knowledge Object.
That matters because it was not where this investigation began. We had assumed that machine-consumable knowledge would eventually require increasingly specialized machine-facing representations. Instead, much of the architecture kept leading us back to the public document.
Native HTML could preserve meaningful structure. Tables could organize comparable assertions. Definitions could establish conceptual meaning. Lists could represent collections. Links could connect related resources. Semantic annotation could make selected distinctions more explicit. Schema.org could provide recognizable vocabulary for public resources where that vocabulary fit.
For many Knowledge Objects, that may be enough.
But there is a distinction we need to preserve before going any further.
The Knowledge Object is not the webpage.
The Knowledge Object is a coherent and bounded representation of something the publisher knows.
The webpage is one way that knowledge can be published.
Usually those boundaries may align closely.
Sometimes they do not.
13.1 When the Page Is Enough
Consider the Apex X5 Mark II.
The publisher knows the camera’s identity, specifications, video capabilities, lens compatibility, manufacturer, important terminology, availability, and sources.
Most of that knowledge belongs naturally in the human publication.
A photographer wants the specifications. There is no reason to remove the camera’s weight from the page and reserve it for machines. Video capabilities belong there too. Compatibility information is useful. Definitions can help readers understand unfamiliar technical concepts. Source information can establish authority.
The page can represent those things effectively because the knowledge and the human information need overlap substantially.
A specifications table can serve both consumers. A definition can serve both. A link to the lens-mount resource can help a person navigate while preserving a meaningful connection between two public resources. Explanatory prose can remain available where facts alone are insufficient.
At some point, the publisher should be willing to stop.
A second representation is not inherently more sophisticated. It creates another artifact that has to remain accurate and aligned with the knowledge already published.
If the important knowledge can be expressed faithfully in the public document without damaging the human experience or leaving consequential meaning behind, the visible page may be all the publication requires.
That is a good outcome.
But the same conclusion does not follow for every Knowledge Object.
13.2 When the Knowledge Is Larger Than the Page
Consider a Medicare plan.
A useful plan page might contain the information a beneficiary is most likely to need: plan identity, important costs, commonly used benefits, availability, performance context, definitions, provenance, and explanations of how the coverage works.
The publisher may know considerably more.
The complete plan knowledge may contain hundreds of benefit and cost-sharing assertions. Different values may depend on network status, service category, benefit period, or other conditions. The service area may contain a large collection of geographic records. Different assertions may have different provenance. Some values may be derived from several source records. Particular facts may have resolution conditions that apply only to those facts.
All of that can belong legitimately to the same Knowledge Object.
It does not follow that all of it belongs visibly on the page.
Imagine publishing hundreds of detailed benefit records simply because the publisher possesses them. The beneficiary looking for the specialist copay now has to navigate through exhaustive state that may be important to the knowledge architecture but irrelevant to the immediate human task.
Or imagine placing detailed derivation lineage beside every calculated value. The provenance may matter. Forcing all of it into the reading experience may make the page substantially worse.
This exposes an important distinction.
The semantic boundary asks what belongs to the Knowledge Object.
The presentation boundary asks what belongs in a particular human experience.
Those boundaries can be different.
That does not mean the publisher should hide useful knowledge from people. Nor does it create a category of facts that somehow belong only to machines.
It means that possessing knowledge and presenting all of that knowledge simultaneously are different responsibilities.
We already accept this distinction in ordinary software.
A retailer may know thousands of facts about its inventory without displaying every database field on every product page. A hospital may maintain detailed operational information while presenting patients with the information relevant to choosing or visiting the facility. A university may possess a much richer model of a degree program than belongs in the first screen an applicant encounters.
The Knowledge Object gives us a way to preserve that distinction without redefining the object around the limitations of the page.
If the publisher knows something that belongs semantically to the object, the knowledge does not stop belonging merely because displaying all of it would make the human publication worse.
The Knowledge Object can therefore be larger than its visible expression.
That leads to a simple idea.
One Knowledge Object can have more than one manifestation.
A manifestation is a published expression of the knowledge, or of a coherent portion of it.
The webpage is a manifestation.
Another structured representation may be another.
Neither becomes the Knowledge Object merely because it contains its knowledge.
The object remains upstream of both.
Knowledge Object
│
┌────────┴────────┐
│ │
Visible Page Other ExpressionThis distinction keeps us from making the same mistake in a new form.
Chapter 4 separated the Knowledge Object from the page because the document boundary was not necessarily the natural semantic boundary.
After discovering how much knowledge HTML can carry, it would be easy to collapse them together again.
We should not.
The page can be an excellent expression of the Knowledge Object without becoming the definition of it.
13.3 Different Representation, Same Knowledge
Once a Knowledge Object has more than one manifestation, a different problem appears.
The representations may differ.
The knowledge cannot.
Suppose a Medicare plan page tells a beneficiary:
Monthly premium: $18
Another representation of the same knowledge might preserve additional dimensions:
Value: 18.00
Currency: USD
Period: monthly
Plan year: 2026
The two representations are not identical.
They should not need to be.
The visible page communicates the premium efficiently to a person. Another representation may preserve distinctions useful for computation, exchange, validation, or another form of consumption.
Both can faithfully express the same assertion.
The same principle applies to granularity.
A human-facing benefits table might present the twenty benefits most useful for comparison while another representation contains the complete benefit set.
A visible percentage might be rounded to one decimal place while another representation preserves the underlying precision.
A page might use a familiar product name while another representation preserves a canonical identifier.
These are differences in representation.
They do not necessarily represent differences in knowledge.
The problem begins when the representations cease to describe the same reality.
Suppose the visible page says:
Monthly premium: $18
while another manifestation says:
Monthly premium: $22
Now the publisher does not have two representations of one assertion.
It has two competing assertions.
The same problem occurs if the visible page identifies a benefit as unavailable while another manifestation identifies it as available, or if one representation describes the 2026 plan year while another silently carries forward 2025 state.
At that point, the Knowledge Object has effectively fractured into separate truth stores.
This gives us a useful test:
If both manifestations were interpreted correctly, would they describe the same state of the world?
They do not need to contain the same amount of information.
They do not need to use the same syntax.
They do not need to serve the same immediate purpose.
But where they represent the same knowledge, they must remain semantically aligned.
That requirement changes how publishers should think about maintaining multiple representations.
The publisher should not maintain an $18 premium for the webpage and another $18 premium for machines.
It should maintain the premium.
The representations follow from that knowledge.
The same is true of identity, relationships, temporal state, provenance, and other assertions that appear in more than one manifestation. Their forms can differ because their consumers and purposes differ. Their authority should not.
This is why the concept of manifestation matters to KNOL without requiring us to descend into the mechanics of manifests, serialization, synchronization, or compilation.
It protects the abstraction we have spent the book developing.
The Knowledge Object is defined by what the publisher knows and by the semantic boundary around that knowledge.
It is not defined by the page that displays it.
It is not defined by a machine representation that carries it.
And it does not multiply simply because the same knowledge is expressed in more than one form.
The page is not the Knowledge Object.
The page is one way the knowledge becomes visible.