Best,
Dilini

Better just check the whole bibliography at http://delicious.com/jamesmelzer/pattern_language

• All the components have an id, which is a 1-3 character mnemonic prefix plus a two-digit counter starting at 01.
• All component ids can have variations, with the default case being v0. The name of a variation takes the form: nam01v0.
• Component variations can be described in the library with multiple examples. The first example is implied x0 with subsequent examples named x1, x2 and so on. The full namespace for an example is nam01v0x0.

For many components, the component id (with variation id) is used as the container class name in the HTML code. This is not always the case, although the reason is unclear. I recommend always using the component id as the container class name. This will make components in the field easier to find and maintain.

In a few cases, both the generic component id (nam01) and the id with variation (nam01v3) are used on nested containers, or as separate class calls on the same container. This dual-classing is done when most of the basic layout is handed by the parent, and the variation merely enhances these basics. For example: http://www.sun.com/webdesign/components/pc00.html . In cases where the structure of each variation is entirely different, simply use the variation id as the only class. For example: http://www.sun.com/webdesign/components/g03.html .

All components are categorized by where they occur on the page and where they occur in Sun’s web properties. The categories are used for displaying groups of components, either as an index or as a filter.

Having said that, if it would be helpful to utilize the framework for Pattern Tap for your collection, with some amendments that would help detail each pattern, then let me know, I’d be interested to work with you on something like that.