← Back to catalogue
Published

Point of Interest

vr.wm-plc-006 · wm-plc-006-point-of-interest

Describe one identifiable POI for discovery and orientation through qualified assertions about a place or represented feature.

World Models Physical world and living systems PHY.PLC.POI

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 12 findings · 36 questions

Identity and naming Persistent POI identity and culturally qualified naming remain distinct.

Identity and represented feature

Keep POI identity, source listing ID and represented-feature identity separate. Similar names, shared coordinates and common addresses only suggest matches.

Persistent POI identity and reconciliation

Keep POI identity, source listing ID and represented-feature identity separate. Similar names, shared coordinates and common addresses only suggest matches.

  1. Which master identifier and namespace identify this POI independently of the feature and source listings it describes? identity
  2. What makes this a single POI subject rather than a catalogue, event, organization or moving asset? definition
  3. Which evidence supports or rejects an asserted duplicate, split or successor relationship? validation

Names and language

Keep names, aliases, historic forms and display labels as attributed values. Display preference is not official status; language tags do not prove equivalence.

Localized labels and naming claims

Keep names, aliases, historic forms and display labels as attributed values. Display preference is not official status; language tags do not prove equivalence.

  1. Which labels, languages and scripts describe the POI, including an explicit unnamed or unknown case? classification
  2. What evidence and jurisdiction qualify any official-name claim? authority
  3. How are former names, transliterations and disputed alternatives retained and selected for a requested language? temporal
Location and place context Spatial representations and approach references require explicit meaning and quality.

Spatial representation

Distinguish display point, entrance, extent and relative indoor anchor. Coordinate corrections need not create a new POI. Unknown geometry cannot silently become a fabricated coordinate.

Geometry roles and uncertainty

Distinguish display point, entrance, extent and relative indoor anchor. Coordinate corrections need not create a new POI. Unknown geometry cannot silently become a fabricated coordinate.

  1. Which location representation is used for display, extent or arrival, and what CRS, axis order and level qualify it? spatial
  2. How was each position observed or transformed, with what uncertainty and conditions? measurement
  3. When must a geometry projection be refused because its role, coordinate system or accuracy is unsuitable? constraint

Place context and approach

Record typed containment, adjacency and address references without inferring legal occupancy, parcel rights or a traversable route. An entrance may have a distinct access profile from the POI.

Qualified spatial links and entrances

Record typed containment, adjacency and address references without inferring legal occupancy, parcel rights or a traversable route. An entrance may have a distinct access profile from the POI.

  1. Which places, buildings, parcels or indoor spaces contain or adjoin this POI, according to which evidence? relationship
  2. Which address, entrance or approach references serve each intended arrival context? composition
  3. Which physical access restrictions or unknown conditions apply at each entrance independently of map visibility? access
Description and recognition Capabilities, categories and recognition evidence support discovery without guaranteeing use.

Categories and amenities

Use versioned category assertions and conditional amenities. A facility description does not execute a service, guarantee availability or confer permission.

Classification and possible visitor uses

Use versioned category assertions and conditional amenities. A facility description does not execute a service, guarantee availability or confer permission.

  1. Which category scheme, version and terms classify this POI and what competing assignments remain? classification
  2. What amenities or visitor activities are described, with which conditions, restrictions and applicability? requirement
  3. Which unsupported accessibility, safety or service claims must remain unknown or be delegated to a qualified profile? exception

Recognition and observations

Identify signs, imagery and observation references without treating a matching label or image as proof of identity. Observations are time-bound and may be stale or conflicting.

Evidence for on-site recognition

Identify signs, imagery and observation references without treating a matching label or image as proof of identity. Observations are time-bound and may be stale or conflicting.

  1. Which signs, images or landmarks help distinguish this POI from nearby or similarly named places? evidence
  2. Who observed each recognition cue, when and by what method under which conditions? provenance
  3. What changes or contradictory observations make the recognition evidence stale or unsafe to rely on? quality
Availability and change Schedules, observed availability and lifecycle changes have separate semantics.

Schedules and visitor availability

Separate recurring local hours from instants, exceptional closures and real-time availability. Missing schedules mean unknown. Natural landmarks need not have operator opening hours.

Qualified opening schedules and exceptions

Separate recurring local hours from instants, exceptional closures and real-time availability. Missing schedules mean unknown. Natural landmarks need not have operator opening hours.

  1. What regular hours, local time zone and validity interval apply to the place or specific service? temporal
  2. Which holiday, seasonal, overnight or temporary exceptions override a schedule, and with what precedence? exception
  3. How does the evidence distinguish scheduled opening from observed availability, appointment-only use or unknown status? state

