Concepts

Resource and Resource Essence

There are many things or people in this world that you pay attention to, are interested in, or want to know about, such as web webpages, books, articles, friends, family, etc. The object or thing that you pay attention to or want to know about and describe is a Resource, also called an Entity.

For a specific resource, there are many specific details, structures, and contents. For example, a very thick book has a lot of contents. If you want to understand each content clearly, it will take a lot of time and most of the time it is unnecessary.

In such cases, you may want to first get a general overview, structure, summary, outline, main parts, key parts, essential parts, important parts, parts you’re interested in, or parts you currently need most.

The most important part or pats you want to focus on and understand are the essence of resource, or Resource Essence, or simply called Essence.

Resource Instance and Resource Instance Essence

The things you pay attention to are constantly in motion and changing. In different periods and environments, they present different states or appearances (e.g., you are different in elementary school, middle school, and university). One of these different appearances is called a Resource Instance, abbreviated as Instance.

The most important parts or the parts you pay attention to of one of these different appearances are called the Resource Instance Essence, or simply Instance Essence.

Although these different appearances are different, they are all presented by this one thing.

The resource instance reflects the specific situation of a resource at a specific time and in a particular environment, and is a specific resource in that specific context.

A resource will experience multiple different periods of movement and change, and different environments, so there will be multiple different resource instances, however these instances are all instances of this resource, and they all originate from and point to this resource.

Since a resource presents different appearances in different periods and environments, the resource instance essences of these instances will also differ.

System and System Essence

As these things continuously change and evolve, they combine with other things to form different Systems (or Resource Systems).

For example, you and your classmates in elementary school formed Class 1 of Grade 1. Clearly, a system is composed of specific resource instances.

A system is a special resource, and also has many details, structures and contents. The most important parts of the system that you pay attention to are the System Essence.

The system is composed of resource instances.

Resource-Instance-System Data Model and Management Method

The data model described above for representing things in the world is called the Resource-Instance-System Data Model (or Resource-Instance-System Model, or simply Resource-Instance-System).

The method of managing data or resources using this data model is referred to as Resource-Instance-System Data Management or Resource-Instance-System Resource Management.

This data model comes from the following basic facts:

1. There are many things in the world or things we need to pay attention to.

2. These things are constantly moving, changing, and interacting with other things, and at different times and in different environments, will have different states or present different appearances.

3. In this process of movement, change and interaction, some things form some systems. Each system, when viewed as a whole, is also a resource, which is also constantly moving, changing, and interacting with other things.

Technical description or definition

The resource-instance-system data model is somewhat similar to classes and objects in object-oriented languages. In fact, this data model introduces object-oriented ideas.

This data model can also be called object-oriented data model. Correspondingly, the resource-instance-system resource (data) management method can also be called object-oriented data management or object-oriented resource management.

Essence and Essence Description

A concise description of a resource essence, a resource instance essence, or a system essence is collectively referred to as an Essence description. If no distinction is made, it can also be called an Essence.

More specifically:

1. A concise description of a resource essence is called a resource essence description. If no distinction is made, it can also be called a resource essence. That is to say, whether it is a resource essence itself or its description, if no distinction is made, it can be called a resource essence.

2. A concise description of a resource instance essence is called a resource instance essence description. If no distinction is made, it can also be called an resource instance essence. That is to say, whether it is a resource instance essence itself or its description, if no distinction is made, it can be called a resource instance essence.

3. A concise description of a system essence is called a system essence description. If no distinction is made, it can also be called an system essence. That is to say, whether it is a system essence itself or its description, if no distinction is made, it can be called a system essence.

The essence description or essence mainly consists of the following fields:

1. URL

   Uniquely identifies a resource.

   For example, the address of a web page.

   In fact, other strings can also be used to uniquely identify this resource, such as the ISBN number of a book.

   You can use the suffix form "#part_string" after the URL to indicate a part of a resource, For example, "https://en.wikipedia.org/wiki/URL#Syntax".

   If you’re simply recording observations or writing articles, and the resources don’t have URLs, you can use any string, such as use the title of the article as a URL. (Internal URLs will be developed in the future, eliminating the need to input URLs for such resources.)

   A resource can be regarded as a system, that is, the resource can be bound to a system through the URL of a resource. After binding, it can be considered that the resource has been transformed into a system.

2. Name

   You can give a resource a short name.

   The name is necessary for the system and uniquely identifies a system.

   Names are optional for resources and resource instances.

   Names are case-insensitive and exclude leading or trailing spaces.

3. Introduction

   A concise description or introduction, which can be an overview, outline, structure, simple description, brief introduction, etc. of a resource, an instance, or a system.

4. Keywords

   Accurate and simple keywords or a list of keyword are used to describe a resource, an instances, or a system more briefly, highlight the key points, and be clear at a glance.

   A Keyword can be a concept, type, tag, etc.

The Name, Introduction, and Keywords are collectively referred to as descriptive fields.

If the descriptive fields of a resource instance are all empty, the descriptive fields of the corresponding resource are displayed by default. This behavior can be understood as a resource instance inheriting from its corresponding resource.

Resource and Entity

In fact, a resource is an entity, and an entity is a resource.

In order to distinguish different types of resources, these different types of resources are collectively referred to as entities.

An Entity is one of the following types:

• Resource
• Resource instance
• System
• Keyword

A keyword can be understood as an entity used to describe other entities.

System Hierarchy

A system consists of resource instances and subsystems.

The structure or content of a system can be:

• A resource instance
• Multiple resource instances
• A subsystem
• Multiple subsystems
• A combination of one or more resource instances and one or more subsystems

A system can have multiple subsystems, and a subsystem can have multiple sub-subsystems, so they form a system tree structure, or a system hierarchy, similar to a file system.

A system can contain multiple subsystems, and this system is the parent system of these subsystems.

A system's subsystems, subsystems of subsystems, ..., are collectively referred to as the descendant systems of this system.

A system's parent system, parent system of parent system, ..., are collectively referred to as the ancestor systems of this system.

The root system is predefined and cannot be edited, but can only be viewed or used.

Its name is predefined, called ROOT, In a system path, the first slash / represents the root system.

The system name of a subsystem must be unique in a parent system (case-insensitive, excluding leading/trailing spaces, focusing on meaning rather than form), used to represent a specific subsystem.

A system in the system tree are represented by its system path, which consist of system names from the root system to the specific system.

For example, /Country/Province/City/District, where the first slash / denotes the root system, and one of other slashes is the system path separator.

Systems and resource instances are similar to folders and files.

The order of a subsystem or instance within a system is called its system order, or simply order.

The system order is calculated by the following algorithm:

1. First, sort all subsystems or instances by their creation time

2. Then the user can manually sort (reorder) these subsystems or instances

3. The final order is the system order