This document covers the proceedings of the work group meeting.

Next online meeting: Wednesday, September 19, 14:00 to 16:00 CEST

Roll Call of Attendees

P=present, E=excused

Agenda

Agenda

1. Approval of agenda and roll call.
2. Resourcing of schematrons and testing.
3. Alignment of status codes.
4. Plan for next steps.
5. Ascii doc work.
6. 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. Resourcing of schematrons and testing.

Resourcing remains a challenge. Following noted:

• Schematron development
  • SE may be able to contribute Martin Forsberg.
  • NO is providing automation tool and can provide Siw for part of work.
• Testing
  • Jesper may be available if funding available.
• Other
  • Waiting for response from DK.
  • No contact made with PL, NL and UK.
  • IT may be able to contribute Iacopo either for testing or dev.
  • Waiting for response from BE.

Georg and Siw will meet on Monday to schedule schematron development.

3. Alignment of status codes.

The use of action and status code across document reviewed and decided to align the order response, that currently uses UNECE 1225 on document level with other transactions by using following values from ISO4343:

12 - Received (new in BIS3) , becomes, AB - Message acknowledged

27 - Rejected , becomes, RE - Rejected

29 - Accept w/o amend , becomes, AP - Accepted

30 - Accept with amend , becomes, CA - Conditionally Accepted

4. Ascii doc work.

Questions relating to askii doc discussed and answered.

5. Plan for next steps.

Next week will focus on developing the schematrons, aiming to start public review on Sept 24th. Providing for testing before that date will be challenge, options to compensate are:

• Delay review date,
• Shorten review period.
• Plan for testing as part of the review.

If needed the team favored the last option.

AOB

Attachments in Dispatch advice.

It was noted by Arne that the dispatch advice does not support attachments. They are needed for hazardous cargo deliveries. Elisa supported the comment. Since deadline for RFC is passed it was agreed that Arne will submit during review period.

Message examples

Team members will contribute test messages either directly into Git or by emailing them to Georg.

• Assign the generation of test messages to team members. Georg Birgisson
  

Meeting closed at 16:00 CEST.