ubl — archive

Meeting Minutes UBL Joint meeting Mar 23rd 2004

From: Bill Meadows
To: [email protected]
Date: Tue, 23 Mar 2004 19:03:00 -0000

 MHonArc v2.5.0b2 -->
















ubl message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Meeting Minutes UBL Joint meeting Mar 23rd 2004




From: Bill Meadows <[email protected]>
To: [email protected]
Date: Tue, 23 Mar 2004 11:18:11 -0800






Attendees: Lisa Seaburg, Tim McGrath, Michael Dill, Stephen Green, Mike
            Grimley, Bill Meadows, Marion Royal, Sylvia Webb, Sue
            Probert, Monica Martin, Paul Thorpe, and Gunther Stuhec.

1. Appointment of a chair.  Tim McGrath was nominated by Marion Royal,
     Bill Meadows seconded.  Tim was appointed.

2. Assignment of a secretary to take minutes.  Tim assigned Bill.

3. Review of issues on version 9.1 of the schemas. (from various emails)

   1)  We are missing a required 'Version' element in the documentation
       of every data type. (We seem to be missing it in all the other
       schemas as well, for data types *and* BIEs.)
   Agreed.
   AI - David - add to cc parameters and populate in schemas

At this time Gunter announced he was going to drop off.
Steve asked him about the cc parameter schemas not being in the NDR.
Gunther replied ' We forgot it'.  Gunther dropped off at 8:25 am PST.

  2)There are some documentation elements whose names do not reflect
    those specified in the NDR: Occurrence, & ComponentType.
    should be Cardinality & CategoryCode

   AI - change occurrence to cardinality.
    I did not capture a resolution to catogorycode/ component type.  -
    Open?	

  3) In the CCT schema, the attribute definitions all declare
     'use="optional"' even though it is the default value and does not
     need to be declared. In the UDT schema, 'use="optional"' is *not*
     declared (except in the restriction of 'cct:IndicatorType'). Do we
     want/need to be consistent here?
   AI- consistently, explicitly spell out 'use="optional"'

  4) The documentation elements are not listed in the order specified in
     the NDR.
   AI - Mike G - change the order in cc parameter schema
   AI - David - recognize when building the schemas

  5) We should have ccts:DataType in the documentation for each secondary
     representation term (e.g. Video has a data type of Binary Object.
     Type). It documents what the "base=" is.
   AI- David - populate data type of secondary rep terms with primary rep
       term.

  6) Should have an import statement for UnspecialisedDatatypes to
     indicate this is where to get data types for any new types from.
   AI- David add import statement to top of schemas.

  7) there seems no point in a /codelist directory.  shouldn't these just
     be in '/common'?
   AI- Tim add to tomorrows agenda for discussion.


8)  confirm that the statement...
       <xsd:element name="CurrencyCode" type="CurrencyCodeType">
        <xsd:annotation>
         <xsd:documentation>This element MUST be conveyed as the root 

           element in any instance document based on this Schema
           expression</xsd:documentation>
        </xsd:annotation>
       </xsd:element>
     - is correct for each code list schema (obviously with the
       appropriate code list name).
   AI - David - don't include root element in code list schemas

  9) We only need cbcs for each "BBIE property" (PropertyTerm+Rep.Term) -
     not a cbc for each qualified BBIEs.  although i am then not sure how
     we can name any qualified BBIEs.
   AI - Mike G -research and give example(s) for discussion Wed.

  10) We should have a ccts:DataTypeQualifer value for each code type (in
      the documentation).
   AI - David populate in schema documentation.

  11) Minimum and Maximum Temperature do not have a correct ccts:DataType
     (it says <ccts:DataType>. Type</ccts:DataType>)
   AI - Tim - remove definition of data type for ASBIE's in model.

  12) There appears to be an inconsistency in layout between the cac
      schema and the document schemas.  The Common Aggregate Components
      schema lists elements at the top and document schemas list them at
      the bottom.
   AI - David - add import statement for Spec data type for all document
        schemas.

  13) In the UDT schema, the 'DateTimeType' definition is what I would
      expect; there is a restriction on cct:DateTimeType that removes the
      infamous 'format' attribute.
      However, the datatypes with a base of 'cct:IndicatorType' or
      'cct:NumericType' define a restriction, but then include the
      'format' attribute, which in effect makes it no different than the
      CCT datatypes.     Is this what was intended?
   AI - David  remove format attribute on UDT indicator type, and numeric
        type (and those based on)

Brief discussion of Mark Crawford's comments.  It was decided
we need Mark to be present to explain and give examples of his
comments that have not been addresses in the above comments.


New Business - Next Call 8am PST Wed Mar 23rd.

 
=============================================================================
           ______
          /_____/\             Bill Meadows
         /_____\\ \            XML Web Services Project Manager
        /_____\ \\ /           Sun Microsystems Inc.
       /_____/ \/ / /          7788 Gateway Blvd. NWK18-206
      /_____/ /   \//\         Newark, California  94560
      \_____\//\   / /         Phone (510) 936-4928
       \_____/ / /\ /          Email: [email protected]
        \_____/ \\ \           =====================================
         \_____\ \\
          \_____\/ 

 
=============================================================================
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information.  Any unauthorized review, use, disclosure or
distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy
all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~















[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]