Project Title	CCTS V3.0 Implementation of comments
Topic	Review of editings and editors comments
Date	2007/02/22
Start Time	13:00 CET
End Time	16:00 CET
Note Taker	Gunther Stuhec
Participants	[~mkblantz], Anthony B. Coates, Mark Crawford, Gunther Stuhec

Agenda

1. Welcome
2. Agree on agenda
3. Select note taker
4. Decision for: Change Proposal (Chapter 6.1 and 7.1)
5. Decision for: Change Proposal (Chapter 6.5)
6. Comments by Mails (Sue Probert, Ed Buchinski, Tony Coates, Duane Nickull)
7. Comments in the document CCTS V3.0 Draft
8. Other business
9. Next meeting

Meeting Results

Change Proposal (Chapter 6.1 and 7.1)

Meta models for data types

Tony submitted revised meta models with data types and without data type details (6.1 and 7.1) and detailled meta models for data types

Which meta model for figure 6.1 and 7.1 should used be in the document (with or without data type details)?

Use meta models without data type details

Change Proposal (Chapter 6.5)

Comments by Mails (Sue Probert, Ed Buchinski, Tony Coates, Duane Nickull)

Comments in the document CCTS V3.0 Draft

Examples for CCTS V3.0

[~mkblantz] will submit some agreed examples that can be used for the CCTS V3.0

She proposed following CCs and ABIEs:

ACC: Contract. Details
	ABIE: Trade_ Contract. Details

	ASCC Contract. Performance. Metrics
	ABIE: Trade_ Contract. Permance. Metrics

Business Context

The BBIE property and ASBIE property has no business context

The business context must belong ot all relevant artefacts including BBIE property and ASBIE property

Figure 5-1

Should the properties also included?

It should be explained in the text below.

Controlled Vocabulary

No change of text

Localized Information

Add text for the specific selection of dialects
Send not to Fred van Blommestein

6.6 General Core Component Properties

This section has no additional value
6.6 can be deleted, bacause other chaptes already have the necessary information.

Usage rules

How do you identifiying rules
It is better to define a specific class for usage rules that should be associated to all artefacts that require usage rules. This suggestion should be submitted to CCTS Project at the next iteration of public review.

What is about OMG OCL. Should be this a part of the CCTS?
OMG OCL is a syntax specific constraint languages and should be deleted from CCTS V3.0.

Sequencing
Rewiev of new sequencing text.

Kind of sequencing should be precised by additional rules, in which order the artefacts should be sequenced in an ACC, ABIE. A submission should be send to the CCTS Project during the next iteratio of public review.

Decisions

Action Items

Activity	Category	Start Date	Due Date	Responsible Person	Comment	Status
Submit some agreed examples that can be used for the CCTS V3.0	Specification	2007/02/22	2007/02/26	[~mkblantz]
Localized information - Add text for the specific selection of dialects	Specification	2007/02/22	2007/02/26	Mark Crawford
Localized information - Send updated information to [~fvblommestein]	Specification	2007/02/22	2007/02/26	Mark Crawford
Proposal for precised rules for sequencing	Proposal	2007/02/22	2007/03/16	[~gunther.stuhec
Proposal for defining a specific class for usage rules	Proposal	2007/02/22	2007/03/16	[~gunther.stuhec
Ubload new updated version of CCTS V3.0 to website	Specification	2007/02/22	2007/02/26	Mark Crawford

Next Meetings