← Back to catalogue
Published

castle

vr.tr.castle · thing-q23413

Let an agent handle castles by name, location, period, type, history and visiting, with sourced information.

Thing Registry Physical world and living systems PHY.PLC

Bundle → Layer → Finding → Questions Filled

4 bundles · 8 layers · 8 findings · 16 questions

Identity Which castle.

Name

Castle.

Name

Castle identity.

  1. Which castle is meant, and where? provenance
  2. Which heritage record describes it? provenance

Type

Form.

Type

Castle type.

  1. What type of castle is it? definition
  2. When was it built? provenance
History Past.

Owners

Holders.

Owners

Owners.

  1. Who built and held the castle? provenance
  2. Which sources document it? provenance

Events

Sieges and changes.

Events

Events.

  1. What major events happened there? provenance
  2. Are legends marked as legends? boundary
Visiting Access.

Opening

Hours and tickets.

Opening

Opening.

  1. When is it open and what does entry cost? provenance
  2. Is booking required? provenance

Access

Accessibility and safety.

Access

Access and safety.

  1. Is step-free access available? provenance
  2. What safety rules apply on walls and ruins? provenance
Protection Heritage.

Status

Listing.

Status

Heritage status.

  1. Is the castle legally protected? provenance
  2. Who manages it? provenance

Conservation

Repairs.

Conservation

Conservation.

  1. What conservation work is under way? provenance
  2. How can the public support it? action

Classifiers Filled

Family
Thing Registry
Category
Physical world and living systems
Entry kind
thing
Plane
PHY
Domain
PHY.PLC
Other names and narrower kinds
diaolou, castle with zuda, alcázar, fortified manor house, tower house, castle farm, country castle, vasaslott, Tuscan tower house, L-plan castle, Z-plan castle, peel tower

What it is Filled

A fortified residence or stronghold, mainly of the European and Middle Eastern Middle Ages, built by nobility or rulers, and similar structures elsewhere such as Japanese castles and Chinese diaolou; many are now heritage sites.

Why it exists Filled

Let an agent handle castles by name, location, period, type, history and visiting, with sourced information.

Distinguishing features Filled

  • Fortified residence
  • Mostly medieval
  • Many types by region
  • Often protected heritage

What robots and AI may and may not do Filled

Must not

  • Present romanticised or unsourced legends as castle history.
  • Encourage climbing walls, entering closed areas or using drones where it is forbidden.
  • Advise digging, metal detecting or removing stone or finds from the site.
  • Help enter a ruin or a privately held castle without permission.

Only with a human decision

  • Any physical work, excavation or survey on a protected structure.
  • Access to closed or unsafe parts of a site.

May

  • Report a castle's history, ownership and opening arrangements from the custodian's sources.
  • Warn visitors about walls, steps, uneven ground and closed areas.
  • Report damage, graffiti or unsafe structure to the custodian or heritage authority.

Moral aspects Filled

  • Falls from walls and ruins seriously injure visitors each year.
  • Castles are protected monuments that unauthorised digging and climbing damage permanently.

Who is affected

  • Visitors, including children
  • The custodian and staff
  • Future visitors and researchers

Owners Filled

Steward

The owner or heritage trust that holds the site, under the national monuments authority.

Master systems

  • National monument and listed building registers

Links to other meta-models Filled

parent

  • Q57821 - registry parent class

related

  • fortification - category
  • palace and fort - buildings
  • heritage site - status
  • nobility - owners

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.castle
  • Wikidata: Q23413 (https://www.wikidata.org/wiki/Q23413)

Direct properties required Filled

  • Enclosed site area: m2 - Measure the horizontal area within a documented defensive boundary using a surveyed plan.
  • Curtain wall height: m - Measure vertically from the adjacent ground level to the surviving wall crest and record the location.
  • Defensive wall thickness: m - Measure perpendicular to the wall faces at a documented position and elevation.

Recognition required Filled

  • Keep, curtain wall, towers
  • Castle types such as motte-and-bailey
  • Palaces and forts are related but different
  • Walls, towers, keeps, gatehouses and moats, often on hills or near water.

Capabilities and actions required Filled

  • identify castle types and periods
  • find history from reliable sources
  • plan visits with access information
  • check heritage protection

Hazards and failure modes required Filled

  • Romanticised or unsourced histories
  • Falls from walls and uneven ground
  • Damage to fragile ruins

Standards and interfaces required Filled

  • Heritage listing and scheduling laws
  • World Heritage Convention for listed castles

Context of use required Filled

  • Historic defence and residence; today heritage and tourism.
  • motte-and-bailey castles
  • concentric castles
  • tower houses
  • Japanese castles
  • alcazars and fortified manors

Sources Filled

  1. Wikidata item Q23413: castle - identity and sense of the item
  2. Wikipedia: Castle - general description of the item

Open questions

  • Should each castle be a separate entry?
  • How should heritage records be linked?
  • How should castle types be classified across regions?

Machine files

Provenance

thing registry research (pass 2) · unreviewed

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