Glossary · area 13 of 19
The RDF and JSON-LD machinery behind structured data, and the schema.org types a business page actually needs.
45 terms. Each opens its own page with what it can and cannot support, how the scanner measures it, and where it comes up in the guides.
An Internationalized Resource Identifier used to identify resources with Unicode-capable syntax. An IRI can name something without resolving to a retrievable page.
A Uniform Resource Identifier that identifies a resource by name, location, or both. “URI” is broader than a fetchable web URL.
A resource identifier that also supplies a network location and access scheme. A syntactically valid URL may redirect, fail, or identify no durable entity.
An RDF node without a globally reusable IRI. It can represent local structure but cannot reliably join the same entity across pages or datasets.
An RDF value such as text, a number, or a date rather than another identified resource. A literal states a value without creating an independently linkable node.
A declaration of a literal’s value space, such as integer, date, or boolean. A declared datatype can still contain an invalid or misleading lexical value.
Metadata identifying the natural language of a text literal. It supports language-aware processing but does not translate or validate the text.
The relationship type connecting a subject to an object in an RDF triple. Its IRI supplies meaning; a locally invented key without context may not.
The resource from which an RDF statement’s relationship starts. It should be stably identified when claims must merge across documents.
The resource or literal at the receiving end of an RDF statement. A string object cannot carry the identity and relationships of a node object.
An RDF graph associated with an identifier inside a dataset. The name can support grouping or provenance, but RDF alone does not impose one interpretation on it.
The single unnamed graph in an RDF dataset. It is a structural position, not automatically the most authoritative or complete graph.
A default graph plus zero or more named graphs. Dataset structure organizes claims but does not establish that any claim is true.
Combining RDF graphs by taking their triples together. Shared IRIs join claims; blank-node handling and contradictory statements require additional policy.
Transforming graph data into a consistent form for comparison or processing. Normalization does not reconcile semantic contradictions.
A deterministic serialization or labeling of an RDF dataset so equivalent data yields the same byte-level form. It supports hashing, not truth verification.
Replacing compact terms with full IRIs and explicit value structures. Expansion exposes graph meaning but can fail when contexts are unavailable or malicious.
Applying a context to shorten IRIs and simplify a JSON-LD document. Different compact forms can represent the same graph.
Converting nested JSON-LD into a flatter collection of node objects. It aids processing while reducing the author’s original visual grouping.
A JSON-LD context loaded from another URL. It centralizes vocabulary definitions and introduces availability, versioning, and supply-chain risk.
Changing or substituting a JSON-LD context so familiar keys resolve to unintended meanings. Valid JSON can therefore produce a semantically altered graph.
A formally identified class or property within a namespace. Using the term syntactically does not mean the described entity satisfies its intended meaning.
A Schema.org class assigned to an entity, such as Person or Product. A type declaration is a publisher claim, not independent classification.
A named relationship or value used with Schema.org types. Parser acceptance does not guarantee that the property is appropriate or supported by a consumer.
Schema.org guidance naming types with which a property is commonly used. It is inclusive guidance rather than a closed-world validation rule.
Schema.org guidance naming expected value types for a property. Consumers may tolerate alternatives, but inconsistent values reduce interoperability.
A relationship expressed from the opposite direction, such as parent versus child. Declaring both can improve traversal but creates another place for disagreement.
Schema.org markup representing an ordered or unordered collection. It describes listed items but does not prove they are visible, complete, ranked, or available.
An ItemList describing a page’s position in a navigational hierarchy. It should reflect actual site structure rather than a fabricated keyword path.
A Schema.org type for a page as a creative work. It is often the connective node between page content, publisher, primary entity, and breadcrumb.
A broad Schema.org type for article content. It does not establish journalistic quality, originality, authorship, or eligibility for a search feature.
An Article subtype for news reporting. Marking ordinary marketing copy as news changes the claim, not the content’s nature.
An Article subtype for a blog entry. It supports content classification but carries no quality or freshness benefit by itself.
A Schema.org entity representing a product or service offered to users. A Product node without stable identifiers can be confused with variants or similarly named items.
A commercial proposition connecting an item to price, currency, seller, availability, and conditions. Stale offers create confident machine-readable contradictions.
A Schema.org type describing an offered service. It should identify provider and service area where relevant; a generic service name alone resolves poorly.
A Schema.org type for a physical or conceptual location. It gains disambiguating value from address, coordinates, and stable identity rather than type alone.
Structured address components attached to a person, organization, or place. It can normalize location data while still being outdated or internally inconsistent.
Measured: ENTITY_NO_COORDINATES 4.1% · GEO_COUNTRY_MISMATCH 0.1%
Latitude and longitude attached to a place. Precise numbers can be precisely wrong, so they should agree with the stated address and map location.
Measured: ENTITY_NO_COORDINATES 4.1% · GEO_COUNTRY_MISMATCH 0.1%
Structured contact details associated with an entity and purpose. It improves routing only when telephone, language, area served, and contact type are maintained.
A summary of multiple ratings with count and scale. It is not a substitute for visible underlying reviews and can be misleading without denominator and source.
A structured evaluation by an identified author about an item. Markup cannot establish that the reviewer exists, used the item, or expressed the displayed opinion.
The edge connecting a creative work to its creator. A string name supports display; a stable Person or Organization node supports entity resolution.
The edge connecting a creative work to the entity responsible for publication. It identifies responsibility but does not establish editorial independence or authority.
A property identifying the primary entity described by a page or creative work. Overusing it for several unrelated nodes defeats the disambiguation it is meant to provide.