Difference between revisions of "Common Namespace Management Model"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
And [[MU]] uses the following namespaces | And [[MU]] uses the following namespaces | ||
* This will be defined locally by the domain experts. So, maybe, we will first reserve the top namespace, called: '''Domain'''. | * This will be defined locally by the domain experts. So, maybe, we will first reserve the top namespace, called: '''Domain'''. | ||
* The namespaces related to [[MU]] should maximize the use of [[Semantic Tags]] and [[Semantic Result Format]] features to help navigate data. | |||
And [[Inter-Organizational Workflow]] uses these reserved namespace such as: | And [[Inter-Organizational Workflow]] uses these reserved namespace such as: | ||
* Exchange/Trade, Refusal, '''Signature''', Staking, Transport, '''Payment'''/Reimbursement... | * Exchange/Trade, Refusal, '''Signature''', Staking, Transport, '''Payment'''/Reimbursement... | ||
Revision as of 11:53, 14 March 2022
First, it borrows the namespace convention of MediaWiki and Semantic Mediawiki. That means:
- Main, Template, Module, MediaWiki are reserved already. In particular, the word Category is also an important reserved word, for a very convenient namespace.
- Semantic Mediawiki defines a namespace for namespaces, called Property, using two colons(::) as the delimiter to denote the user defined namespaces. So that we can use relational database engine to identify and manipulate all these namespaces.
Then, PKC occupies the following names: PKC
And MU uses the following namespaces
- This will be defined locally by the domain experts. So, maybe, we will first reserve the top namespace, called: Domain.
- The namespaces related to MU should maximize the use of Semantic Tags and Semantic Result Format features to help navigate data.
And Inter-Organizational Workflow uses these reserved namespace such as:
- Exchange/Trade, Refusal, Signature, Staking, Transport, Payment/Reimbursement...