OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Minutes of Atlantic UBL TC call 29 June 2005


Minutes of Atlantic UBL TC meeting
15h00 - 17h00 UTC Wednesday 29 June 2005

ATTENDANCE

   Jon Bosak (chair)
   Mikkel Brun
   Mavis Cournane
   Stephen Green
   Mike Grimley
   Betty Harvey
   Anne Hendry
   Bryan Rasmussen
   Zarella Rendon
   Sylvia Webb

STANDING ITEMS

   Additions to the calendar (http://ibiblio.org/bosak/ubl/calendar.htm)

      ThomasL will provide details on an interim ebXML Asia
      Committee meeting in Seoul.

   Liaison reports

      None.

   Subcommittee reports

      None.

   Team reports

      None.

   Review of Pacific and Eurasia calls

      JonB: Regarding the UN/UBL call noted in the Eurasia
      minutes: the statement that "There was acceptance of the
      proposal to collaborate on the development of a common core
      component library" refers to a convergence of UBL and
      UNeDocs; there do not appear to be resources available that
      could achieve a convergence of UBL, eDocs, and the TBG17 CC
      library within the UBL 2.0 timeframe.  Everyone agrees that
      it would be best if we could reduce three sets of semantics
      to one, but given the apparent impossibility of
      accomplishing this in the near term, it seems advantageous
      to at least reduce three sets to two if resources can be
      found on the CEFACT side to do it.  This would at least
      align the two efforts that CEFACT is proposing to put into
      TBG2.

ACTION ITEM REVIEW

   PENDING ACTION: JonB to ask for a volunteer to serve as liaison to
   TBG17.

      Status: Put out a request, but no response.

   PENDING ACTION: MavisC and MikeG to review the email exchange
   contained in MartyB's message of 25 April and report back in
   next week's Atlantic TC call. Note also that we have been
   hoping for input from Henry Thompson.

      MavisC: The NDR editors reviewed the exchange and have sent
      a response and advice to MartyB and TonyC.  Henry Thompson
      has promised to work on our inquiry tomorrow and get back to
      MavisC with a response.

   PENDING ACTION: TC to review the SBS package over the next two
   weeks, with all comments back to the SBSC by 4 July.

      Status: Still no comments.

      StephenG: Any coming in after 4 July will be applied to the
      2.0 SBS.

   PENDING ACTION: JonB to review the current TC process and
   determine whether the SBS should be moved forward as a
   committee draft or a committee specification, the primary
   requirement being for a persistent URL.

      Status: Still pending.

   PENDING ACTION: JonB to contact KRLSC to see whether the June
   2006 meeting can be hosted in Seoul.

      Status: Still pending.

   PENDING ACTION: JonB to seek a host for a March 2006 meeting in
   Brussels.

      Status: Still pending.

   PENDING ACTION: JonB to revise the FAQ linked from the UBL TC
   page.

      Status: Still pending.

   PENDING ACTION: MavisC to send input to MarkC for ATG (see item
   #6 in the minutes of the 1 June Eurasia call).

      StephenG: DavidK reports an updated set of CCTS schemas that
      appear to include the 1.0 attributes we need; we need to
      check on this next meeting.  The key is whether we actually
      have a channel here for conveying our inputs to ATG2.  And
      we need to know whether ATG2 has updated the schemas; the
      ones we have say "draft."

DECISION ON REUSABLE

   AGREED that the proposed change is primarily for users of the
   spreadsheets and would not be necessary if using a tool that
   was context-aware.

   StephenG: Strictly speaking, there are no "common" or "core"
   BIEs; they exist only in context.  Furthermore, it appears that
   this problem is addressed by the CCTS mechanism for specifying
   context and that we might get the intended benefit by
   completely implementing the CCTS context code lists etc.

   AGREED that we should check with our CCTS experts to determine
   whether the CCTS approach provides a suitable solution before
   continuing this discussion.

NDR SESSION

   MavisC/MikeG: The NDR editors discussed BryanR's request for an
   ANY area.  We don't have an objection to this, but think that a
   better solution might be to use the UBL documents as specified
   in our schemas and then embed them in a wrapper containing the
   data needed for local requirements.

   JonB: Or better yet, in another part of the message (for
   example, another MIME part in an ebXML message).

   StephenG: Or in the CEFACT document header.

   AGREED to record this and continue the discussion next meeting.
   BryanR is invited to join the NDR editors in their conference
   call immediately preceding the Atlantic meeting 13 July.

NEXT MEETING

   *** Remember that we are skipping the Atlantic and Pacific
   calls next week.  The next Atlantic TC call will take place 13
   July. ***

   Sign off on the 1.0 SBS.

   Discuss use of ATG2 data type schemas.

   Check on the status of CCTS schemas wrt attributes needed for
   UBL.

   Check on whether CCTS provides a mechanism for categorizing
   elements by domain that could be used to address the
   requirement to subdivide the Reusables.

   Continue the discussion of ANY and the other requests from
   BryanR, to wit:

      (1) A reconsideration of our prohibition of XSD ANY, because
      there are regional laws requiring the inclusion of specific
      information, and we need an extensible content area to
      handle this; (2) Restrictions on strings in UBL content to
      ensure that the content consists of more than white space,
      for example through length or minlength facets; (3)
      Reconsideration of our prohibition of appinfo, because there
      are many cases where one element is conditional on another;
      this would give Scehamatron (for example) the data it needs
      to do conditional/contextual validation.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]