[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes of Pacific UBL TC call 19|20 November 2007
MINUTES OF PACIFIC UBL TC MEETING
TUESDAY 20 NOVEMBER 2007
ATTENDANCE
Jon Bosak (chair)
G. Ken Holman
Tim McGrath (vice chair)
Andy Schoka
STANDING ITEMS
Additions to the calendar:
http://ibiblio.org/bosak/ubl/calendar.htm
TM: Was not able to attend the Standards 2007 conference in
sydney.
GKH: Add name to XML 2007 entry.
Liaison report
AS: TL and AS represented UBL at the TBG17 F2F in Paris.
The meeting was very positive.
TM: We also participated in a TBG17 telecon since the last
report, and another call is scheduled for later today to
discusss the timetable and prototypes of the process and
artefacts.
Subcommittee report: TSC
AS: Con call scheduled for next week.
Review of Atlantic call
No comments.
Support page submissions
None this week.
2008 TC WORK SCHEDULE
See
http://lists.oasis-open.org/archives/ubl/200711/msg00019.html
TARGETING COMMITTEE SPECIFICATIONS
AGREED that we are aiming for CS status with the
Customization Guidelines, the 2.0 Update Package, the IDD,
and UBL 2.1 (followed by OS in the case of 2.1 after
sufficient time has elapsed for implementations). [Note that
we have already targeted CS status for the UBL 2.0 NDR.]
SCHEDULE FOR UPDATE PACKAGE
GKH (re: status check: gc updates): All of the genericode
files will need to be updated to bring them up to gc 1.0
(versions in UBL 2.0 OS are gc 0.4).
AGREED: TM to give GKH revised content by 12/17; GKH to
deliver entire updated gc directory tree by 1/7 [i.e.,
2008-01-07].
AGREED to move final build of 2.0UP to 1/14 and approval of
PRD to 1/28, i.e., approve the UP PRD at the meeting in
Manhattan.
SCHEDULE FOR UBL 2.1
ACTION: TSC to fill in line 12 after the con call scheduled
for 11/29.
AGREED to move publication of 2.1 CS to April 2009.
SCHEDULE FOR UBL 2.0 NAMING AND DESIGN RULES
GKH/TM: We need to add a section to the NDR to document
instance-level code list metadata: list ID, list version ID,
etc. With code lists, UBL is defining values, and we need a
section describing the metadata for those values. GKH has
done this for CVAs and is prepared to help MG/MC with the
task.
ACTION: JB to put this on the agenda for the Atlantic call.
SCHEDULE FOR CUSTOMIZATION GUIDELINES
GKH: MC/MG are only scheduled to have Chapter 1 done by
Manhattan. We have to sign off on it there, and then write
Chapters 2 and 3.
TM: Thus completing the Guidelines at the meeting in Europe.
ACTION: JB to put Chapter 1 status check on the Atlantic
agenda.
SCHEDULE FOR CALCULATION MODELS
GKH: This will come out of HISC along with the XForms; take
it off the schedule as a separate item.
SCHEDULE FOR BITS
TM/AS: This looks about right, as most of the work remaining
will be done in PSC.
UPDATE PACKAGE: JPLSC COMMENTS
See
http://lists.oasis-open.org/archives/ubl/200710/msg00021.html
We got halfway through the JPLSC comments this week, as
detailed below. We intend to finish this in next week's
Pacific call.
Two basic points were noted at the beginning of the discussion:
(1) we cannot make any backwards-incompatible changes until the
next major release of UBL (not UBL 2.1, which is a minor
release); (2) everything decided here will have to be reviewed
by the PSC as well as by participants in the Atlantic call.
The numbers refer to item numbers (not line numbers) in the
spreadsheet provided by the JPLSC.
1. To be considered for the next major release.
2. A quick check of Order and Order Response shows these ASBIEs
in green, so we're not seeing the problem referred to. We
will need specific examples.
3. ACTION: TM to post to the PSC list for further
consideration.
4. The order is deliberate, not an oversight. To be
reconsidered in the next major release.
5. The language is deliberate, but it may be advisable to
provide a separate definition for Catalogue Managing Party.
ACTION: TM to post to the PSC list for further
consideration.
6. The terms are not interchangeable. ACTION: TM to provide an
answer.
7. ACTION: TM to provide an answer.
8. This is a typo in the definition: "code" should be "cost
centre." ACTION: Add to the update task list.
9. This is deliberate; the semantic JPLSC are requesting is
given by "ID." (UBL 1 had BuyerOrderID and SellerOrderID.
In UBL 2 these are ID and SalesOrderID, respectively.)
10. This is a PSC question. It was the subject of considerable
debate in 2.0. To be considered for UBL 2.1 (added optional
constructs).
11. TM to provide an answer.
12. Same as item 9.
13. Same as item 9.
14. This is a typo in the definition, and the correction given
is correct. ACTION: Add to the update task list.
15. Same as item 8. ACTION: Add to the update task list.
16. The definition is correct as is.
17. The added qualifier "legal" is necessary in order to
differentiate the legally binding total specified by the
supplier in the Invoice from the monetary total specified by
the buyer in the Order. However, the definition should be
clarified by changing "total amount payable" to "legally
binding total amount payable." ACTION: Add to the update
task list.
18. ACTION: TM to post to the PSC list for further
consideration.
19. We understand the concern raised by JPLSC, and in fact this
document was called "ForwardingInstruction" (singular) in
early drafts of UBL 2.0. The name was changed to
"ForwardingInstructions" (plural) in accordance with input
from UN/CEFACT TBG3 in order to align with the name in
UNTDED and UN/CEFACT UNeDocs.
20. The correction is correct: "shipping instruction" should be
"forwarding instruction." But then we don't need two
sentences. So the correction should be: (1) Leave the first
sentence as is; (2) remove the second sentence; (3) add
"shipping instruction" as an alternative Business Term.
ACTION: Add to the update task list.
21. Same as item 19.
22. This is something to be explained in some future
Implementation Guidelines. It is true that Shipping Order
will usually be issued after Forwarding Instructions, but
this is not always the case. Following the UNTDED, the
optional ShippingOrderID is provided for cases in which
Shipping Order is made before Forwarding Instructions. In
most Forwarding Instructions, this element would not be
used.
Processing of the remaining JPLSC comments continues next week.
2008 TC MEETING SCHEDULE
28 Jan - 1 Feb 2008 in Manhattan
Confirmed. 101 Park Avenue.
April 2008 in Rome (together with UBL International Day)
GKH: We are converging on the week of 14-18 April 2008 for
the TC meeting in Rome, but this is not final yet.
ACTION: Discuss these dates in the Atlantic call.
4-8 August 2008 in Montréal
Confirmed. Hotel Europa, rue Drummond.
January 2009 in Fremantle
Still tentative.
NOVEMBER-JANUARY TC CONCALL SCHEDULE
Week of 11/19 Regular schedule
Week of 11/26 Regular schedule
Week of 12/03 Skip
Week of 12/10 Regular schedule
Week of 12/17 Regular schedule
Week of 12/24 Skip
Week of 12/31 Skip
Week of 01/07 Regular schedule
Week of 01/14 Regular schedule
Week of 01/21 Skip
Week of 01/28 Manhattan F2F
Week of 02/04 Skip
Week of 02/11 Regular schedule
##################################################################
TRACKING ITEMS
##################################################################
UPDATE PACKAGE
Methodology:
http://lists.oasis-open.org/archives/ubl/200710/msg00027.html
http://lists.oasis-open.org/archives/ubl/200711/msg00006.html
PACIFIC ACTION ITEMS FROM MANHATTAN (MAY 2007)
ACTION: PSC and TSC to provide feedback on UBL 2.0 SBS 2.0:
http://www.oasis-open.org/committees/download.php/23873
Pending.
ACTION: PSC and TSC to summarize business rules that are (1)
wanted in UBL but not allowed by [i.e., capable of being
addressed by] the NDR (e.g., requirement to include one of
PartyName and PartyIdentifier but not both) and (2) data items
whose constraints are inherited from another standard (e.g.,
lengths of data items specified by UNTDED); the rules so
identified to become candidates for a list of schematron
assertions "recommended to be included" (final characterization
TBD).
Pending.
Jon Bosak
Chair, OASIS UBL TC
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]