Editing Pages (1YC)
- If you see a typo, fix it! (1YD)
- When annotating a Wiki page, edit the page, add your comment, and sign it with two dashes followed by your Wiki name a slash and then a date (or a date/time stamp), all in a pair of parenthesis.. For example, "See the end of this suggestion. (--JaneDoe / 2004.08.15 20:18 PST)" (1YE)
- To keep the page structure consistent within this wiki, it is advisable that, when starting a new page, for one to (a) take a look at the wiki Page Index first, and try to follow the structure and pattern of how pages are named and structured; and/or (b) consult with the ColabWikiAdmin for advice (especially if one is just beginning to create new content for this wiki.) (30BP)
- If you noticed that a page has been vandalized, please restored the content (see details at WikiSpam) and notify the ColabWikiAdmin. (2TAE)
Page Naming Conventions (1YF)
- Wiki pages related to major categories or subjects should best be prefixed accordingly, e.g. "UblOntologyRepository", "UblOntologyLanguage". (1YG)
- When specifying dates or date/times, please express them in a format in the order of the significance of the elements (like yyyy.mm.dd_hh:mm). For example: (1YJ)
- "notes taken by ppy / 2004.08.15 20:18 PST" (1YK)
- ConferenceCall_2004_08_15 (1YL)
- This wiki supports one level of sub-pages (which can be invoked by placing a slash before the WikiWord of the sub-page.) Please use sub-pages, whenever there are possibilities the the same WikiWord identified pages may cause ambiguity when placed at the top level. (1YH)
- for example, if the community runs multiple projects, and each project will run their own meetings and conferencd call schdeule, then it would be prudent to put, say, the meeting-calling wiki pages as sub-pages to each project. (1YI)
- in the current case of the COLAB - collaborative work environment, where multiple communities are working side by side, it is all the more important that communities use prefix their pages with their CoP / CoI name or use subpages to publish content with names that could be by other communities too. (3B1X)
- for example, if you need to have your CoP or CoI charter on one page, then rather than creating a page called "Charter" and place your content on it, you should, for example, use something like "SICoP_Charter" or "SICoP/Charter" (3B1Y)
- or, for example, if SICoP is having a conference call on 11-Oct-2006, it is suggested that the agenda, proceedings, etc. for that session be published in a page named: "SICoP/ConferenceCall_2006_10_11" (since other CoP's or working groups could very well have their conference calls on that same day too.) (3B1Z)
Accessibility Considerations (1YM)
Compliance with Section 508 (of the August 1998 amendment of the U.S. Rehabilitation Act) is required for all US federal government CWE sites, and highly recommended for all other sites. Users (which will be the content developers) should review the http://www.section508.gov/ site for more details, and to make sure their work meets with requirement. (1YN)
When users author content that involve non-text elements to convey information, like color pallettes, images & graphics, multimedia presentation, image maps, tables, frames, and when making use of scripts, plug-ins, applets, forms and/or timed responses, they should take responsibility to ensure section 508 compliance, if it is so required. Section 1194.22 - Web-based Internet Information and Applications of the Section 508 VPAT should be referenced. (202)
Wiki pages should generally have no problem with Seciton 508 compliance as the pages are essentially text based. In the case of images, which will be displayed whenever a compatible image element (e.g. a link to a png, gif or jpg file) shows up within the body of the page. To ensure compliance, users should properly caption such linked image elements. For example: (1YO)
Picture of the CWE system being demonstrated. (1YP)
Maintained Pages (1YQ)
While part of the power of wiki's is that anyone who can read a page can also write to it, there are circumstances, when the editing work is better done by one (or a small number of) individuals. If, for some reason, a person is to take full responsibility in maintaining a particular page, please make sure one clearly states that as part of the footer. Include at least the following information: (1YR)
- This page is maintained by "Your Name" (1YS)
- Page last updated (1YT)
- Describe your desired content update instructions, like: (1YU)
History Section (1YX)
There will be times when mailing list discussions lead to important changes that either directly or indirectly affect the Wiki. For example, we may discuss a new approach. Once we reach a decision, we would have to make a major update to a particular Wiki page. When this happens, it's good practice to create a History section on that page, and include a link to the relevant discussion (at the discussion forum archives.) That way, we capture why things are the way they are. (1YY)