Pattern rules and implications
	--Pattern classes are all abstract
	--Pattern classes can extend from a pattern abstract

Realization rules and implications
	--You do not have to realize the whole pattern
	--Case 1: You can realize a single subtype of a class (a subtype of a collection or an ordered pair); a branch of a pattern tree
	--Case 2: You can start partway down the branch (i.e. Methodology Pattern starting at Design rather than Methodology) - you need to be sure there is a means of including this within a functional view i.e. something must be able to point to it UNLESS it is the head class
	--Case 3: You can cut off partway down the branch by NOT specifying the target class (leaving it defined as the pattern class) - this results in the inclusion of the relationship in the class BUT the relationship target cannot be specified because the Controlled Vocabulary for Reference/TypeOfClass is a null list (there is no valid content that can satisfy the requirements of Reference, the Reference itself is optional and therefore can be omitted)

Functional View rules and implications
	--A class is included in a Functional View in its entirety 
	--A class can be "restricted" through documentation - in this case the documentation states that a specific class is NOT supported within the Functional View, the class itself is not included in the Functional View. A reference can STILL be included in the instance of the Functional View BUT it MUST be an external reference (to an object external to the instance)