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: Outcomes of Wednesday co-ordination meeting


Please find attached a summary of the outcome of the call.

Thanks to anne for notes upon which this is based.

jon.bosak@sun.com wrote:
[jon.bosak@sun.com:]

  
Anne will be posting the minutes from this morning's call
    

I've just been informed that Anne has sent rough notes to Tim, who
will be putting the outcomes in final form.  So this means that we
should be seeing them Thursday morning Perth time, perhaps late
Wednesday in the U.S.

Jon

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ubl/members/leave_workgroup.php.

  

-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160


Call Held from 0700 until 0930 California time on Wednesday 17th March (to be sure, to be sure)

Attendees:
Anne
Jon
Tim
Stephen
Michael D.
Mike G. (joined at 9:25)
Bill
Lisa
Alan
Sue

Issue 1:  Structure of Specialised Data Type schemas.
Resolution: 
keep sdt schema module.
refer to it in cbc. 
leave it empty until we have specialised data types for non-codes.
we can have more than one sdt schema.
each code list schema is also an sdt schema.

Issue 2:(related to above) moving some code enumerations into sdt -
  the hard-wired ubl ones (Stephen)
Resolution: not required if we adopt the first resolution

Issue 3: use of DerivedCodeType (Tim) and any remaining related issues 
Resolution: derived code type does not give a clue as to semantic meaning.
name to use is the "name of the code"type, not derivedcodetype.
every code list schema has it's own code name type and that is what
we use when we reference it 

Issue 4: annotation-documentation for codes and what to do with 3 additional cl 
components in model (ie. credits) (David)
Resolution: 
"CodeListNamespacePrefixID" is used when encoding schemas and does not need to be documented as metadata.
"CodeListDescription" and "CodeListCredits" will not be used in the schemas and only appear in the models.
  
Issue 5: any remaining issues with referring directly from clsm to cct
Resolution:  were referring to cct called codetype but should alway be referring to the udt called codetype.
this is fixed now.

Issue 6: namespace prefix error noted below (Stephen)- actually specification of incorrect code list for TaxSscheme. CurrencyCode.
Resolution: fixed in models for draft 9

Issue 7: date -> datetime problem noted below (Stephen)
Resolution: cctype and udt for datetime will use base of xsd:datetime.  
the udt called datetype will use base of xsd:date
the udt called timetype will use base of xsd:time

Issue 8: inconsistencies noted in #3 below (Stephen)
Resolution: David, to fix 4461_code.
Tim, changed PaymentMeansTypeCode in models to PaymentMeansCode

Issue 9: need intensive QA
Resolution: Stephen, Anne, Tim in parallel to ndr (lisa, mike) 

Issue 10: final format for code names in enumerations for 1.0 
Resolution: update of code list names from this morning's discussion + operator code values (Anne)
we aggreed to include in list of enumerated values the name as well.
David add code name to enumeration with each content.
Example is...
<xsd:enumeration value="USD">
    <xsd:annotation>
     <xsd:documentation>
      <CodeName>United States Dollar</CodeName>
     </xsd:documentation>
    </xsd:annotation>
</xsd:enumeration>

Issue 11: operator code - is that all there is? 
Reolution: stuck with 'operator' name for this, even though only applicable to 'rate' calculations
  
Issue 12: 'format' supplementary components not in cct schema module (MikeG)
Resolution:  These should be added to the CCT schema for Numeric, Indicator and DateTime (as per models).  
this is CCTS requirement.
we just encourgae implementations not to use them.
David to fix.

Issue 13: truncation of definitions (Stephen)
Example:  <ccts:Definition>A character string (letters, figures or symbols) that for
  brevity and/or language independence may be used to represent or replace a
  definitive value or text of an Attribute together with relevant
  supplementary information. Date Time. Type Identifier. Ty</ccts:Definition>
Resolution: David to fix.

Issue 14: remaining occurance of OrderAcknowledgementCode in sdt (Stephen)
Resolution: Correct name is AcknowledgementResponseCode.
David to fix.

Issue 15: base of code types in code list schema modules (cct or sdt) (Tim)
Resolution:  always udt - all codes based on udt code type (similar to Issue 5)
has been taken care of already.

Issue 16: ownership (and updating of ) core component parameters (Tim)
Resolution:  schema is used to define meta data for documentation.
Should be synchronised with LC models and NDR rules.
Need updating to reflect current metamodel.
Code List representation needs to use the corrected names to make clear relationship of this info and the schemas it appears in.
Ownership - should be driven by models so it is LC data. Tim to send proposed changes to LC list for comment
Updating - currently is a hand crafted schema.  GEFEG can build 1.0 version, but we can look at generating it later.
Set of NDR rules related to metadata we need to capture for each bie, dt, and cct should be aligned.  
Once we get consensus on titles we can generate draft 9 models.  this should not delay other schema modifications
Even if we compromised on parameters for general documentation, the ones we use in Code Lists should be fixed.

Issue 17: declarations for imported schemas (Stephen)
Resolution:  decision on issues 1 makes this unnecessary (at this stage - but it may come up again).

Issue 18: finalization/alignment of acronyms and acronym list (LC/NDR)
Resolution: The approved acronyms for 1.0 are...
  id
  guid
  uri
  undg
  cv2

Issue 19: remove of 'use' subfolder in codelist subfolder (extra layer w/o value?) (Stephen)
Resolution: yes, David to change
  
Issue 20: who owns / will update the 'external' schema diagram
Resolution:  ndr owns it.  as soon as schmeas are finalized, should be updated.

Issue 21: need for uml diagrams from Dave Carlson and how to present
Resolution:   Advise Dave when we get better understanding of deliverable needed.

Next meeting:
There will be two meetings Friday 19 March to finish up the 1.0
schemas.  Both will be at the usual UBL number:

   #############################################
   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
   #############################################

>From 5-7 a.m. California time (1-3 p.m. in London, 2-4 p.m. in
Berlin, 9-11 p.m. in Perth), Tim, Stephen, and Michael (at a
minimum) will meet in a schema generation working session.  This
meeting is open to anyone who wants to participate.




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