<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2119133258;
mso-list-type:hybrid;
mso-list-template-ids:846618814 710168580 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Dear All,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>At our last telecon we agreed a position on the recommendations from my actions below [agreements are documented in-line below] and my comments on the MPS Services Reorganisation document.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>With respect to the latter it is noted that comment 8 was agreed and comments 9,10 and 11 were rejected.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>As a result, I have updated the MPS Services Reorganisation document to reflect the agreed position [attached as WG Position 150119] and removed comments that have been closed.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>There are some minor updates to the model as a result, which I shall post tomorrow before the meeting.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Roger<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='color:#1F497D'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'> Roger Thompson [mailto:roger.rocketbrain@btinternet.com] <br><b>Sent:</b> 11 January 2019 13:45<br><b>To:</b> Mehran.Sarkarati@esa.int; moims-mp@mailman.ccsds.org<br><b>Subject:</b> Response to Actions from MP&S WG Telecon of 04/12/2018<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dear All,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In preparation for next week’s telecon, the following e-mail contains responses to my actions from the previous WG Telecon.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><u>170816-01: Update and Refine UML diagrams of the MPS Data Model<o:p></o:p></u></b></p><p class=MsoNormal><b><o:p> </o:p></b></p><p class=MsoNormal>As agreed, I have updated the model to reflect that Plan Versions and Patch Plans are not assumed to be contained within Planning Requests.<o:p></o:p></p><p class=MsoNormal>I also resolved the RevisionStatus class and enum name conflict by renaming the RevisionStatus class “PlanRevisions”.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><u>181204-02: Refine the concept of feedback and status update for<o:p></o:p></u></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Planning Request<o:p></o:p></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Plan<o:p></o:p></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Activities<o:p></o:p></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Event<o:p></o:p></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Resources<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>At the Berlin Meeting the set of MPS services was restructured as follows:<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Planning Request Service [PRS] works on Planning Requests [PRQ]<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Plan Distribution Service [PDS] works on Plans [PLN]<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Plan Execution Control Service [PEC]<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Plan Information Management Service [PIM] works on Planning Database [PDB]<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Plan Edit Service [PED] works on Planning Activities, Events and Resources<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It is suggested that each of these services should provide all the operations required to operate on particular objects as follows. Proposed updates to the summary of Service Operations produced in Berlin are included below in italics. I have also attached a commented version of the MPS Services Reorganisation document.<o:p></o:p></p><p class=MsoNormal>There are diagrams in the Green Book that reflect the set of services and the information objects they support.<o:p></o:p></p><p class=MsoNormal>I attach a powerpoint with some proposed updates to these – this work overlaps with my activities in the System Architecture WG, so it would be good to get agreement of the WG on the functional diagram.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>Planning Requests</b> are managed exclusively by the PRS service. This should provide feedback on the status of Planning Requests , down to the level of their contained Activities or referenced Plans – but only for the requested items. No further detail will be reported on the content of Plans referenced in requests. At present the only identified operation is <b>MonitorRequestStatus </b>which will return Request Updates. This only provides feedback at the level of the Planning Request – not the contained/referenced Activities or Plans. To obtain such feedback there are various options:<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>The Planning User uses the PDS service to obtain the resultant plan (but note this does not currently allow for monitoring of the status of Activities contained within a Plan).<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>The Request Update is extended to include the set of planned Activity Instances originating from the Request and their resultant Activity Updates<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>A separate Service/Operation Set is provided to subscribe to the status of planned Activity Instances originating from the Request (Activity Updates) – but this still requires the identity of Activity Instances to be returned in the Planning Request Update.<o:p></o:p></p><p class=MsoNormal><b><i>Recommendation: extend the Request Update to include planned Activity Instances and their Activity Updates.<o:p></o:p></i></b></p><p class=MsoNormal><b><i><span style='color:#1F497D'>[RST] WG Position: recommendation rejected, it was agreed that no further reporting should be provided within the Planning Request service.<o:p></o:p></span></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>Plans</b> and their reported status are managed by the PDS service. The identified operations allow a consumer to obtain full Plans (including their content of Planned Items and Resources), and to monitor Plan Status at the level of the plan. The identified operations do not currently provide for the return of Plan Status at the level of contained objects (Activities, Events and Resources).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The <b>Plan Execution Control Service</b> provides operations to load or merge plans/patch plans and to control the execution at the level of the Plan (implementation specific actions, but expected to include start, stop, suspend, resume) and to monitor the status of the execution process. It does not provide visibility of the current state of the plan or planned items.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The <b>Plan Information Management Service</b> provides operations to manage and access the MPS definitions: planning request templates, planning activities, planning events and planning resources. This is static definition data only and does not include dynamic information such as the associated instance objects and updates.<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b><i>Remove operations associated with [global] Constraints as these have been removed from the model<o:p></o:p></i></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b><i>Add get operations to return the selected definition(s)<o:p></o:p></i></b></p><p class=MsoNormal><b><i><span style='color:#1F497D'>[RST] WG Position: agreed.<o:p></o:p></span></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The <b>Plan Edit Service</b> enables an external function to modify the content of an existing or executing Plan. This manipulation is at the level of Planning Activities, Planning Events and Planning Resources and provides operations to insert, update and delete Planning Activity and Event instances and to update Planning Resources.<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b><i>Remove Submit/Update/Concel requests: these are duplicates of PRS operations. Plan Execution should expose PRS.<o:p></o:p></i></b></p><p class=MsoNormal><b><i><span style='color:#1F497D'>[RST] WG Position: agreed<o:p></o:p></span></i></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b><i>Remove ApplyPatchPlan: this is a PEC operation.<o:p></o:p></i></b></p><p class=MsoNormal><b><i><span style='color:#1F497D'>[RST] WG Position: rejected, the WG felt this operation does constitute part of the Plan Edit Service.<o:p></o:p></span></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What has not been clearly specified is where an external function can obtain active information on the current [execution] status of the items within a Plan: the Planning Activity and Event Instances and Resources. What is required is the ability to subscribe to the associated Updates to Activities, Events and Resources, subject to particular filters:<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>A specific Plan or Plan Version<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>The currently executing Plan<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>A subset of the above selected by Domain or Ownership (User).<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>A subset of the above by object type (Activity, Event or Resource)<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Specified Planning Activity or Event Instances, or Planning Resources<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>These operations could either be included either within the Plan Distribution Service (in effect providing detailed status on Planned Items and Resources referenced by a Plan); or with the Plan Edit Service as this is primarily concerned with the same objects (Planning Activities, Events and Resources). As these operations may be required by any Plan Observer, while Plan Edit is a very specific set of operations that are probably restricted access, it is recommended that the low level Planning Item status feedback is provided via PDS.<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b><i>Add a new operation MonitorPlanItemStatus as PUB/SUB to register for updates to Planning Activities, Planning Events and Planning Resources.<o:p></o:p></i></b></p><p class=MsoNormal><b><i><span style='color:#1F497D'>[RST] WG Position: agreed – this operation to be added to the Plan Distribution Service.<o:p></o:p></span></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To summarise it is recommended that feedback and status update is provided as follows:<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Planning Request</b>: via PRS service – operations already identified, but extend Request Update to include Activity Instances and their Updates<b><i><span style='color:#1F497D'> [RST] </span></i></b><span style='color:#1F497D'> <b><i>Rejected</i></b></span><b><o:p></o:p></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Plan</b>: via PDS service – operations already identified<b><o:p></o:p></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Activities</b>: via PDS – new MonitorPlanningItemStatus operation required<b><i><span style='color:#1F497D'> </span></i></b><span style='color:#1F497D'> <b><i>[RST] </i></b> <b><i>Agreed – the proposed operation addresses Activities, Events and Resources</i></b></span><b><o:p></o:p></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Event</b>: as above<b><o:p></o:p></b></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><b>Resources</b>: as above<b><o:p></o:p></b></p><p class=MsoNormal><b><span style='color:#1F497D'><o:p> </o:p></span></b></p><p class=MsoNormal><b><i><span style='color:#1F497D'>[RST] WG Position: In addition it was agreed that the List, Get, GetPlanStatus and MonitorPlan operations of the Plan Distribution Service should also apply to PatchPlans. This implies PatchPlans may need an ID, and that operations may require flags to indicate whether referenced items are Plans or PatchPlans.</span></i></b><b><span style='color:#1F497D'><o:p></o:p></span></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><u>181204-02 Formulate the “user need” for having an attribute Version in the entities of the data model<o:p></o:p></u></b></p><p class=MsoNormal><b><u><o:p><span style='text-decoration:none'> </span></o:p></u></b></p><p class=MsoNormal>What are the use cases we want to solve by having a version?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Versioning is associated with Planning Data Definitions (Planning Request Templates; Planning Activity Definitions; Planning Event Definitions; Planning Resource Definitions; Function Definitions). The ObjectID of each associated Definition object is unique, so the Version is not necessary to ensure that the correct version of a definition can be referenced.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The general use case is to provide a more human-readable Version reference that correlates with an organisation’s internal configuration control processes, rather than being simply a unique Object ID.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Specifically this could allow for correlation with an institution’s wider configuration control at the level of a Mission Planning Configuration Database (or indeed an entire Mission Database), where a coherent set of definitions is:<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Subjected to a validation and verification process<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Released for operational use<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The Version field can then be used by the institution to indicate the context of which configuration control Version the definition was first created.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To a great extent the format and meaning of the Version is therefore specific to the Mission or Institution and the attribute is simply providing a hook for linkage to external configuration control processes. Standardising the format of the Version would allow for filtered retrieval and sorted listing of Versions based on the content of the Version attribute. The following options for the format of a Version attribute are proposed:<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Free format text (String type)<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>A simple number (Integer type)<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>A compound number <b><i>m.n </i></b>with Major and Minor versions (two Integers)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The advantage of either of the first options is that they can be represented as simple MAL Attributes, while the compound number is a Composite of two MAL Attributes.<o:p></o:p></p><p class=MsoNormal>An advantage of free format text is that it can support any institutional version numbering scheme.<o:p></o:p></p><p class=MsoNormal>The disadvantage of free format text is that it requires interpretation in order to be able to retrieve or sort definition versions according to a criteria.<o:p></o:p></p><p class=MsoNormal>The disadvantage of a simple number is that it cannot support a [common] versioning scheme with major and minor versions.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Given that the Version attribute is not required to support the MPS Information Model itself, it is therefore recommended that definition version attributes should use the String data type, removing the requirement for a special data type to support it and allowing a simple MAL Attribute to be used.<o:p></o:p></p><p class=MsoNormal><b><i><span style='color:#1F497D'>[RST] WG Position: following some debate it was agreed that this Version attribute should be a String, removing the requirement for a special data type in the MPS Information Model.</span></i></b><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>