Mark L. commented: "By “use case pattern” I am referring to an “archetype”. An archetype is an idealized model of a 
person, object or concept from which similar instances are derived, copied, patterned or emulated. An example might be 
“Compute-intensive Grid” for resource sharing and utilization with vaiations having to do with “static versus “
dynamic”; single versus mulitple data center; single versus multiple domain; etc. These archetype patterns can be 
further composed into things such as “execution” “data access and movement”, etc."

-----

The implication being that the usecases in the current document (v0.3) fail to capture a high enough level of 
abstraction.