Coblewuz

Additional Notes

A glossary of terms used within the Coblewuz reference, an explanation of how classification decisions are made, and guidance on reading the information architecture of the platform.

Terminology

Terms used in the Coblewuz reference

The following terms appear throughout the Coblewuz reference environment. Understanding how they are used in this context will help you navigate the reference more efficiently.

Reference environment
The reference environment is the collection of pages that make up coblewuz.com. It is distinct from the Coblewuz system itself, which users may access subject to a separate arrangement. The reference environment provides information about the system; it does not constitute the system.
Classification
Classification refers to the assignment of content to a named category based on its subject, type, or intended use. Within the Coblewuz system, classification is applied to reference content so that users can locate related material by navigating to the appropriate category rather than reading all content sequentially.
Access arrangement
An access arrangement is the agreement that allows a specific individual or organisation to use the Coblewuz system beyond the publicly accessible reference. Arrangements are initiated through the enquiry process and confirmed in writing by Coblewuz Systems Ltd. They are personal to the named party and are not transferable.
Enquiry
An enquiry is a submission made through the form on the Enquiry page, or directly by email to [email protected]. Enquiries may seek information about the reference, request access to the system, or raise questions for the support team. The Coblewuz support team reviews all enquiries and responds to the address provided.
Support team
The support team is the group within Coblewuz Systems Ltd responsible for responding to enquiries and managing access arrangements. The team reviews submissions in order and may ask for additional information before providing a response. It does not commit to specific response times.
Structured information
Structured information is content that has been organised according to a defined scheme. Within the Coblewuz context, structured information is content that has been classified, labelled, and arranged so that its relationship to other content is clear. This is the kind of information that the Coblewuz system is designed to hold and present.
Function
A function, as used in the Coblewuz reference, describes a specific capability of the system. Functions are described on the Functions page. The term refers to a defined behaviour or tool within the platform, not to a mathematical or programming function.
Classification Principles

How content classification decisions are made

The basis for classification

Content within the Coblewuz reference is classified on the basis of three considerations: the subject of the content, the type of information it contains, and the user need it is intended to address.

Subject classification groups content that relates to the same aspect of the platform. For example, content about the enquiry process is grouped together regardless of whether it appears on the enquiry page, the overview, or the functions section.

Type classification distinguishes between descriptive content, procedural content, and legal or policy content. Descriptive content explains what something is; procedural content explains how to do something; legal content sets out conditions and obligations.

How classification affects navigation

The classification structure of the reference is reflected in the navigation. The four main sections correspond to the four primary subject areas of the reference: the overall introduction, the platform overview, the functions description, and the enquiry channel.

Within each section, content is further organised by type. Users who are looking for procedural guidance will generally find it later in a section, after descriptive context has been established. Legal and policy content is held in dedicated pages that are accessible from every page of the reference.

This structure is intended to serve both linear readers and those navigating directly to a specific section. Neither mode of reading is assumed to be primary.

Reading the Reference

How to approach the information architecture

  1. Start with the home page if you are new to Coblewuz

    The home reference page is designed as an entry point. It introduces the platform, summarises its purpose, and provides routes to the three other main sections. First-time visitors are encouraged to begin there before exploring in detail.

  2. Use the overview to understand the structure

    The overview page explains how the reference itself is organised. If you find the information architecture confusing, the overview is the appropriate place to seek orientation. It describes what each section contains and how classification decisions have been made.

  3. Consult the functions page for capability detail

    The functions page provides the most detailed account of what the Coblewuz system is able to do. It describes individual capabilities and the access process. Users who have read the overview and are ready to assess whether the system suits their needs should read the functions section next.

  4. Use the enquiry page to make contact

    The enquiry page is the appropriate channel for all communication with the support team. Whether you have a question about the reference or wish to begin an access request, the enquiry form and contact details are the correct starting point.

  5. Review the supplementary pages for further background

    The details, extra, privacy, and terms pages provide background that complements the main reference sections. They are not required reading for all users but contain information that is relevant to specific questions about scope, conditions, and terminology.

Reference and supplementary pages

HomeReturn to the Coblewuz reference home OverviewHow the reference environment is structured FunctionsCapabilities within the Coblewuz system EnquireContact the Coblewuz support team

Also see: Platform details · Privacy · Terms of use