Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

    Approval of agenda and roll call

    Agenda approved and attendance noted in attendance table.

    Status of development.

...

  • The picked up and we are getting ready to start sharing the documents. They are available at the following location.
  • http://test-docs.peppol.eu/poacc/upgrade-3

    Comments to the documentation can be given by creating issues in Github using the following link

  • https://github.com/OpenPEPPOL/poacc-upgrade-3/issues
  • Review will be started in team by assigning document to reviewers as follows

  • PEPPOL BIS 3A Order OnlyArne
    PEPPOL BIS 28A OrderingArne
    PEPPOL BIS 36A Message Level ResponseDirk
    PEPPOL BIS 1A Catalogue Only
    PEPPOL BIS 18A Punch Out
    PEPPOL BIS 30A Despatch Advice
    PEPPOL BIS 42A Order AgreementThomaz
    PEPPOL BIS 63A Invoice ResponseDirk

    Georg Birgisson and Siw Midtgård Meckelborg (Unlicensed) will create a short list of what to look for in the review and notify the reviewers when they can start.

  • Issues arising from development

  • Raising following questions for evaluation and discussion in later meetings.
  • How should we align the Allowances Charge class with other documents (Order Agreement, Order), missing Allowance charge reason code, base amount and multiplier.
  • How do we handle UNSPSC in item classification since it is not part of the EN code list.
  • Should we create restriction on the ICD list for time identifiers.
  • The endpoint identifier list is being published by the Publication Office, GB is following that up. There is need to follow up with TIC on changing the ID policy. TIC already has an issue Jan will follow up on it .
  • Processing of Change requests

  • Issue
    Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyPB30-33
    , to add full address information to price in Punch Out was agreed.
  • Issue
    Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyPB30-30
    , for support for multiple order response, to add line, indicate delivery and support backorder agreed for BIS28 Ordering. The resolution of this issue also closes issue
    Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyPB30-28
    ,
    Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyPB30-29
    and
    Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyPB30-31

...