Knowledge Architect/Basics/Structure/Location

Location

While uniquely locating resources may seem to also identify them uniquely, resource identification and location are two separate requirements, especially as multiple resources can have a common location, individual resources can be assigned to different locations, and resource location can be time/period-based.

Identifying time and space location is different and separate from resource identification.

Time qualities can refer to points, periods, and durations in time. Fortunately, common practical related standards are readily available, for time referencing, starting with ISO8601 which already integrates references to possibly repeatable time points, periods, and durations.

Time qualities are often determining both in knowledge and reality, for example, as period-qualified resources (e.g. events) typically tend to drive processes (ex: order/invoice).

More so, processes typically also require orchestration (e.g. synchronization, triggering, sequencing, etc.) and rich time management, either through built-in quality rules, or through dedicated orchestrator resources, or both.

Spacial resource locations can be physical (e.g. geo) or virtual (e.g. electronic, ex: URL, system disk path).

Multiple standards and conventions exist for various forms of location (e.g. URL/URI/URN, Xpath, paths, email and postal addresses, postal codes, phone numbers, airport codes, 2D and 3D geo-locators, etc).

Resource references are fundamental knowledge architecture requirements. Integrated time and space location specifications and references associate (e.g. bridge) the virtual nature of knowledge resources to the time/space-based physical world.

As fully integrated standards have not yet been available to structure and generalize resource location referencing, we implemented integrated time/space specifications, while the corresponding standards proposals, are not described in this overview.