AW: [ubl] [ubl-ssc] Agenda, 18 November 2004

["David Kruppke" <dill2@gefeg.com>]

Hi Anne,

I'm sorry I'm not available today in the evening.


Here are my comments to some items that were a problem: (see DK:)



--------------------------
UBL-UnspecializedDatatypes
--------------------------

  5. CCTS 2.01 doesn't specify how to generate Dictionary Entry Names
     for Supplementary Components of Secondary Representation Terms.

     UBL has implemented the Supplementary Components for both
     Primary and Secondary Representation Terms as components
     of Unspecialized Datatypes following the same naming rules
     as for CCTs (and CCs and BIEs).  That is the ISO 11179
     ObjectClass+PropertyTerm+RepTerm and seems a logical approach.
     UBL models Secondary Representation Terms (Graphic, Video,
     Date, Time, etc.) as being of the same Object Class as their
     respective Primary Representation Term, but with the Object
     Class qualified by their respective Secondary RT name.
     Example: Graphic type is of object class 'binary object'
     with an object class qualifier of 'graphic'.

     EF handles unspecialized DTs as unqualified DTs and so
     doesn't expect an object class 'qualifier' for these DTs.
     In EF, unqualified DT components should not have an Object
     Class Qualifier, and EF has no way to store qualifiers of
     'unqualified' DTs.  So that information is not being used
     in the schemas.

     Because of this EF has problems creating the Dictionary Entry
     Names for Supplementary Components of unspecialized DTs that
     represent a Secondary Representation term because it doesn't
     use Primary RT rules for these.  So EF disregards the qualifier
     and uses the Secondary RT type name as the name, as it would
     for a Primary RT (Graphic SCs would be prefixed with 'Graphic').

     AIs:
     + EF alignment: David explain how the names for CCs and SCs
                     for secondary RTs are currently generated by EF.


DK: As I said on Wednesday GEFEG will implement the qualifier for secondary
representation terms and will be able to handle the names of Supplementaries
as Dictionary Entry Names.



------------------------
UBL-Reusable and MainDoc
------------------------

  1. Because CCTS 2.01 doesn't know a "Property Term Possessive Noun"
     and "Property Term Primary Noun" we are only able to store these
     entries as user notes.


DK: GEFEG will implement a special model type called "UBL CCTS" or so. This
model type will be able to handle "Property Term Possessive Noun" and
"Property Term Primary Noun".



  6. [ELN4] A UBL global element name based on a qualified
     ccts:BBIEProperty MUST be the same as the name of the
     corresponding xsd:complexType to which it is bound,
     with the qualifier prefixed and with the word "Type" removed.

     It could be that there are elements whose names consist of
     qualifier property term, property term, and representation
     terms that refer to a complex type with the name having
     only the property term and representation term.

     AIs:
     + 1.1: David check correctness of above statement of current situation.
     + 1.1: Check that SS/EF follow rule.

DK: EDIFIX definitely follows the rule.




> -----Ursprüngliche Nachricht-----
> Von: Anne Hendry [mailto:anne.hendry@sun.com]
> Gesendet: Donnerstag, 18. November 2004 08:39
> An: ubl-ssc@lists.oasis-open.org
> Betreff: [ubl] [ubl-ssc] Agenda, 18 November 2004
>
>
>
> The UBL Software Subcommittee will meet on 19 November 2004
>
> The Atlantic call will occur at 16H00 - 17H00 UTC :
>
>  09h00 - 10h00 Thursday San Francisco
>  12h00 - 13h00 Thursday Washington
>  17h00 - 18h00 Thursday London
>  Midnight - 1:00 Friday Singapore
>
> http://www.timeanddate.com/worldclock/fixedtime.html?day=28&month=
> 10&year=2004&hour=16&min=0&sec=0&p1=0
>
>
> ** The Pacific call will not be held this week. **
>
>
> #############################################
> STANDING INFORMATION FOR UBL CONFERENCE CALLS
> U.S. domestic toll-free number: (866)839-8145
> Int. access/caller paid number: (865)524-6352
> Access code: 5705229
> #############################################
>
> Agenda:
>
> 1. Continued review of AIs from EF/SS alignment.
>    I pulled the alignment and 1.1 AIs from the
>    ssc f2f report (attached) for our discussion.
>
>      + EF alignment: Change CCT/UDT/SDT spreadsheets to use
> 'Content' value.
>      + EF alignment: For BinaryObject only have 'Content' and
> characterSetCode'
>                      in SS.
>      + EF alignment: David explain how the names for CCs and SCs
>                      for secondary RTs are currently generated by EF.
>      + EF alignment: Remove trailing space from SDT spreadsheet.
>      + EF alignment: Depending on 1.1 decision, remove
> UBL-specific codelist
>                      attributes (prefixid, desc, credits) from SS.
>      + EF alignment: Remove value from 'name' row(s) in SDT SS.
>      + EF alignment: Complete SDT import functionality.
>
>      + 1.0.1: Remove trailing space from SDT spreadsheet.
>      + 1.0.1: Add white space trimming in EF.
>      + 1.0.1: Remove format attribute from spreadsheet NumericType.
>
>      + 1.1: EF suggest other way to model secondary RTs.
>      + 1.1: Change CCT and UDT spreadsheet to use 'Content' value.
>      + 1.1: Fix order of the supplementary components in CCT/UDT/SDT
>             for "Code. Type" and "Identifier. Type"in SS.
>             [Also, neither schema nor ss are in CCTS order for
> BinaryObjectType.]
>      + 1.1: Find out if EF can preserve extra ss information
> (columns, etc).
>      + 1.1: Decide if we need UBL-specific code list attributes (eg.
>             codeListNamespacePrefixID, codeListDescription,
> CodeListCredits)
>      + 1.1: Figure out a better way to represent additional CodeList
>             attributes.  EF suggests columns for these.
>      + 1.1: Need to align SDT SS, Codelist model and EF import ability.
>             Dependency on completion of Codelist model.
>      + 1.1: GEFEG provide list of the columns from the TBG17 SS they want
>             to see in the UBL SS.
>      + 1.1: Review schema format (GSX1).
>      + 1.1: Update schemas for GSX1.
>      + 1.1: Resolve gaps in CCTS for naming requirements for SS/EF.
>      + 1.1: ELN4 conformance - Check that SS/EF follow rule
>      + 1.1: DOC3 conformance
>      + 1.1: respond to Mark's comment on ATN1.
>      + 1.1: Check validity of SSM10 rule w.r.t UBL implementation.
>             (NDR issue #10)
>
> 2. Other business.
>
>
>
>
>
>
>