Difference between revisions of "Namespace management"
m (1 revision imported) |
|||
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
Namespace management is the essential skill to master in [[Data Science]]. [[Namespace]] provides the allowable vocabulary to encode [[data]]. | |||
{{LogicModel | |||
|name=Namespace management | |||
}} | |||
In the context of [[MW:MediaWiki|MediaWiki]] and [[MW:Semantic MediaWiki| Semantic MediaWiki]], '''namespace management''' is realized through the use of '''key phrases''' and inter-linked '''[[properties]]''', indexed in the relational database of [[MW:MediaWiki|MediaWiki]]. | In the context of [[MW:MediaWiki|MediaWiki]] and [[MW:Semantic MediaWiki| Semantic MediaWiki]], '''namespace management''' is realized through the use of '''key phrases''' and inter-linked '''[[properties]]''', indexed in the relational database of [[MW:MediaWiki|MediaWiki]]. | ||
[[wikipedia:Namespace management|Namespace management]] is the foundation of mathematics, as [[wikipedia:Henri Poincaré|Henri Poincaré]] once said: | |||
Mathematics is the art of labeling different things with the same name. | |||
This observation is directly applicable in the field of systems engineering, software engineering, and most importantly, reveals the foundational mechanism of how to organize names, using [[wikipedia:number theory|number theory]]. The use of [[number theory]] to analyze [[wikipedia:namespace|namespace]] can be dated back to Euclid's work on reasoning about the infinite supply of [[prime number]]s, and [[wikipedia:Kurt Godel|Kurt Godel]]'s work on the [[wikipedia:Incompleteness Theorem|Incompleteness Theorem]]. | |||
== Naming a page == | |||
A [[Naming system]] could be formalized as a set of ''naming'' rules mapping from ''values'' to ''names'': | |||
<math> Naming: value \to name </math> | |||
To decide the ''naming'' rules, the prerequisite is to figure out how to organize data in a system. Knowledge organization/representation has different styles [[Paper/Knowledge Organization and Representation under the AI Lens]]. In a rule-based [[representation style]], each page entity is matched with rewrite rules based on its patterns. When combining with [[object-attribute-value]], or [[semantic]] representation style, the patterns could be defined by its attributes or relations. | |||
For example, a name for a program could be a string concatenated by its input semantic and output semantic: <code> <nowiki> {{Output}}from{{Input}} </nowiki> </code> turing into <code> Beta Distribution From Mean And SD </code> | |||
==Desired Attributes of [[Namespace management system]] == | |||
* Consistency | |||
* Expressiveness | |||
* Precision | |||
== Resource == | |||
[[Multilingual MediaWiki]] | |||
[https://doc.wikimedia.org/mediawiki-core/ Media Wiki Docs] | |||
[https://gerrit.wikimedia.org/r/Documentation/index.html MediaWiki Gerrit - How to write code] | |||
[https://www.mediawiki.org/wiki/Manual:Code MediaWiki Source Code] | |||
[[MW:Manual:Database layout|MedaiWiki Database Layout]] | |||
== Namespace Management Rules in PKC == | |||
Ideally, all the naming conventions should be configured here and the rules will apply to all the pages in the system. | |||
{| class="wikitable" | |||
|+ Current Naming | |||
|- | |||
! Prefix !! Purpose !! Naming Rules !! Notes | |||
|- | |||
| Jobs || || || | |||
|- | |||
| Resource || || || | |||
|- | |||
| PKC Workflow/Issues || || || | |||
|} | |||
== All types of pages to be managed == | |||
* Activities | |||
* Daily Documents | |||
* Meetings | |||
* Events | |||
<noinclude> | |||
==Related Pages== | |||
[[Definition::Namespace]] | |||
</noinclude> |
Latest revision as of 09:50, 26 February 2022
Namespace management is the essential skill to master in Data Science. Namespace provides the allowable vocabulary to encode data.
Logic Model (Namespace management) Template:LogicModel 02 26, 2022 | ||||||
---|---|---|---|---|---|---|
| ||||||
| ||||||
|
In the context of MediaWiki and Semantic MediaWiki, namespace management is realized through the use of key phrases and inter-linked properties, indexed in the relational database of MediaWiki.
Namespace management is the foundation of mathematics, as Henri Poincaré once said:
Mathematics is the art of labeling different things with the same name.
This observation is directly applicable in the field of systems engineering, software engineering, and most importantly, reveals the foundational mechanism of how to organize names, using number theory. The use of number theory to analyze namespace can be dated back to Euclid's work on reasoning about the infinite supply of prime numbers, and Kurt Godel's work on the Incompleteness Theorem.
Naming a page
A Naming system could be formalized as a set of naming rules mapping from values to names:
To decide the naming rules, the prerequisite is to figure out how to organize data in a system. Knowledge organization/representation has different styles Paper/Knowledge Organization and Representation under the AI Lens. In a rule-based representation style, each page entity is matched with rewrite rules based on its patterns. When combining with object-attribute-value, or semantic representation style, the patterns could be defined by its attributes or relations.
For example, a name for a program could be a string concatenated by its input semantic and output semantic: {{Output}}from{{Input}}
turing into Beta Distribution From Mean And SD
Desired Attributes of Namespace management system
- Consistency
- Expressiveness
- Precision
Resource
MediaWiki Gerrit - How to write code
Namespace Management Rules in PKC
Ideally, all the naming conventions should be configured here and the rules will apply to all the pages in the system.
Prefix | Purpose | Naming Rules | Notes |
---|---|---|---|
Jobs | |||
Resource | |||
PKC Workflow/Issues |
All types of pages to be managed
- Activities
- Daily Documents
- Meetings
- Events