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: Re: [ubl] Re: AW: UBL schema tests


Forgot to attach the diagram...

Anne Hendry wrote:

> Hi Lisa,
>
> Good question as to minutes.  I took some notes but expected the final 
> definitive would come with the final version of the  ndr doc.  Is that 
> available?  I haven't seen it.  The only one I have is dated 24 
> February.  I did take some rudimentary notes on this part of the 
> discussion, if you can glean from this:
>
> ...
> code lists shcmea: secton 3.7 of ndr defines rules for code list.
> develop ss with unspecialized and unspecialized dts.
> here would like to get concensus.
> need rep term qualifier - need 57 rep term qualifiers for sdts.
> no, only for code lists.
> St: need to make names from code lists, not from codes.
> replacing prefix with name that begins with rep term qualifier.
> J: in lcs bin?  Tim: yes.
> A: only for 12?  MD: must be done for all datatypes.
> ST; no, could just do for codes; only need one dt for ones [codes] we 
> don't use.
> MD/TM/SG: work out in next 24 hours.
>
> MC: this was Sue and Stig.
> MD: ok, used namespce prefix as rep term qualifier
> MC: for specialized dt.
> ...
>
> So, in the end, what I now recall is that there was a bit of a 
> standoff between whether or not we needed to have something for all 
> the codes or just the 12, and Michael was to work this out with Tim 
> and Stephen (lcsc).  I think Michael was on the edge of agreeing to go 
> with Tim/Stephen's suggestion of only having 12 dts (the ones for the 
> codes we specify) and using the same (only one) prefix for all the 
> others.  Is this what would preclude the need for the specialized cl 
> module?
>
> To hopefully help this process I've attached the graphic that we were 
> using at the f2f.  May not be the final version after all the tweaks 
> from Mark based on conversations, but pretty much the same, and we are 
> currently talking about the two lower-right boxes contained in the 
> lower (blue/green) half of the diagram.
>
> -Anne
>
> Lisa-Aeon wrote:
>
>> Stephen,
>> You were not able to see the drawing Mark had for us at the Face to 
>> FAce,
>> but it included a Code List Schema Module.  We need to be aligned 
>> here, if
>> there are decisions made, do we have minutes or something from the 
>> meetings
>> so that we can see what happened and why?
>>
>> What I have attached is just the external modules part of his 
>> drawing, saved
>> as a BMP, hopefully you can open and see it.  I am confused, I guess 
>> because
>> I missed so much of the meeting.
>>
>> Lisa
>>
>> ----- Original Message ----- From: <stephen_green@seventhproject.co.uk>
>> To: "Lisa-Aeon" <lseaburg@aeon-llc.com>
>> Cc: "Tim McGrath" <tmcgrath@portcomm.com.au>; "David Kruppke"
>> <kruppke@gefeg.com>; <ubl@lists.oasis-open.org>; "Marty Burns"
>> <Burnsmarty@aol.com>
>> Sent: Monday, March 08, 2004 12:12 PM
>> Subject: Re: Re: [ubl] Re: AW: UBL schema tests
>>
>>
>>  
>>
>>> Lisa and All
>>>
>>> Personally I'm not sure we now have any need of any Codelist Schema
>>> Modules. It was decided that Specialised DataTypes could be used for
>>> those Codelists which need XSD validation.
>>> Is there any need for anything other than the SDT Schema Module for
>>> these?
>>> If so then we would need a set of Codelist Schema Modules but I think
>>> it was decided, wasn't it, that there would be one prefix 'sdt:' for
>>> such codes.
>>> The other need for Codelist Schema Modules might have been for the 
>>> other
>>> codes but these, it was decided wasn't it, would not have XSD 
>>> validation
>>> so therefore they would surely not need a Schema -  they would have the
>>> 'udt:'prefix, the CodeType being included in the Unspecialised
>>> Schema Module.
>>> If this is wrong could someone explain quickly.
>>> I *think* (not sure) that Codelist Schema Module may be a vestige from
>>> the previous (Montreal) codelist solution (along with the codelist
>>> folders and its subfolders). Someone please correct me again.
>>>
>>> Steve
>>>
>>>
>>>
>>> Lisa-Aeon <lseaburg@aeon-llc.com> wrote on 08.03.2004, 15:36:45:
>>>   
>>>
>>>> Marty Burns and I are reviewing the draft 7.1 codelist right now also.
>>>>     
>>>
>> We
>>  
>>
>>>> are alittle confused, we are using Marks Visio drawing from the 
>>>> face to
>>>>     
>>>
>> face
>>  
>>
>>>> and there seems to be missing pieces of the codelist stuff.  Is there
>>>> supposed to be a Codelist Schema Modules?  not just Unqualified 
>>>> Codelist
>>>> module.  Where will it reside, and what will be in it?
>>>>
>>>> Also, in the Common Basic Components, and in the CCT there are types
>>>>     
>>>
>> that
>>  
>>
>>>> have attributes that are code list values, but they are not inheriting
>>>>     
>>>
>> from
>>  
>>
>>>> codelists.  For example - Amount.Type.
>>>>
>>>> We need some answers on how this is all supposed to work......neither
>>>>     
>>>
>> Marty
>>  
>>
>>>> or I were in the meeting where this was discussed at the F2F.  We are
>>>>     
>>>
>> trying
>>  
>>
>>>> to see how the CCT and CCP are working within the Codelist modules, 
>>>> and
>>>>     
>>>
>> we
>>  
>>
>>>> are not seeing it.  For example:  Codetype contains a listID that 
>>>> is not
>>>>     
>>>
>> the
>>  
>>
>>>> CCP listID.
>>>>
>>>> Not having these answers is slowing down the review of this work.  Can
>>>> someone please get back to us.
>>>>
>>>> Lisa and Marty.
>>>>
>>>>
>>>>
>>>>
>>>> ----- Original Message ----- From: "Tim McGrath"
>>>> To: "David Kruppke"
>>>> Cc:
>>>> Sent: Friday, March 05, 2004 7:06 PM
>>>> Subject: [ubl] Re: AW: UBL schema tests
>>>>
>>>>
>>>>     
>>>>
>>>>> we obviously need to become more co-ordinated in this work.
>>>>>
>>>>> the code list mechanism used here is not what i expected to see.  for
>>>>> example, in Order we use the Data Type "ISO4217 Alpha_ Code. Type"
>>>>>       
>>>>
>> for
>>  
>>
>>>>> the BBIE called "Order. Transaction Currency. Code".  you have also
>>>>> taken "ISO4217 Alpha" as a Qualifier for the Representation Term and
>>>>> thereby changed the Dictionary Entry Name - we don't want to do this.
>>>>>
>>>>> also,  why do we still have a 'DerivedCodeType'?  Shouldn't the
>>>>> SpecialisedDataType just refer to the namespace for the precise code
>>>>> list.  Is this just a legacy of the old code list mechanism (and 
>>>>> hence
>>>>> an unnecessary level of referencing) or does it add some value?
>>>>>
>>>>> finally, the structures you build in the Specialised Data Types still
>>>>>       
>>>>
>>
>>  
>>
>>>>> use the old/incorrect attributes and xsd:datatypes.  these should now
>>>>>       
>>>>
>> be
>>  
>>
>>>>> taken from those in the models.
>>>>>
>>>>> to help synchronise ourselves -  i have uploaded the latest complete
>>>>> models to the UBL LC web page and just so we can make sure we are
>>>>> talking about the same things, i am renaming these models 'draft 
>>>>> 7' so
>>>>> we can forget the versions and sub versions below this.  the link
>>>>>       
>>>>
>> is...
>>  
>>
>> http://www.oasis-open.org/apps/org/workgroup/ubl/ubl-lcsc/download.php/5786/UBL-1.0-draft7-models.zip 
>>
>>  
>>
>>>>>
>>>>> David Kruppke wrote:
>>>>>
>>>>>       
>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> please find enclosed the file "draft-6.1.zip". It includes the
>>>>>>         
>>>>>
>>>> "draft-6.1"
>>>>     
>>>>
>>>>>> schema modules.
>>>>>>
>>>>>> These files are based on Tims models.
>>>>>>
>>>>>> The codelists "ChannelCode" and "CurrencyCode" contain already 
>>>>>> codes,
>>>>>>         
>>>>>
>> the
>>  
>>
>>>>>> appropriate specialized datatypes as well.
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>>
>>>>>> David
>>>>>>
>>>>>>
>>>>>>         
>>>>>
>>>>> -- 
>>>>> regards
>>>>> tim mcgrath
>>>>> phone: +618 93352228
>>>>> postal: po box 1289   fremantle    western australia 6160
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 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. 
>>
>>  
>>
>>>>>       
>>>>
>>>> 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. 
>>
>>  
>>
>>
>>
>> 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. 
>>
>>
>>  
>>
>
>
>
> 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. 
>
>

external_modules_flow.pdf



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