← Back to catalogue
Published

fortification

vr.tr.fortification · thing-q57821

Let an agent handle fortifications by type, period, location, condition and heritage status, including safe and respectful visiting.

Thing Registry Physical world and living systems PHY.PLC
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

4 bundles · 8 layers · 8 findings · 16 questions

Identity Which fortification.

Type

Castle, fort, wall.

Type

Type.

  1. What type of fortification is it? definition
  2. From which period? provenance

Location

Site.

Location

Location and name.

  1. Where is it, and what is it called? provenance
  2. Who owns it? provenance
History Use and events.

Construction

Building phases.

Construction

Building history.

  1. When and by whom was it built and altered? provenance
  2. Which sources document it? provenance

Events

Sieges and use.

Events

Historical events.

  1. Which events happened there? provenance
  2. How are they interpreted? boundary
Condition and protection Heritage care.

Condition

State.

Condition

Condition.

  1. What condition is it in? measurement
  2. Are parts unsafe? boundary

Protection

Listing.

Protection

Protection status.

  1. Is it protected, at which level? provenance
  2. Is metal detecting or excavation permitted? boundary
Visiting Access and safety.

Access

Hours and routes.

Access

Visiting information.

  1. When and how can it be visited? action
  2. Is it accessible? measurement

Safety

Hazards.

Safety

Visitor hazards.

  1. Which hazards should visitors know about? boundary
  2. Are there closed areas? boundary

Classifiers Filled

Family
Thing Registry
Category
Physical world and living systems
Entry kind
thing
Plane
PHY
Domain
PHY.PLC
Other names and narrower kinds
tarisznyavár, tulou, Gompa, fortified ecclesiastical site, principia, heliographic post, agadir, De Redin towers, Cuirasse Decauville, defence work, lunette, coffre

What it is Filled

A military construction or site designed for defence, such as castles, forts, walls, earthworks and fortified religious sites, from ancient to modern times.

Why it exists Filled

Let an agent handle fortifications by type, period, location, condition and heritage status, including safe and respectful visiting.

Distinguishing features Filled

  • Built for defence
  • Many types across periods and cultures
  • Often protected heritage
  • Some contain unexploded ordnance or hazards

What robots and AI may and may not do Filled

Must not

  • Damage, deface or dig at a protected historic fortification.
  • Help anyone loot artefacts from a fortified site.
  • Disclose sensitive details of active military defences.
  • Lead visitors onto unsafe walls or ruins.

Only with a human decision

  • Restoration or alteration work on a listed fortification.

May

  • Describe fortifications and their history from archaeological and historical sources.
  • Monitor the condition of historic fortifications for those who care for them.

Moral aspects Filled

  • Historic forts are shared heritage, often with painful histories of conquest.
  • Fortified religious sites are still sacred to some communities.

Who is affected

  • Heritage communities
  • Visitors
  • Local residents

Owners Filled

Steward

The state heritage body or the site's owner; the armed forces for active defences.

Master systems

  • National heritage registers

Links to other meta-models Filled

parent

  • Q811979 - registry parent class
  • Q97095925 - registry parent class

related

  • built structure - military
  • heritage - monument
  • conflict - purpose

contains

  • wall and tower - elements

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.fortification
  • Wikidata: Q57821 (https://www.wikidata.org/wiki/Q57821)
  • heritage listing number: jurisdiction-specific protected sites

Direct properties required Filled

  • wall thickness: 1-10 m - varies widely

Recognition required Filled

  • Defensive walls and towers
  • Moats and earthworks
  • Heritage signage
  • Walls, towers, ditches, bastions and gates; forms range from hill forts to star forts and fortified churches or tulou.

Capabilities and actions required Filled

  • visit and study it
  • conserve and restore it
  • protect it as heritage
  • excavate it, under permits

Hazards and failure modes required Filled

  • Falls from walls
  • Collapse of ruins
  • Unexploded ordnance at modern sites
  • Illegal metal detecting

Standards and interfaces required Filled

  • Heritage protection law
  • Archaeological excavation permits
  • UNESCO World Heritage

Context of use required Filled

  • Historically defence; today mainly heritage, tourism and research.
  • castles
  • forts and star forts
  • city walls
  • earthworks and hill forts
  • fortified religious sites and tulou
  • military camps such as Roman principia

Sources Filled

  1. Wikidata item Q57821: fortification - identity and sense of the item
  2. Wikipedia: Fortification - general description of the item

Open questions

  • Should fortification types be separate entries?
  • How should visitor safety be recorded?
  • The registry entry has merged aliases such as gompa and heliographic post; should they be split off?

Machine files

Card as JSON Specification Card backlog vercy.card/1

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-q57821/spec.json