wiki
Enable an agent to recognise a wiki, assess its content and editing state, and determine which contributions or maintenance actions are appropriate.
Bundle → Layer → Finding → Questions Filled
6 bundles · 11 layers · 18 findings · 28 questions
Workspace and page identity Identifies the wiki's subject boundary and the rules that make a page the recognised home for a topic.
Workspace boundary
Establishes which information community and collection this wiki represents.
Wiki sense and remit
Record whether the registered thing denotes a wiki workspace, and identify its intended subjects, readers and exclusions.
- Does wiki here denote the shared information workspace, the editing approach or the software that implements it? definition
- Which subject and audience rules determine whether a proposed page belongs in this wiki? boundary
Canonical page identity
Captures page naming, namespaces and continuity across moves or merges.
Titles, identifiers and redirects
Record how pages are uniquely addressed and how alternate names continue to resolve after editorial restructuring.
- Which title, namespace and identifier rules distinguish separate pages from alternate names for one page? definition
- When a page is renamed or merged, how should links, redirects and revision attribution be preserved? action
Editing and revision control Describes how contributions become shared page content and how their effects can be inspected or reversed.
Edit publication
Captures the route from a proposed change to the version readers encounter.
Save, review and conflict behaviour
Record editor capabilities, publication gates and the handling of overlapping edits.
- Does saving a page expose the change immediately, or does a review or staging step intervene? definition
- How must an agent detect and resolve an edit conflict without overwriting another contributor's changes? action
Revision inspection and restoration
Establishes the available evidence of change and the limits of undoing it.
History, diffs and reverts
Record revision attribution, comparison support, history gaps and permitted restoration operations.
- Which revisions, contributor identities, timestamps and edit summaries are retained and accessible? provenance
- Can an unwanted change be reversed selectively, and what later edits or dependent pages would the reversal affect? action
Linked content and reuse Represents the page relationships and shared components through which the wiki organises information.
Page network
Captures internal links, topic grouping and deliberate gaps in coverage.
Links, categories and uncreated pages
Record how readers discover related pages and distinguish intentionally uncreated targets from broken navigation.
- Which links, categories, indexes or equivalent structures establish the wiki's topic organisation? definition
- How many unresolved internal links are intentional requests for new pages, and how many result from moves, deletion or naming errors? measurement
Shared content dependencies
Identifies reusable content whose changes can propagate beyond its own page.
Templates, inclusions and media
Record whether templates, transclusion, shared media or structured properties are used and which pages depend on them.
- Which reusable components supply content or presentation to other pages in this wiki? definition
- Before changing or deleting a shared component, how can an agent identify and preview its effects on dependent pages? action
Participation and content trust Connects contribution authority, discussion and evidence to the state of shared pages.
Editorial authority
Captures who may act and how disagreements or protected-page changes are handled.
Permissions, protection and discussion
Record workspace roles, page-specific restrictions and the recognised route for obtaining editorial decisions.
- Which roles may edit, move, delete, protect or restore pages, and which page-level restrictions override general access? boundary
- Where should an agent propose a disputed change or request an action it cannot perform directly? action
Evidence and reuse rights
Distinguishes revision attribution from support for claims and permission to reuse material.
Claim support and content origin
Record supporting references, imported-content origins, review markers and applicable reuse terms without treating edit history as verification.
- What references, local records or review decisions support a page's substantive claims, and which claims remain disputed or unverified? provenance
- What licences or permissions cover the page text and embedded media, including material imported from elsewhere? boundary
Wiki maintenance and continuity Describes how the shared corpus remains usable, current and recoverable.
Corpus maintenance
Captures maintenance signals and controls over repeated or automated contributions.
Review backlogs and automated edits
Record stale-page indicators, unresolved maintenance requests and the rules governing bot or bulk edits.
- Which pages lack a substantive review within the wiki's own review interval, and which maintenance requests remain unresolved? measurement
- What preview, rate, approval and rollback requirements apply before an agent performs bulk or automated edits? action
Export and recovery
Establishes whether the wiki can be preserved or restored with its meaningful relationships intact.
Recoverable wiki corpus
Record export and backup coverage for pages, revisions, attachments and shared components, together with evidence of restoration.
- Do available exports or backups include revision history, media, redirects and reusable components, or only current page text? boundary
- What restoration or migration check has demonstrated that pages, links and included content remain usable? provenance
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of wiki this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these kinds and varieties hold for the sense of wiki this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these identifiers and schemes hold for the sense of wiki this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of wiki this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these typical measurements hold for the sense of wiki this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of wiki this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these regional variation hold for the sense of wiki this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of wiki this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Physical world and living systems
- Entry kind
- thing
- Plane
- PHY
- Domain
- PHY.OBJ
- Other names and narrower kinds
- Gamepedia wiki, Phriction, MediaWiki instance, specialized wiki, encyclopedic wiki, dictionary wiki, former wiki, Kilakita Wiki, MediaWiki wiki, bliki, closed wiki, open wiki
What it is Filled
A wiki is a website or networked hypertext system that enables users with appropriate permissions to create, edit and interlink pages through a shared interface, typically retaining a history of revisions.
In scope
- Workspace identity, subject boundary and page organisation
- Collaborative page creation, editing and revision handling
- Internal links, reusable content and navigation conventions
- Contributor permissions, discussion and editorial governance
- Content provenance, maintenance status and recoverability
Out of scope
- Wiki engine source code and software product lifecycle
- Physical servers, storage devices and network infrastructure
- Independent models of subjects described by wiki pages
- The owning organisation's wider structure and activities
- General-purpose document collaboration without a wiki workspace
Why it exists Filled
Enable an agent to recognise a wiki, assess its content and editing state, and determine which contributions or maintenance actions are appropriate.
Distinguishing features Filled
- Its principal content units are addressable pages organised as a navigable, interlinked workspace, rather than primarily chronological posts or message threads.
- Authorised contributors can revise shared pages as maintained resources, rather than only submit comments or separate responses.
- Editing changes the shared body of content; collaboration is not limited to exchanging individually owned files.
- Wiki denotes the content workspace and its editing practices here; an installed wiki engine without such a workspace is a neighbouring software entity.
- Public access, anonymous editing and encyclopaedic subject matter are not required recognition tests; the model must record the actual access and editorial arrangements.
What robots and AI may and may not do Filled
Must not
- Edit to vandalise, promote or mislead.
- Post private information about people.
- Present wiki content as authoritative without checking sources.
- Hide that edits were made by an automated agent where the rules require disclosure.
Only with a human decision
- Mass edits or bot runs on a public wiki.
May
- Read and edit wiki pages where it is authorized, following the site's rules.
- Cite revision history when summarising content.
Moral aspects Filled
- Wikis are shared knowledge that many trust.
- Volunteer communities depend on good faith.
Who is affected
- Readers
- Editors
- People written about
Owners Filled
Steward
The operator of the site; contributors hold rights in their edits under its licence.
Links to other meta-models Filled
parent
- Q131093 - registry parent class
- Q35127 - registry parent class
- Q5155040 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.wiki
- Wikidata: Q171 (https://www.wikidata.org/wiki/Q171)
Direct properties required Filled
- Subject and audience boundary: Declared topics, intended readers and inclusion criteria
- Wiki engine: Supporting software and relevant enabled extensions, if known
- Page addressing convention: Title or identifier rules, namespaces, redirects and canonical addresses
- Contribution access: Anonymous, registered, invited, role-restricted or locally defined combinations
- Revision exposure: Immediately visible, pending review, staged or locally defined workflow
- Revision traceability: History available, partial, unavailable or unknown; attribution and comparison capabilities recorded
- Page protection: Unrestricted within workspace, protected by role, locked or unknown
- Content reuse terms: Applicable licence or policy, including exceptions for imported text and media
- Broken internal link count: Links, with inspection date and treatment of intentional links to uncreated pages
- Content review age: Days since substantive review, per page; unknown where no review is recorded
Recognition required Filled
- Web pages with edit links and a revision history.
Capabilities and actions required Filled
- Locate the canonical page for a topic and inspect its links, revisions and editorial status.
- Create or revise pages within the workspace's topic boundary and contribution rules.
- Compare revisions and propose or perform an authorised restoration of earlier content.
- Repair links, consolidate duplicate pages and maintain redirects while preserving relevant history.
- Raise a discussion or request review when a contribution is disputed or requires approval.
- Assess and export permitted content together with the dependencies and history needed for its intended reuse.
Hazards and failure modes required Filled
- Incorrect or outdated contributions can mislead readers and propagate into downstream decisions.
- Inappropriate access permissions can expose confidential content or permit unauthorized changes.
- Vandalism and unresolved editing conflicts can damage content integrity and disrupt collaboration.
- Malicious page content can attempt to redirect an automated agent beyond its authorized task.
Standards and interfaces required Filled
- Web Content Accessibility Guidelines 2.2, issued by the World Wide Web Consortium, provide accessibility criteria applicable to wiki pages and editing interfaces.
- RFC 9110, HTTP Semantics, issued by the Internet Engineering Task Force, specifies web communication semantics applicable to wikis served over HTTP.
Context of use required Filled
- Wikis support collaborative documentation, reference collections and the maintenance of shared knowledge.
- They are encountered in public communities, educational settings and internal organizational systems.
- Page links and revision histories help contributors organize information, review changes and maintain evolving material.
Sources Filled
- Wikidata item Q171: wiki - identity and sense of the item
- Wikipedia: Wiki - general description of the item
Open questions
- Does the registry intend wiki as a workspace, a software category or an editing method, and is the supplied PHY / PHY.OBJ placement appropriate for that sense?
- Does an existing Vercy world model already cover this concept, requiring a registry link rather than a separate publication?
- Which capabilities are essential to recognising a wiki, and which should remain optional, particularly revision history, discussion pages and transclusion?
- Which authoritative sources should support the eventual researched definition and its boundary with collaborative documents and content management systems?
- Which engine-specific behaviours and local governance rules require separate profiles rather than assertions about all wikis?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q171/spec.json