Difference between revisions of "Mapping Rules"
Jump to navigation
Jump to search
Musaab Khan (talk | contribs) |
Musaab Khan (talk | contribs) |
||
| Line 32: | Line 32: | ||
== Category == | == Category == | ||
* Category should list down all the pages in the entity involved. Each page marked with a Category tag of the entity will be available to view at the Category:Entity page. | * Category should list down all the pages in the entity involved. Each page marked with a Category tag of the entity will be available to view at the Category:Entity page. | ||
| − | [https://or.bitplan.com/index.php/Category:City | + | * [https://or.bitplan.com/index.php/Category:City Example for help] |
== Template == | == Template == | ||
Revision as of 10:43, 22 March 2021
Introduction
Certain aspects of the software can be systematically implemented. If it is worth wile to work systematically then some rules should be applied. Otherwise ad-hoc decisions are possible which shall be documented in place. e.g the Source Code
Rules
Each rule boils down to the decision taken for the systematic working of things.
- For each entity type there is a form with the same name. e.g Entity Event has Form:Event.
- Each Entity needs to have 7 technical SMW pages:
- List of
- Help
- Concept
- Category
- Template
- Form
- Properties(1 page per property)
List of
- List down all the items in the entity.
- Must contain everything that the entity is involved in.
- The page can have the functionality to add more.
Concept
Help
Category
- Category should list down all the pages in the entity involved. Each page marked with a Category tag of the entity will be available to view at the Category:Entity page.
- Example for help