Re: [ubl] Minutes of Pacific UBL TC call 20 November 2019 01:00UTC

[Andrea Caccia <andrea.caccia@studiocaccia.com>]

Dear all,

as a follow up to the request for contributions about the logo please find attached a very poor graphical proposal that hopefully can give an idea of what I have in mind.

There are some empty spaces (left when moving the "OASIS" and "ISO/IEC..." texts); using the original UBL logo as a basis (instead than starting from the Ken's proposal) can solve the issue.

I think that using a non-white plain color for the background (as one of the last Ken's proposals) reduces the impact of the logo and can create issues when the logo is put on other backgrounds  or close with other logos.

The main goal of the big white ellipsis is to maintain distinguished and identifiable the logo in as many contexts as possible. Outside the ellipsis it should be transparent (I could not do it with the simple graphical tool I used).

Possible variants: make the "OASIS" text bigger and/or the "ISO/IEC..." smaller to balance better; use the "OASIS blue color" for the 3 texts or for the whole logo (keeping a white background).

Andrea 

Il giorno 20 nov 2019, alle ore 03:14, Kenneth Bengtsson <kbengtsson@efact.pe> ha scritto:

MINUTES OF PACIFIC UBL TC CALL 20 NOVEMBER 2019 01:00UTC

http://www.timeanddate.com/worldclock/fixedtime.html?iso=2019-11-20T01:00:00

Pacific: 19:00MSP/20:00Lima/20:00Ottawa/01:00UTC/12:00Sydney

 

PARTICIPATION

 

Kenneth Bengtsson (convener)

Erlend Klakegg Bergheim

Andrea Caccia

Ken Holman

 

Regrets:

 

Levine Naidoo

 

REFERENCING THE SPECIFICATION

 

One of the following should be used as a specific citation:

-  OASIS Universal Business Language (UBL) v2.2

-  OASIS Universal Business Language (UBL) v2.1 (ISO/IEC 19845:2015)

The following would be used for a general (any version) citation:

-  OASIS UBL (ISO/IEC 19845)

The canonical 2.2 documents are available in the OASIS repository:

-  http://docs.oasis-open.org/ubl/os-UBL-2.2/

The canonical 2.1 documents are available in the OASIS repository:

-  http://docs.oasis-open.org/ubl/os-UBL-2.1/

The ISO/IEC catalogue entry for UBL 2.1 is found at:

-  http://www.iso.org/iso/catalogue_detail.htm/?csnumber=66370

The ISO/IEC document and attachments for UBL 2.1 are found at:

-  http://standards.iso.org/ittf/PubliclyAvailableStandards/

 

STANDING ITEMS

 

Additions to events calendar - http://ubl.xml.org/events

Nothing

 

Review of Pacific call minutes

Pacific call cancelled last week

 

Review of Atlantic call minutes

https://lists.oasis-open.org/archives/ubl/201911/msg00011.html

 

Membership status review

https://www.oasis-open.org/policies-guidelines/tc-process#membership

 

New member orientation information:

https://www.oasis-open.org/committees/document.php?document_id=59647

 

Voting status is determined by the following:

-  existing voting members must not miss two consecutive meetings to maintain voting status

-  non-voting members must attend two consecutive meetings to obtain voting status

-  members formally on leave by prior request must not attend and their voting status is not impacted

 

Current UBL TC voting member list (alphabetical):

 

-  Todd Albers

o  Member ASC X9 AB, Member ISO 20022 Payment SEG, Member W3C Web Payments Interest Group, Business Payments Coalition

-  Oriol Bausa Peris

o Member OASIS BDXR, Member OASIS ebXML, Editor TC434 Validation

-  Kenneth Bengtsson

o  Chair OASIS BDXR, Observer OASIS ebXML, DK Expert UN/CEFACT

-  Erlend Klakegg Bergheim

o  Member OASIS BDXR, Member OASIS ebXML Core & MS, Member CEN/TC434/WS8

-  Peter Borresen

o  DK Member CEN/TC440, Assistant Convenor CEN/TC440/WG7

-  Andrea Caccia

o Chair CEN/TC 434, Member ETSI/ESI TC, IT Expert UN/CEFACT

-  Ger Clancy

-  Kees Duvekot

o  Member OASIS BDXR, Member of the StandaardisatieÂplatform e-factureren

-  Cecile Guasch

o Member CEN/TC440, Convenor CEN/TC440/WG1, Convenor CEN/TC440/WG2, European Commission liaison (DIGIT Interoperability Unit)

-  G. Ken Holman

o  Member OASIS BDXR, CA Member JTC 1/SC32, CA Expert UN/CEFACT

-  Yves Jordan

-  Ole Madsen

o DK Member CEN/TC440, CEN/TC440 Liaison JTC 1/SC 32

-  Natalie Muric

 

UBL 2.3

 

ISO submission

 

Editors and subcommittee chairs need to familiarize themselves with ISO/IEC Directives Part 2 in order to produce content that is compliant with ISO requirements:

https://www.iso.org/directives-and-policies.html

 

ISO requirements being discussed here: https://issues.oasis-open.org/browse/UBL-240

 

UBL 2.3 First Public Review Comment Resolution

 

Proposal for final comment resolutions uploaded here: https://www.oasis-open.org/committees/document.php?document_id=66254&wg_abbrev=ubl

 

Members should review the comment resolutions so that we can respond formally to commenters.

 

UBL 2.3 Second Public Review

 

Preparation of PRD02:

 

-  Implement resolutions of PRD01 comments

-  Review prose to comply with ISO requirements as discussed here: https://issues.oasis-open.org/browse/UBL-240

-  https://issues.oasis-open.org/browse/UBL-247

-  Update conformance clause to include conformance with additional Extension constraints: https://issues.oasis-open.org/projects/UBL/issues/UBL-248

-  Update section 3.5.2 with Extension elements present at every ABIE: https://issues.oasis-open.org/browse/UBL-249

-  XPath definition in Document Reference may need review. Discussion here: https://issues.oasis-open.org/browse/UBL-263

-  Cardinalities of LegalDocumentReference and TechnicalDocumentReference: https://issues.oasis-open.org/browse/UBL-253

-  Requirements for storage facilities: https://issues.oasis-open.org/browse/UBL-269

 

GUIDANCE REGARDING THE USE OF THE OASIS UBL LOGO

 

Draft committee note: https://www.oasis-open.org/committees/document.php?document_id=66208 (see also:https://lists.oasis-open.org/archives/ubl/201911/msg00009.html).

 

Logotype being discussed here: https://lists.oasis-open.org/archives/ubl/201911/msg00014.html

 

Members are encouraged to provide feedback and suggest alternatives.

 

UBL PAYMENTS AND FINANCE SUBCOMMITTEE (PAYFIN)

 

Nothing

 

UBL POST-AWARD

 

Nothing

 

UBL PRE-AWARD

 

Nothing

 

UBL TRANSPORTATION SUBCOMMITTEE (TSC)

 

Nothing

 

UBL NAMING AND DESIGN RULES SUBCOMMITTEE (NDRSC)

 

Ken is exploring the use of digital signatures in the JSON UBL representation. JWS (used for example in the JWT) is a possibility.

 

ETSI is working on a JAdES digital signature specification for JSON. Andrea to share more information.

 

A ticket has been created to follow this subject: https://issues.oasis-open.org/browse/UBL-270

 

TC LIAISONS

 

ISO TC 204/WG7

 

Agreed at the September 11, 2019 TC conference call to seek a formal liaison with ISO TC 204/WG7 specifically for collaborating on the new ISO 24533 specification.

 

We need to appoint a liaison, preferably someone who is a member of both groups. See also: https://www.oasis-open.org/policies-guidelines/liaison#liaisons

 

CEN TC 434

 

Agreed at the Copenhagen face-to-face meeting that the UBL TC is open to establish a formal liaison with CEN TC 434 to create a European or international standard for electronic invoicing, if there is an interest from the CEN TC.

 

Andrea will keep the UBL TC informed of any progress.

 

ISO/IEC JTC 1/SC 32/WG 1

 

ISO/IEC JTC 1/SC 32/WG 1 is open to establish a formal liaison. Ken and Andrea participated in the last WG 1 meeting. Andrea will post a progress report.

 

JIRA TICKETS

 

Available filters:

-  Discuss: https://issues.oasis-open.org/issues/?filter=15172

-  UBL 2.x: https://issues.oasis-open.org/issues/?filter=12972

-  BDNDR: https://issues.oasis-open.org/issues/?filter=13472

-  All UBL: https://issues.oasis-open.org/issues/?filter=11670

-  TCAdmin: https://issues.oasis-open.org/issues/?filter=13070

 

When creating tickets, remember to distinguish the following components by how they are described to be used as categories:

https://issues.oasis-open.org/browse/UBL/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel

If you leave the "Component/s" field empty, the ticket will not show up in the summary filter.

 

Members please note to discuss ticket issues as comments to the ticket so that we can audit the discussion when making decisions about the ticket, without having to find the discussion on the main mail list.

 

JIRA status and resolution value definitions

Necessary to review the definitions of ticket status and resolution in JIRA to align with the values that currently can be assigned.

 

Our current definitions are:

 

-  NEW: the issue has been created but not yet agreed to be in consideration or not for the development distribution

o  in order for the issue to become active work for the committee the new ticket must be changed to OPEN or it will not be seen in the "to do" filter

o  the other option on a new ticket is to change it to DEFERRED

o  please remember to look at the open filter to ensure visibility: https://issues.oasis-open.org/issues/?filter=12972

-  OPEN: the issue is in consideration for the development distribution

o  keep the issue OPEN when assigning to Ken for incorporation

o  please remember to add a comment regarding expectations whenever you assign an OPEN ticket to another person for any action

-  RESOLVED + Incomplete: the issue has been decided but not yet in test

-  RESOLVED + Applied: the issue is incorporated in test but not released

-  RESOLVED + Fixed: the issue is incorporated in a working draft version

-  RESOLVED + Later: the issue is still up for discussion for a future minor revision but not the current development

-  RESOLVED + No Action: considered as no action for any distribution

-  RESOLVED + Cannot Reproduce: considered as no action for distribution

-  APPLIED + Fixed: the issue is included in a public review (record the availability of the disposition once review opened)

-  DEFERRED: the issue is not in consideration for any minor revision

o  please remember to use this when creating new tickets for backwards-incompatible changes

-  See also the discussion on the status workflows here: https://lists.oasis-open.org/archives/ubl/201709/msg00000.html

 

SUBCOMMITTEE CONFERENCE CALLS

 

-  Transportation Subcommittee will be meeting on Thursday every week at 14:00UTC (will be using Peter's GotoMeeting facility)

-  Pre-award Subcommittee will be meeting on Wednesdays every week at 13:30UTC (will be using Natalie's WebEx facility)

o Pre-award cancelled next week. Possibly setting up a meeting at a different time (see Pre-award SC above).

-  Other subcommittees will be meeting on an as-required basis

 

FACE-TO-FACE

 

Face-to-face meeting(s) in 2020?

 

Possibility in Napa Valley in May 2020.

Possibility in Minneapolis.

 

Possibly back-to-back with Exchange Summit Americas and IBM Think! Conferences (both held same week).

 

TC CONFERENCE CALL SCHEDULE

 

Call schedule

 

2019-11-20

-  Pacific: 19:00MSP/20:00Lima/20:00Ottawa/01:00UTC/12:00Sydney

-  Atlantic: 09:00MSP/10:00Lima/10:00Ottawa/15:00UTC/16:00Europe

2019-11-27

-  Pacific: 19:00MSP/20:00Lima/20:00Ottawa/01:00UTC/12:00Sydney

-  Atlantic: 09:00MSP/10:00Lima/10:00Ottawa/15:00UTC/16:00Europe

2019-12-04

-  Pacific: 19:00MSP/20:00Lima/20:00Ottawa/01:00UTC/12:00Sydney

-  Atlantic: 09:00MSP/10:00Lima/10:00Ottawa/15:00UTC/16:00Europe

2019-12-11

-  Pacific: 19:00MSP/20:00Lima/20:00Ottawa/01:00UTC/12:00Sydney

-  Atlantic: 09:00MSP/10:00Lima/10:00Ottawa/15:00UTC/16:00Europe

2019-12-18

-  Pacific: 19:00MSP/20:00Lima/20:00Ottawa/01:00UTC/12:00Sydney

-  Atlantic: 09:00MSP/10:00Lima/10:00Ottawa/15:00UTC/16:00Europe

2019-12-25

-  Calls cancelled

 

Outline of teleconference times for 2019

 

https://lists.oasis-open.org/archives/ubl/201812/msg00000.html

(Note the date for the Australia time change is indicated incorrectly)

 

TC calendar

 

http://www.oasis-open.org/committees/calendar.php?wg_abbrev=ubl

 

iCal subscription link: http://www.oasis-open.org/apps/org/workgroup_feeds/ical/my_vcalendar.ics?token=fa658a7994a6cefb10c10be09e139af3&workgroup_id=50

 

Will anyone be requesting a leave of absence in the near future? For privacy reasons, this discussion will be kept off of the minutes.

 

OTHER BUSINESS

 

None