[Ccsds-omg-liaison] RE: AB Homework: SOLM FTF Report (dtc/12-02-12..15)

[Kizzort, Brad]

Thank you for your review and good catches, Hugues.

Juergen will be posting new versions of the following three documents for the SOLM FTF report:
	1. Final Report - 	dtc/12-03-01
	2. Inventory -		dtc/12-03-02
	3. Spec w/change bars -	dtc/12-03-03

I added the specification changes to the resolution description of 17101 and 17102 in the final report.  The resolution description was drafted to describe the model impact, which was the primary change.  When the figure and text ripple effects were discovered, they were added to the resolution without updating the resolution description.  This update corrects that deficiency in the final report. 

The inventory was updated to eliminate the duplicate entry for the metamodel and for the updated document numbers above.

I added issue tags to the Specification w/change bars.  Most of the tags could be inserted prior to the paragraph (or figure) containing the change, but in the case of tables, several of the issue tags were inserted after the appended rows rather than splitting the table.

Brad Kizzort
solm-ftf at omg.org


-----Original Message-----
From: VINCENT Hugues [mailto:hugues.vincent at thalesgroup.com] 
Sent: Wednesday, February 29, 2012 7:06 AM
To: solm-ftf at omg.org
Cc: space at omg.org; ab at omg.org
Subject: AB Homework: SOLM FTF Report (dtc/12-02-12..15)

Dear all,


Here are my first comments as AB reviewer of the "SOLM FTF Report" (dtc/12-02-12..15)


Inventory file:
	- Metamodel for SOLM is written twice
	- Metamodel URL: http://www.omg.org/spec/SOLM/20120201/SOLMetamodel.xmi
	- All Machine-consumables URL:
		http://www.omg.org/spec/SOLM/20120201/XXX


Specification:
	- You're supposed to put "issue tags" before each modification in the "with
	  change bars" document. The form of such a tag is:
		a line
		Issue <Number>: <Text of the issue>
		a line
	  You can have a look at ptc/11-10-06 for instance


Issue 17101
	- "This resolution applies to the non-normative model as captured in Enterprise 
	Architect and results in changes to the normative XMI model when it is exported. The 
	"revised text" below illustrates the impact on the XMI model"
		this is not the only modified thing since there is a change in a figure


Issue 17102
	- "This resolution applies to the non-normative model as captured in Enterprise 
	Architect and results in changes to the normative XMI model when it is exported. The 
	"revised text" below shows the impact on the XMI model"
		this is not the only thing since there is figures and texts modification
	- "6.6.10" -> "6.5.10"
	- "6.6.11" -> "6.5.11"


These modifications of the report document don't require a new vote from the FTF.


These comments don't preclude any further comments from me or other AB members.

Best regards,
Hugues VINCENT
OMG Architecture Board Member
hugues_vincent (at) omg.org