Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


4.1.  UW NetID stem

A top-level stem:


represents is established to name groups based on the UW NetID namespace.  Under this stem is a stem for each UW NetID, including personal and shared types, and mailing-list ids, but not temp UW NetIDs or other reserved types.  For example,


is a stem whose naming authority is the person holding the personal UW NetID "rlbob".  Examples of groups group names based on that stem are:


The stem based on a shared UW NetID has as a naming authority the owners of that shared UW NetID, or their delegates. Capability to manage groups using that stem is handled consistently with management of access to other resources available to that shared UW NetID.  For example, the shared UW NetID "cac" has the stem:


is the group whose members have the affiliation "student". 

The use of this stem may be extended to support other UWaffiliation-wide group names for which the UW NetID stem is not appropriate.oriented group names, possibly in a hierarchical delegated fashion (e.g. uw_someorg_foo).

The syntax of group names under the UW Affiliation stem is not further constrained. 


is established to name groups with membership based on UW academic courses.   For example:

Wiki Markup  course_\[example_needed\]   course_2005sum-psych101a

The syntax of groups in the academic course stem is:

Wiki Markup
 \[ UWWI has created a convention for this.  This needs to be described algorithmically here. \]

  uwYear + uwQuarter + "-" + uwCurric + uwCrsNo + uwSectID

See for descriptions of the above attribute types.

4.4  Unstructured stem

A stem:


is established to name groups in an unstructured fashion.  Typically names under this stem will be managed by central or departmental support teams rather than end-users.  For example,


is a name in the unstructured stem.  Names under this stem are not themselves usable as stems.

The syntax of group names under the Unstructured stem is not further constrained. 

5.  Exceptions 

There may be existing practice where centrally-managed groups are named with names that do not conform to the scheme defined in sections 3 and 4.  There may also be cases where applications require group names that do not conform to this plan, but it is still appealing to manage such groups centrally.  In these cases exceptions may be granted.  Such group names must still conform to the base UW NetID syntax.  Groups named with exceptional names should still benefit from participation in group management and use operations.  Such names do not participate in the hierarchical naming scheme, however; that is they are not used as stems.  For example:


might be exceptional group names.  They could not be used as stems for other group names.

6.  Representation of group names as URIs