Lifecycle and temporal continuity

Separate feature existence, operational status and listing publication state. Closure does not erase a landmark; relocation or operator replacement needs an explicit identity decision.

POI existence, listing status and changes

Separate feature existence, operational status and listing publication state. Closure does not erase a landmark; relocation or operator replacement needs an explicit identity decision.

  1. Which evidence distinguishes proposed, active, temporarily closed, ceased, historical and retired listing states? lifecycle
  2. Which rename, relocation, closure or operator-change event affects the POI and what identity decision follows? event
  3. What are the separate validity, observation and ingestion times for a changed assertion? temporal
Stewardship and evidence Accountable roles and assertion lineage support controlled review.

Stewardship and contacts

Keep catalogue custodian, contributor, place operator, property holder and naming authority separate. A contact channel or source attribution grants no update rights.

Role-qualified responsibility and update authority

Keep catalogue custodian, contributor, place operator, property holder and naming authority separate. A contact channel or source attribution grants no update rights.

  1. Which role stewards the POI record and which separately referenced roles operate or hold rights in the place? ownership
  2. What mandate permits each contributor to propose, review or approve a POI change? authority
  3. Which contact details can be exposed for the stated purpose without exposing private resident or contributor data? privacy

Assertion provenance and review

Link assertions to sources, revisions and review decisions. A source identifier, digest or contributor role cannot establish factual accuracy.

Evidence lineage and competing assertions

Link assertions to sources, revisions and review decisions. A source identifier, digest or contributor role cannot establish factual accuracy.

  1. Which source entity and derivation activity support each POI assertion? provenance
  2. How are incompatible source values retained and a preferred projection selected without deleting the dispute? decision
  3. What evidence age, completeness or verification threshold makes a POI assertion fit for its intended use? quality
Rights and exchange Rights-aware projections preserve limitations and external model boundaries.

Rights and controlled disclosure

Apply source-specific reuse rights and purpose-specific release decisions. Public discovery is a controlled projection; sensitivity can require suppression. Historical continuity does not require perpetual personal-data storage.

Licensing, sensitive locations and disposal

Apply source-specific reuse rights and purpose-specific release decisions. Public discovery is a controlled projection; sensitivity can require suppression. Historical continuity does not require perpetual personal-data storage.

  1. Which location or attachment details require restricted, generalized or suppressed views for each audience? security
  2. Which licenses, attribution duties and source restrictions govern each reused description, geometry or image? requirement
  3. What retention, correction and disposal rules govern POI assertions, evidence and generated views? retention

Profiles and interoperability

Bind a local profile before exporting. OGC conceptual alignment, vocabulary use and GeoJSON serialization require separate implementation checks. Missing mandatory target fields cause refusal, not invented values.

Loss-aware projections and acceptance

Bind a local profile before exporting. OGC conceptual alignment, vocabulary use and GeoJSON serialization require separate implementation checks. Missing mandatory target fields cause refusal, not invented values.

  1. Which pinned target profile maps POI identity, geometry, payloads and provenance without conflating the represented feature? interoperability
  2. Which acceptance fixtures test duplicate locations, unnamed places, uncertain geometry, overnight hours and restricted entrances? validation
  3. What authority, current revision and validation evidence are required before preparing a recipient-scoped local export? process

Classifiers Filled

Family
World Models
Category
Physical world and living systems
Entry kind
entity
Navigation path
NAV.PHY.PLC.POI
Domain
PHY.PLC.POI
Industry
Cross-industry
Tags
pointinterestphy.plc.poi
Also called
U7

What it is Filled

A persistent POI subject with its own identifier, source-qualified synopsis and references to independently mastered features. It is not a whole catalogue, an address register or the physical asset itself. A POI can describe an area, line or indoor location; the word point does not require point-only geometry. Multiple listings may describe the same feature without sharing record identity.

In scope

  • POI identity, localized labels, category assertions and represented-feature references
  • Location roles, geometry quality, entry context, observed recognition and qualified visitor information
  • Listing lifecycle, provenance, stewardship, rights, selective disclosure and proposed local projection operations

Out of scope

  • Address assignment, street naming, postal formatting, coordinate reference system definition and geocoding service execution
  • Building, parcel, indoor-space, organization, event and gazetteer master lifecycles
  • Route planning, real-time navigation, physical entry control, booking, payments, access certification and continuous tracking of moving persons or assets

