OASIS Universal Business Language (UBL) TC

Re: [ubl] Groups - UBL-1.0-draft-11-models.zip uploaded

  • 1.  Re: [ubl] Groups - UBL-1.0-draft-11-models.zip uploaded

    Posted 04-04-2004 23:13
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ubl message

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


    Subject: Re: [ubl] Groups - UBL-1.0-draft-11-models.zip uploaded


    [tmcgrath@portcomm.com.au:]
    
    | i am not sure we want to have the values for codes anywhere but
    | the schemas.  it creates a potential for mis-alignment as they may
    | not represent what is in the normative schemas.  if implementators
    | want text files with the name/value pairs then they can look in
    | the schemas.
    
    That's fine; I just wasn't clear on the order of generation.  I
    agree that we don't need to include the text files.
    
    Jon
    
       Mailing-List: contact ubl-help@lists.oasis-open.org; run by ezmlm
       Precedence: bulk
       X-No-Archive: yes
       List-Post: <mailto:ubl@lists.oasis-open.org>
       List-Help: <mailto:ubl-help@lists.oasis-open.org>
       List-Unsubscribe: <mailto:ubl-unsubscribe@lists.oasis-open.org>
       List-Subscribe: <mailto:ubl-subscribe@lists.oasis-open.org>
       Delivered-To: mailing list ubl@lists.oasis-open.org
       Date: Sun, 04 Apr 2004 09:18:19 +0800
       From: Tim McGrath <tmcgrath@portcomm.com.au>
       User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
       X-Accept-Language: en-us, en
       MIME-Version: 1.0
       CC: ubl@lists.oasis-open.org
       References: <200404030053.i330rRv2852370@jurassic.eng.sun.com> <001201c4198c$152468c0$0f5230d5@user7i6bxplv6p>
       Content-Type: multipart/alternative;
        boundary="------------060600000208050603000300"
       X-AntiVirus: Reynolds Virus Scan OK. http://reynolds.net.au/policies/viruses/
       X-ReynoldsPurgeDate: 1081041504 
       X-Spam-Status: No, hits=0.1 required=7.0
    	   tests=EMAIL_ATTRIBUTION,HTML_20_30,HTML_MESSAGE,REFERENCES,
    		 USER_AGENT_MOZILLA_UA,X_ACCEPT_LANG
    	   version=2.55
       X-Spam-Level: 
       X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
       Content-Length: 5911
    
       --------------060600000208050603000300
       Content-Type: text/plain; charset=us-ascii; format=flowed
       Content-Transfer-Encoding: 7bit
    
       i am not sure we want to have the values for codes anywhere but the 
       schemas.  it creates a potential for mis-alignment as they may not 
       represent what is in the normative schemas.  if implementators want text 
       files with the name/value pairs then they can look in the schemas.
    
    
    
       Stephen Green wrote:
    
       >Jon
       >
       >Just to note that the last draft of spreadsheets was draft 12 rather than
       >draft 11
       >http://lists.oasis-open.org/archives/ubl/200403/msg00257.html
       >
       >The matter of codelists:
       >Anne sent the latest update of values (held in text files) to Michael
       >around 17th March. I expect we need a copy of these for the package
       >from Anne.
       >
       >Four codelists (Country, Currency, OrderAcknowledgement
       >and Payment Means) simply have values coming from Edifact and these
       >are generated from the Edifix tool with the latest values, as far as I know.
       >
       >The other codelist data (metadata) is held in the spreadsheet called
       >the Specialised DataTypes model spreadsheet. This will need updating
       >with 1.0 final values for some metadata (URLs) as part of the creation of
       >the
       >actual final set of models and Schemas.
       >
       >All the best
       >
       >Steve
       >
       >