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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-dev message

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


Subject: RE: [ubl-comment] UBL LATAMR


Carlos,

 

I reply to the ubl-dev mailing list instead of the ubl-comment mailing list because this is a support question and not a question about the ubl 2.1 prd3 review (which was already concluded)

 

The UBL address type has been setup to be as flexible as possible to be able to represent any possible address formatting combination. Because of this there are no mandatory elements in this address type.

The object provides various ways of representing address:

 

1)      Populate the elements that are used in a specific address format

2)      Populate only the “0-n” address line with an already formatted address

3)      Use both options at the same time, so a formatted address and individual elements

4)      Add a Address Format Code to show how the various elements should be combined to form a printable address (but not provide that formatted address in the object)

5)      Any other representation that you would like to use and agree upon with your trading partners

 

You say that the UBL Address Object does not have localization but I am not sure what you mean by that. Could you explain that more?

(I see that for each element you can specify the language that is used for example)

 

Here is how we have implemented this part:

 

When we for example want to represent a Brazilian address in the UBL addres object we first look at this page:

http://bitboost.com/ref/international-address-formats/brazil/brazil.html

 

we look at the example:

    Juan Smith

   Rua Visconde de Porto Seguro 1238       [street name + house/building number]

   Sao Paulo-SP                            [city-ProvinceCode] Yes, São Paulo is properly written with an ã, but this will still work.]

   04642-000                               [postal code (equivalent of what in the U.S. is a 'zip code')]

   BRAZIL                                  [country name]   (for mailing across international borders)

 

and based on that we determined that we would use the following UBL address type elements:

(not in the exact XSD order, but in the order as represented above)

 

cbc:StreetName                      “Rua Visconde de Porto Seguro “

cbc:BuildingNumber             “1238”

cbc:CityName                         “Sao Paulo “

cbc:CountrySubentityCode    “SP “ (Here I used the official code for the Province of Sao Paulo)

cbc:PostalZone                     “04642-000”

cac:Country

        cbc:IdentificationCode    “BR”  (here I used the 2 letter ISO code for Brazil)

        cbc:Name                             “BRAZIL”(here I used the ISO name in CAPITALS)

 

Of course you can add additional elements that you feel like adding to make the address more detailed. For the other examples you could for example add cbc:CitySubdivisionName to give the neighborhood  and cbc:BlockName for that Brazila address.

 

I hope this is more clear on how to use this part of the UBL specification.

 

Kees Duvekot

 

 

 

Van: Carlos Martin [mailto:cmfermdp@gmail.com]
Verzonden: maandag 22 april 2013 21:25
Aan: ubl-comment@lists.oasis-open.org
Onderwerp: [ubl-comment] UBL LATAMR

 

Hi, 

 

I work as IT Consulting in Argentina. I´m Working in a company which have some branchs in other South America Countries, and I want to ask about the Address Object Class.

The Addresses Format in South America aren´t  the same in all Countries, and UBL Address Object doesn´t have localization...

The UBL LATAMR SubCommite, has produce some localizations? or have I extend the address object.?

 

thanks for your answer.

Carlos.



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