That'd be fine with me Tim. As far as I'm concerned version 2 offers reasonable value as-is. It would benefit from a once-over by Arofan on his section, and by an overall twice-over where we give more concrete mapping from the recommendations to page/paragraph in the target document (CCTS 1.8). There is one candidate topic I'd like to strategize with the rest of the team. We spent a lot of effort figuring out the difference between names for model elements versus dictionary entry names. The latter as we learned have to be fully qualified whereas the former constitute the segments of the full names. Our initial confusion around this subject (failure to differentiate the two naming perspectives) caused us to attempt to apply fully qualified dictionary entry names to all the model elements (e.g. we tried to give a class a name that included ObjectTerm.PropertyTerm.RepresentationTerm )... It was later that we realized that a class has only an ObjectTerm and that it's properties have property terms and that when one makes a dictionary entry for the property it should have ObjectTerm.PropertyTerm to distinguish the dictionary entry from others. Should this realization manifest itself in our recommendation? If so, I was thinking that I could draw another mapping picture building on the first. This second one would show the ISO 11179 concepts (class, property) and the dictionary entry name components (object term, property term, representation term?, various qualifiers). The diagram would relate these to one-another and to the Core Components model. That is all. Regards, Bill