Why it exists Filled

Describe one identifiable POI for discovery and orientation through qualified assertions about a place or represented feature.

Distinguishing features Derived, awaiting review

  • Unlike WM-XCT-010 Location Referencing / Address: Reference an address or location designation when available. No mandatory civic address and no address assignment or retirement powers are inherited from legacy U7.
  • Unlike WM-XCT-033 Geometry / Coordinate Reference: Keep POI-specific location role and observations; reference geometry and CRS definitions rather than owning transformation engines or reference-system registries.
  • Unlike WM-PLC-010 Gazetteer Place: A gazetteer entry is an external place/name authority. POI labels can be descriptive or unofficial; record disputed name assertions without adjudicating sovereignty.
  • Unlike WM-BLT-001, WM-BLT-002, WM-PLC-002 and WM-PLC-009: Building, premises, parcel and indoor-space references are optional candidate bindings. A POI synopsis and a represented feature have distinct identities and revision histories.
  • Unlike Legacy U7 Address and Location Referencing: Legacy material is reconciled as broad predecessor input. Only its POI identity, category, language, lifecycle and qualified geocode concerns survive locally. Address registrar authority and old conformance assertions are not inherited.

Note: Derived from boundary notes against neighbouring models.

What robots and AI may and may not do Derived, awaiting review

Must not

  • Restricted or dangerous facilities remain at policy-level description; refuse operational details that enable harm.
  • Deny undisclosed access by default.

Only with a human decision

  • Prefer role-based contact references and minimize person-linked data; review source rights before reproducing imagery or descriptions.

May

  • Resolve a qualified POI reference: Proposed operation, not implemented. Resolve an exact namespace and identifier; similarity may return candidates but never automatically merge identities.
  • Record a location assertion: Proposed operation, not implemented. Append qualified geometry or an unresolved location reason, preserving role, source and uncertainty.
  • Record availability evidence: Proposed operation, not implemented. Append schedule or observed availability evidence and distinguish recurring local time from actual observation.
  • Record an identity review: Proposed operation, not implemented. Record an authorized duplicate, relocation or successor decision with evidence and retained aliases.
  • Record a POI state assertion: Proposed operation, not implemented. Append closure, proposed, historical or retirement evidence with separate listing and represented-feature states.
  • Prepare a scoped POI projection: Proposed operation, not implemented. Create a local export under a pinned mapping and license/access decision, reporting every omitted or generalized field.

Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.

Moral aspects Derived, awaiting review

  • Select applicable privacy, naming, accessibility and licensing profiles before operation.
  • Public POI discovery does not authorize entry, navigation, surveillance or unrestricted distribution of precise sensitive locations.
  • Restricted or dangerous facilities remain at policy-level description; refuse operational details that enable harm.
  • Jurisdiction-specific naming, language selection, privacy, accessibility and source-license applicability need profile review.

Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.

Owners Filled

Steward

Name the accountable catalogue custodian role, namespace and authorized purpose

Roles

Catalogue custodian
Own local namespace, purpose and retention decisions
Contributor
Submit attributed evidence within delegated scope
Semantic reviewer
Review identity continuity, conflicting assertions and profile mappings
Access and rights reviewer
Approve recipient scope, licensing and sensitive-location treatment
Consumer
Respect limitations and report stale or ambiguous POI assertions

Links to other meta-models Filled

references

  • WM-XCT-010 - Candidate binding requiring neighbor/version review. Optional address/location designation reference; assignment and postal operations remain external.
  • WM-XCT-033 - Candidate binding requiring neighbor/version review. Optional geometry/CRS binding; geometry role and observed quality remain POI assertions.
  • WM-PLC-010 - Candidate binding requiring neighbor/version review. Optional gazetteer and name authority reference, not identity equivalence.
  • WM-BLT-001 - Candidate binding requiring neighbor/version review. Optional represented building feature with independent master identity.
  • WM-BLT-002 - Candidate binding requiring neighbor/version review. Optional represented premises feature with independent lifecycle.
  • WM-PLC-002 - Candidate binding requiring neighbor/version review. Optional parcel context; location does not prove land rights.
  • WM-PLC-009 - Candidate binding requiring neighbor/version review. Optional indoor-space and level context; no indoor routing ownership.

