[humanmarkup-comment] Re: TC.policy: (updated)

[Ranjeeth Kumar Thunga <rkthunga@humanmarkup.org>]

I've rewritten the document a bit to be clearer
If there are any other ideas, please do bring them up.

Ranjeeth Kumar Thunga



------------
TC.policy (Suggested Guideline)
last updated:  Oct 20 2001
------------------------

These are only suggestions, as sometimes they are not appropriate or
applicable.  Nonetheless, these were brought up by various members over the
course of our discussion to facilitate the discussion process.


PERSONAL INTROCUTION
-----
Please post a personal introduction about yourself to the group.
     1) interests 2) background 3) desired contributions 4) goal for
HumanMarkup effort

Reason:  This helps us know where each contributor is coming from, and what
skills we all have



EXPLICIT DATES
-----
Dates should be in a format internationally understandable:  ex:  Oct 20
2001 or 20 October 2001

Reason:  This prevents confusion between different nationalities (i.e.
10-09-01 may be confusing).



DOCUMENT-CENTRIC
----
-Post in terms of updated revisions of 'proposals' and 'documents', rather
than 'posts', whenever possible.
-Sometimes, however, these aren't appropriate...that is clear.
-Documents should be posted to site, and the administrators will ensure that
they are met.


Reason:  This promotes referenceability and accessibility of material


SUBJECT LINE
----
-Adhere to the subject of the post, and when possible, use the following
format...

    subject:  subtopic:  subtopic:  subtopic:  messagetopic

examples:
    TC.deliverables:   Jan312001:  addRELAXschema
    TC.policy:  footnote:  newmembers


Reason:  This allows easier cataloging of posts.


ONE TOPIC AT A TIME
----
Posts are to address one topic at a time.

Reason:  This allows clearer indexing of ideas when referring back to posts.


TRAILING TEXT
------
-Snip off trailing trailing text <snip/> at the end of a post, to keep them
short and manageable

Reason:  This prevents long posts from getting too unwieldy and unmanageable


PLAIN TEXT
-----
Posts are to be made with embedded plain text OR URL (not .html format, no
attachments)


Reason:  This ensures accessibility of information for text based email
clients.