Description


From monolithic specification, WG are producing more and more multi-documents specifications. Each 
document being having its own life with dependencies with others. Though the division in many 
documents is not necessary a functionnal division (module, profile, level), but it could be a topic 
division. Let's imagine for example that the conformance section of a technology is one document. How 
to make clear where and when the conformance section or sections should go?




Comment


David Marston: "when a document is separate from another with which it was originally thought to be 
associated, it takes on a life of its own. "


Proposal


David Marston: 3. Each Recommendation addresses conformance. Those that don't specify behavior of 
a Class of Product may simply say that they are informative, but beware: even defining terms or stating 
principles can be normative if some other document could cite the terms or principles normatively. If 
your WG issues several Recommendations and some refer normatively to others in the set, try to isolate 
a Class of Product in each Rec and anticipate that other Recs may cite any individual Rec normatively.


Resolution

Solved with the notion of Umbrella Specification.