This document covers the proceedings of the work group meeting.

Next online meeting: Wednesday, October 3, 14:00 to 16:00 CEST

Roll Call of Attendees

P=present, E=excused

Agenda

Agenda

1. Approval of agenda and roll call.
2. Status and plan. Prepare for Public review.
3. AOB.

• Decision Log

  DECISIONS TAKEN IN THIS MEETING. Please see minutes for Decisions. Log of all decisions
  

  Issue and Action Log

  Following tasks were raised in this meeting. For overview of tasks go to Task report - All 

Meeting notes

1. Approval of agenda and roll call

Agenda approved and attendance noted in attendance table.

2. Status and plan. Prepare for Public review.

Schematrons

Schematrons work a

• Despatch advice,  7rules, Iacopo,
• Order agreement, 9rules, Iacopo,
• Invoice Reponse, 2rules, Georg,
• Order, 16rules, Siw,
• Order response, 3rules, Siw,
• Punch out, 19rules, Georg,
• Catalogue business, 16rules, Martin,
• Catalogue response, 2rules, Martin

Status

• Despatch advice,  rules ready, need to be submitted.
• Order agreement, rules ready, need to be submitted.
• Invoice Reponse, done
• Order, done
• Order response, done
• Punch out, done
• Catalogue business, done
• Catalogue response, done

Discussions

• Agreed to make make mandatory for all items, one id mandatory in all except in order. Use Order agreement rule for id's and Invoice rule for names.
• Replace all MUST with SHALL.

Syntax files

• Syntax files have old rules in them. We need to align. Remove rule references and replace with new ones. Done for Order and Order response. Remaining for others.
• Syntax are using old business terms id's.
  • We should use id's.
  • We need to number the new ones.
    1. We use bii numbers for old ones and modified number series for new ones as below.
       1. tir76-xxx
       2. tir76-pxxx

Rules

• Add a rules to ensure that allowance and charge amounts are not negative.
• Id's are missing.
• Rule file sets,
  • for each transaction
    • Automatic rules set, one sch file.
    • Manual rule set, one sch file.
    • Will be distributed as merged (automatic, manual and the common) in one sch file for the review.
    • Consider adding xslt for final distribution.
  • for all transactions.
    • One common file.

Testing

• We can use the unit test methodology, if we want.
• Either way we need numerous test files.

Unit test status

Creation of unit test files. Two approaches identified. Decided to use DIFI approach where only snippets are tested.

• Despatch advice,  done.
• Order agreement, done, missing two rules.
• Order, done
• Order response, done
• Invoice Response, Georg will prepare
• Punch out, Charlotte will prepare
• Catalogue business, Charlotte will prepare.
• Catalogue response, Charlotte or Georg will prepare.
• MLR, not needed.

Work schedule

1. Finish cleaning up schematrons before end Friday - Siw, Georg, Iacopo
2. Finish unit test files before end Friday - Charlotte, Georg
3. Verify testing, Monday - Siw, Georg.
4. Prepare package for distribution, Tuesday - Siw, Georg
5. Initiate review period, Wednesday - Georg

AOB

None raised.

Meeting closed at 16:00 CEST.