aligned

  • OGC POI 1.0 - Selected conceptual alignment. Required geometry/contact fields and payload tests need an implementation profile; incomplete local records are not conformant instances.
  • Schema.org Place and OpeningHoursSpecification - Descriptive projection only; no equivalence between missing schedule and confirmed closure.
  • GeoJSON RFC 7946 - Geometry exchange only; explicit longitude-latitude order and mapped uncertainty metadata.
  • PROV-O - Attribution and derivation mapping, not certification of source truth.

neighbor

  • WM-XCT-010 Location Referencing / Address - Reference an address or location designation when available. No mandatory civic address and no address assignment or retirement powers are inherited from legacy U7.
  • WM-XCT-033 Geometry / Coordinate Reference - Keep POI-specific location role and observations; reference geometry and CRS definitions rather than owning transformation engines or reference-system registries.
  • WM-PLC-010 Gazetteer Place - A gazetteer entry is an external place/name authority. POI labels can be descriptive or unofficial; record disputed name assertions without adjudicating sovereignty.
  • WM-BLT-001, WM-BLT-002, WM-PLC-002 and WM-PLC-009 - Building, premises, parcel and indoor-space references are optional candidate bindings. A POI synopsis and a represented feature have distinct identities and revision histories.
  • Legacy U7 Address and Location Referencing - Legacy material is reconciled as broad predecessor input. Only its POI identity, category, language, lifecycle and qualified geocode concerns survive locally. Address registrar authority and old conformance assertions are not inherited.

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Filled

  • Authoritative master-system identifier plus namespace and revision
  • Governed global identifier or IRI
  • Dimension-assigned UUID or ULID

Direct properties required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Recognition required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Filled

  • Resolve a qualified POI reference: Proposed operation, not implemented. Resolve an exact namespace and identifier; similarity may return candidates but never automatically merge identities.
  • Record a location assertion: Proposed operation, not implemented. Append qualified geometry or an unresolved location reason, preserving role, source and uncertainty.
  • Record availability evidence: Proposed operation, not implemented. Append schedule or observed availability evidence and distinguish recurring local time from actual observation.
  • Record an identity review: Proposed operation, not implemented. Record an authorized duplicate, relocation or successor decision with evidence and retained aliases.
  • Record a POI state assertion: Proposed operation, not implemented. Append closure, proposed, historical or retirement evidence with separate listing and represented-feature states.
  • Prepare a scoped POI projection: Proposed operation, not implemented. Create a local export under a pinned mapping and license/access decision, reporting every omitted or generalized field.

Hazards and failure modes required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Derived, awaiting review

  • OGC Points of Interest Conceptual Model Standard 1.0
  • PROV-O: The PROV Ontology

Context of use required Filled

  • No universal civic-address, official-name, opening-hours or public-entry requirement.
  • Disputed names and territorial context remain source-qualified; English research prose does not restrict instance label languages.
  • Coordinate and time conventions are profile-bound; no local CRS or time zone is silently assumed.

Sources Filled

  1. OGC Points of Interest Conceptual Model Standard 1.0 - Open Geospatial Consortium
  2. Place - Schema.org community
  3. The GeoJSON Format - Internet Engineering Task Force
  4. PROV-O: The PROV Ontology - World Wide Web Consortium
  5. Date and Time on the Internet: Timestamps - Internet Engineering Task Force
  6. OpeningHoursSpecification - Schema.org community
  7. Tags for Identifying Languages - Internet Engineering Task Force
  8. Spatial Data on the Web Best Practices - World Wide Web Consortium and Open Geospatial Consortium

Open questions

  • Run direct source checks outside the sandbox, pin vocabulary versions and review dependencies, errata, source status and exact claim support before promotion.
  • Build adopter profiles and executable fixtures covering duplicate co-located POIs, relocation, missing names/addresses, uncertain geometry, overnight/DST schedules, restricted entrances and disposal of sensitive payloads.
  • Restore an independent external provider review before canonical or publishable-draft promotion.
  • Independent external review is absent under the owner-authorized waiver.
  • Direct HTTP and current-version checks are pending outside the sandbox; browser retrieval is not a measured HTTP result.
  • Executable nested schemas, OGC implementation/payload conformance, neighbor-version bindings and mapping fixtures are not implemented.
  • Jurisdiction-specific naming, language selection, privacy, accessibility and source-license applicability need profile review.
  • Mobile-object tracking, route accessibility certification, live occupancy, booking and pricing are outside this POI boundary.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-plc-006-point-of-interest/spec.yaml