JSON packaging proposal for CLDR

[Rafael Xavier]

About locale coverage, (just to make sure I understood correctly) currently
I download one single file full.zip in order to download all available
coverage for all functionalities. After this change, I'll need to download
tier-1, tier-2, modern and all of a given functionality in order to
download all available coverage of such functionality.

Is that correct?

PS: Initially, I was expecting an incremental coverage: tier-1 ⊆ tier-2 ⊆
modern ⊆ all. If the sets are not incremental, should all be renamed
leftover? :)

On Wed, Jan 14, 2015 at 12:30 AM, Rafael Xavier <rxaviers at gmail.com> wrote:

> Hi John,
>
> Please, could you include the size of each package? I'm interested to know
> how the functionality break down will balance the bytes weight.
>
> Thanks
>
> On Wed, Jan 14, 2015 at 12:19 AM, John Emmons <emmo at us.ibm.com> wrote:
>
>> Hi everyone,
>>
>>    I have been working on a design proposal for packaging of CLDR's JSON
>> data, for the 27 release and following.  Please review and comment:
>>
>>
>> https://sites.google.com/site/cldr/development/development-process/design-proposals/json-packaging at
>> your convenience.  You should be able to put your comments directly into
>> the document.
>>
>> I would like to bring this proposal for approval to the CLDR TC at NEXT
>> week's meeting, on 2015-01-21.
>>
>>
>> Regards,
>>
>> John C. Emmons
>> Globalization Architect & Unicode CLDR TC Chairman
>> IBM Software Group
>> Internet: emmo at us.ibm.com
>>
>> _______________________________________________
>> CLDR-Users mailing list
>> CLDR-Users at unicode.org
>> http://unicode.org/mailman/listinfo/cldr-users
>>
>>
>
>
> --
> +55 (16) 98138-1582, +1 (415) 568-5854, skype: rxaviers
> http://rafael.xavier.blog.br
>



-- 
+55 (16) 98138-1582, +1 (415) 568-5854, skype: rxaviers
http://rafael.xavier.blog.br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20150114/f6283c61/attachment.html>