OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

codelist-comment message

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

Subject: Public Review of Codelist Requirements

I am posting this on behalf of Simon Heinrich of C24 and FpML.  Cheers,  

-------- Original Message -------- Subject:  Public Review of Codelist
Date:  Mon, 06 Nov 2006 19:15:56 +0000
From:  Simon Heinrich <simon.heinrich@c24.biz>
To:  codelist-comment@lists.oasis-open.org

In SWIFT FIN and in FIX I've seen several instances of enumerations  
dictating a
range of values OR one of an additional set of values, e.g. the value must  
be in
the range 000 to 99999 OR must equal one of 199999, 299999, 399999 ...  
etc. Is
there any suggested way to handle these types of enumerations, (other than
entering every single value into the codelist) ?

I see in the code list representation requirements v1.0, under item F .1  
should be possible to represent code lists that cannot be enumerated",
consideration has been given to some types of non enumeratable lists, but  
does not cover this case explicitly.


Simon Heinrich
Product Development Director, C24
Chair, FpML Validation Working Group

Anthony B. Coates
Senior Partner
Miley Watts LLP
Experts In Data
+44 (79) 0543 9026
Data standards participant: ISO 20022 (ISO 15022 XML), ISO 19312,  

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