[ire] CSV: contactPostal clarification question

[Klaus Malorny <[e-mail]>]

Hi all,

I am still a bit puzzled about the "contactPostal" table, containing the 
internationalized/localized postal data (section 5.3.2, pages 55 et seqq. of [1]).

On the one hand, there is a flag field, csvContact:fPostalType, which indicates 
whether name, organization, street, city, state/province, postal and country 
code fields shall be regarded as internationalized or localized. On the other 
hand, these fields may contain their own "isLoc" attribute, indicating their 
designation.

Are these alternatives? I.e. one registry could decide to use the fPostalType. 
In this case, the fields themselves would not use the "isLoc" attribute. A row 
would contain either the internationalized _or_ the localized data set, but 
never both. So the registry would have to actually use two rows in the case that 
it wants to provide both. Or the registry could decide not to use the 
fPostalType, but to add the isLoc attribute to the field definitions. In this 
case, a row could contain data for the internationalized _or_ localized _or_ 
both data sets.

Is this correct?

Regards,

Klaus


[1] http://tools.ietf.org/html/draft-arias-noguchi-dnrd-objects-mapping-05