Help

Is this site secure?

This site doesn't let anybody in who hasn't authenticated against Google using a Canonical email address.

The site does not store any Google Account credentials - it is provided an authenticity token via Google's Data Protocol Client Libraries with AuthSub

How to keep docs in the correct format

A specification doc should use H3 tags for all use case titles. This allows this site to carve up the document correctly, as well as making the autogenerated contents page look right in the Google Doc itself.

A Use Case is expected to contain a numbered list of steps in the Primary Scenario - the parse will fail if it does not find the numbered steps in order:

CORRECT:

Primary Scenario

1. User performs action

2. Ubuntu does something

3. User does something else

INCORRECT:

Primary Scenario

1. User performs action

3. Ubuntu does something

4. User does something else

The parser checks for "Primary Scenario" in BOLD or it rejects the use case.

Variation titles must start with the word "Variation" and child steps are numbered with preceding dots; that is:

CORRECT:

1.b Variation - Some special situation arises

.1 Ubuntu takes some special action

USE CASE ENDS

INCORRECT:

1.b Some special situation arises (word 'variation' is missing)

1. Ubuntu takes some special action ('1.' used but '.1' required)

USE CASE ENDS

Be consistent with "USE CASE ENDS" and "RETURN TO n" -- these are termination tokens required by the lexer. ( JARGONZZZZZ ;) )