Specification Management sub-committee

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[start|Back to Start]] | 
[[Teleconference Notes|Back to Teleconference Notes]]

===== 29 April 2010 =====

Quick notes from the 15th April teleconference:

 Bob Daniel
 Doug Tolbert
 Jishnu Mukerji (HP)
 Larry Johnson (TethersEnd)
 Manfred
 Pete
 Tom Rutt
 Andrew
 Sridhar

0. Appoint a note taker for this call.
>
> 1. Any corrections, clarifications in the notes from the last meeting,
> and acceptance of the same.
>
> 2. Agenda bashing
>
> 3. Discuss work item 1a "Develop guidelines for machine readable files
> that must accompany submissions" led by Pete and Cory.
>
> 4. Brief discussion of next steps.
>
>

[13:07] Jishnu Mukerji (HP): Note taker is Jishnu

[13:08] anonymous morphed into Bob Daniel

[13:10] Jishnu Mukerji (HP): Paper being discussed at http://www.omgwiki.org/smsc/lib/exe/fetch.php?id=playground%3Anew_page&cache=cache&media=playground:machine_readable_artifacts_for_omg_submissions.doc

[13:11] Jishnu Mukerji (HP): Pete gave an overview of the contents of this draft

[13:13] Jishnu Mukerji (HP): Discussion of the item "The files should not arbitrarily change between versions, for example through use of a new tool (or versions thereof). That includes changes to identifiers."

[13:13] Jishnu Mukerji (HP): Larry pointed out this may prove to be onerous for Domain submitters

[13:21] Jishnu Mukerji (HP): Using a different tool to generate XSDs would typically cause massive syntactic changes that have relatively little semantic change

[13:22] Jishnu Mukerji (HP): Pete pointed out that this is a "should" best practice rather than a shall "mandatory" requirement

[13:23] Sridhar: If we doing our standards 'properly' the tool used should not change the interchange format - only a revision of the undrlying model would cause a change

[13:24] Sridhar: Suggested best practice : Interchange format changes should mirror model changes (small changes in model affect interchange by a small amount)

[13:28] Jishnu Mukerji (HP): Larry: Unfortunately XMI is not specified in a way that makes it possible to achieve the second item mentioned by Sridhar

[13:29] Jishnu Mukerji (HP): Pete: There are both XMI and UML issues

[13:31] Jishnu Mukerji (HP): Larry: Action item raise an issue for this

[13:32] Jishnu Mukerji (HP): Pete two issues: 1 against UML to make all associations ordered, and 2 an issue on XMI to require XMI serialization to reflect the same ordering as in UML

[13:32] Jishnu Mukerji (HP): Doug: Restrict this to RTFs

[13:33] Jishnu Mukerji (HP): Manfred: There are limitations in using tools like subversion for managing model versions

[13:36] Jishnu Mukerji (HP): Discussing the Manifest issue brought up by Pete, Andrew and Jishnu said the info in the manifest is necessary. We can decide how it is presented in the published document

[13:40] Jishnu Mukerji (HP): On the issue of zip files, Larry, Manfred and Doug suggested that two separate zip files one for normatives and one for informatives with each file containing a manifest of its content

[13:41] Jishnu Mukerji (HP): Tom: When the files are published they need to be published at the right location URL

[13:48] Sridhar: got to go,  bye

[13:52] Jishnu Mukerji (HP): Contents of zip files will typically not need individual document numbers.
Specification Management sub-committee

User Tools

Site Tools

Page Tools
