NDR SC Minutes 24 September 2003

["Mavis Cournane" <mavis.cournane@cognitran.com>]

Dear all
please find attached today's minutes.

Regards
Mavis
---------------
Agenda
1. Roll call and welcome from the chair (Mavis)

Mavis Cournane
Mike Grimley
Anne Hendry
Eduardo Gutentag
Lisa Seaburg
Stephen Green
Tony Coates

2. Review schedule
 Week 5 (9/24) Start review with NDR Doc. - delayed
 Week 4 (10/1) Start review with LCSC of NDR Doc. - Expected to begin
review.
 Week 3 (10/8) NDR Doc review by SC
 Week 2 (10/15) NDR Doc review by SC
 Week 1 (10/22) NDR Doc review by SC
 Week 0 (10/29) Release on Friday

We will need to review the final schemas. The draft that is out now at v5
and v6 is underway. V6 is meant to be the final one. It is at Sue right now.
It should
be ready for the QA group on Friday. NDR need to look at it starting Monday.
The model has still to be finished. If any of the issues in the schema
relate to the model
that needs t be be done quickly. The NDR QA team is Mike, Lisa. Get Jack and
Bill Burcham to review the list. Lisa will do this.  Review will be done to
check compliance
with NDR Rules. This review should be completed in 5 working days.

3
A - Discussion of Code lists and next steps
The action item was on Gunther to look at compliance with CCTS. Sue is
working onthis now and we are happy with compliance.
SG: The question that is open - the code lists within the CCTS cannot be
catered for the mechanism that the code list team has come up against. There
is nothing
that can be done about it. They cannot be validated in the same way that the
other code lists are.
MHC: How big a problem is it?
This is only a problem for code lists referred to CCTS. THe mechanical fix
for us would mean specifying the code lists in our own format and not using
the CCTS.
JB: Either our agreement with ATG requires us to use their version or it
requires us if we use those codelists to use their version.
SG: It is the core component schema is the problem. The problem is is that
they share the CCTS schema with us. We would like to move the codes out of
that
schema and have them as BBIEs. We do this for other codes.
It applies now to Quantity, Amount and Measure.
JB: There is also an issue with using those for legal reasons. Is the
problem unexpected? Put this as a question to Gunther and Garrett.
Stephen will put this question to them and it can be taken up then in NDR.

B - Mark's proposed document structure
We should Chee Kai if it is possible to incorporate the suggestion by Mark.
Chee Kai already has a structure. He has adjusted his one away from this.

C- Rosetta Net comments
These have come from the liaison group.
We will chunk these out and create teams for responsibility.
 - Versioning.
Any older document should be opened by the latest minor version of the
schema is their suggestion.
EG: I am not sure if this would validate. We need to think about this.
It effects the namespace and the target namespace. Oh no it does not.

4.AOB