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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-cmsc message

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


Subject: Minutes UBL CM call 17 March 2004


Minutes for the UBL CM call 03.17.04 attached.

All the best,
	F.
.-

Fabio Arciniegas - Chief Technical Officer   | "So far as I can remember,
           Postgraphy, LLC                   : there is not one word in
                                             | the Gospels in praise of
   http://www.postgraphy.com/about/faa       | intelligence" - Bertrand
Russell

    _        _     
| ||_)|     / |\/| UBL Context Management SC
|_||_)|_    \_|  | Minutes Conference call 03.17.04 (16:30 PT)

Attendants:
    Anne Hendry      (AH)
    Sylvia Webb	     (SW)
    Eduardo Gutentag (EG)
    Tim McGrath      (TM)
    Fabio Arciniegas (FA)

Not attending, with regrets:
    Mark Crawford

|                  (formatted to 70 cols)                            |
| Legend: (-) General Discourse  (=) Key agreement/decision	     |


- After an 8 minute wait, the meeting starts with comments from all
  participants regarding the low attendance.

- EG asks for comments on the document, especially sections 5 and 6.

- TM points out that section 6 is generally correct, and its contents
  are the only approach viable given the time frame.

- TM points out that section 5 is generaly irrelevant given the fact
  that the pointed document will not have customization content for
  version 1.0, and there is no way for the CM group to define
  customization guidelines given the fluid nature of code lists in the
  recent past after the washington F2F and the 1.0 goals/timeframe.

= EG proposes the deletion/editing of section 5, so it reflects the
  fact that 1.0 does not talk about customization of code lists. The
  group agrees on making section 5 a reference to the code lists
  document pointing out that customization guidelines for code lists
  is only forseen as part of 1.1 and beyond, not a matter
  treated/tractable in 1.0.

= EG points out the recurrent problem of referencing other documents
  inside UBL, and the groups agrees on his suggestion of bracketed
  prose references to other documents until direct links can be made.

- TM makes a references to other forms of customization and the group
  agrees on not going there and concentrating on the comments to the
  document, with 1.0 release in mind.

- AH raises the question about versioning in the title and whether it
  is convenient to make explicit in the title of the document (not
  only on the name of the file) the fact that this document applies
  especifically to UBL 1.0

= The group agrees to include 1.0 in the title.

- AH points out that being specific in the title about 1.0 coupling is
  going to be applicable to other documents generated by the UBL TC.

= The group agrees on the need to revise section 6 terminology to
  ensure that it is still in sync with the current versions of the
  documents is based on.

- AH raises the question about changing section 1.1 to reflect that
  the current version of the document is "informative",
  while procedural content will be included only on version 1.1 and
  beyond. 

= The group agrees that 1.1 should contain a clear invitation for 
  feedback from users rather than the vague sentence in (3).


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