Difference between revisions of "Talk:Organic Design Conventions"
(begin some naming convention stuff) |
m |
||
| Line 3: | Line 3: | ||
;Preserving namespaces | ;Preserving namespaces | ||
| − | When creating an article for something quite specific, like the kitchen of a particular [[Sanctuary]], we wouldn't want to use a name like [[Kitchen]] because the [[Kitchen]] article should remain generic. This is the issue of needing to preserve namespaces. We could use a name like [[Swanson Sanctuary/Kitchen]] instead to denote the fact that we actually mean a specific kitchen. However, this can be quite unwieldy and leads to lots of repeated text. At the [http://developer.mozilla.org/ Mozilla Developer Centre] they use a format which uses the abbreviation of the organisation's name, followed by a semicolon and the article name e.g. "MDC:Frequently Asked Questions". On Organic Design we have been using a slash to show that something is "under" a namespace as is the case with [[ | + | When creating an article for something quite specific, like the kitchen of a particular [[Sanctuary]], we wouldn't want to use a name like [[Kitchen]] because the [[Kitchen]] article should remain generic. This is the issue of needing to preserve namespaces. We could use a name like [[Swanson Sanctuary/Kitchen]] instead to denote the fact that we actually mean a specific kitchen. However, this can be quite unwieldy and leads to lots of repeated text. At the [http://developer.mozilla.org/ Mozilla Developer Centre] they use a format which uses the abbreviation of the organisation's name, followed by a semicolon and the article name e.g. "MDC:Frequently Asked Questions". On Organic Design we have been using a slash to show that something is "under" a namespace as is the case with [[Identity/Summary]]. It still seems a good idea to abbreviate the organisation name, which would give us the format of [[SS/Kitchen]]. |
;Categories | ;Categories | ||
Revision as of 10:13, 1 November 2006
Naming conventions
It would be nice to begin getting some naming conventions documented here.
- Preserving namespaces
When creating an article for something quite specific, like the kitchen of a particular Sanctuary, we wouldn't want to use a name like Kitchen because the Kitchen article should remain generic. This is the issue of needing to preserve namespaces. We could use a name like Swanson Sanctuary/Kitchen instead to denote the fact that we actually mean a specific kitchen. However, this can be quite unwieldy and leads to lots of repeated text. At the Mozilla Developer Centre they use a format which uses the abbreviation of the organisation's name, followed by a semicolon and the article name e.g. "MDC:Frequently Asked Questions". On Organic Design we have been using a slash to show that something is "under" a namespace as is the case with Identity/Summary. It still seems a good idea to abbreviate the organisation name, which would give us the format of SS/Kitchen.
- Categories
