[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Meeting minutes
Meeting minutes attached... -Oliver
ebXML RegRep Technical Committee Telcon Minutes, 6/10/2009 Attendees: Kathryn Breininger Farrukh Najmi Carl Mattocks Nikola Stojanovic Oliver Newell Kathryn inquired whether there were comments on the previous minutes. There were no comments, and the minutes were approved. The first topic on the agenda was to review the response from the ISO 11179 specification authors to the feedback the ebXML RegRep TC provided. The response was generally positive, and it appears the interaction was viewed as beneficial by both specification teams. There was some discussion as to the next step, and whether the RegRep TC would provide a second iteration of feedback based on the response to our initial feedback. The concensus was that additional feedback at this point was subject to the law of diminishing returns, but an ongoing interaction with the ISO 11179 team would certainly be valuable. Kathryn compiled a list of issues to communicate to the 11179 TC related to establishing such an interaction, such as access to each others draft specifications online. Nikola mentioned that the ebXML RegRep spec could benefit from a review by the ISO 11179 committee, in return for our review of 11179. He also commented that a reference to the ebXML RegRep spec should be added to the 11179 bibliography. These issues were added to issue list for the 11179 TC. The topic shifted to the resolution of a number of open issues, in particular, issues REGREPTC-85, REGREPTC-86, REGREPTC-87, and REGREP-88. Oliver mentioned that it might make sense to move the JIRA issue data from the MIT Lincoln Laboratory JIRA instance to the new OASIS JIRA instance. The feasability of doing this will be investigated. - REGREP-85 Discussion Farrukh described the need for a new query to get a set of objects based on their logical id rather than their unique id. There was general agreement that the query was needed. Since a logical id can be shared by multiple versions of a registry object, the query can return multiple registry objects. A name change from 'GetObjectByLid' to 'GetRegistryObjectsByLid' was suggested to make clear that the query could return multiple objects. There was general agreement that the name change made sense. Nicola mentioned that care should be taken to use the plural form consistently for all queries. - REGREP-86 Discussion This issue focuses on the the semantics of 'Submitted' and 'Draft' in ebXML status fields. 'Draft' has been introduced as part of the registration procedures and has some semantic overlap with 'Submitted' in the core specifiction. There is a desire to minimize the number of different definitions for the same concept where possible. There was considerable discussion as to whether the usage of 'Draft' in the regproc, actually did overlap the usage of 'Submitted' in the core spec, or whether it was in fact a separate concept. The issue was not resolved during the telcon, and remains open. The group ageed to hold additional discussion on the issue on the mailing list. - REGREP-87 Discussion Farrukh described the need for a new query to support retrieval of audit trail information. Nikola suggestion to split the query into two queries, one for the Logical id, and one for the id, was well-received. - REGREP-88 Discussion A long-standing issue with the RegRep 3 spec was the lack of a way to retrieve only the latest version of an object via a query, rather than all versions. REGREP-88 adds an attribute that specifies whether or not to match older versions. There was agreement that this addition to the core attributes for all queries made sense. [In a follow up email thread subsequent to the call, it was agreed that the default for the attribute would be false, preventing older versions from being returned]
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]