Inlining localized message bundles

[Henry Stapp]

Problem: The current spec requires that localized message bundles be
stored as external references. This may complicate development for
developers who wish to deal with a single file, and it also
complicates the serving of Gadget XML by containers, since multiple
XML files need to be hosted.

Proposed Solution: We propose that the Local element allow inline
message bundles, in addition to the current externally located
bundles. To use an inline message bundle, leave out the messages
attribute of the Locale element, and include the messagebundle element
within the Locale element.

Usage:
<Locale lang="en" country="us">
<messagebundle>
<msg name="title">This is the message title.</msg>
</messagebundle>
</Locale>

Brian Frisch & Henry Stapp
MySpace

[Evan Gilbert]

+1

In general, I think we should move to a model where all XML spec elements can be in the same or in separate files. This would unify recent discussions on external <Content> sections as well. The idea would be:
- <Locale src="http://foo.com/bar"/> would automatically inline or replace the contents of the <Locale> tag with the contents of http://foo.com/bar.
- <Content src="http://foo.com/bar"/> would do the same
- etc.

I don't think we should do this in the 0.8 or 0.9 timeframe, but would be great to unify these in the future, so +1 on this specific proposal for 0.8.

[Kevin Brown]

On Wed, Apr 16, 2008 at 1:54 PM, Evan Gilbert <uid...@google.com> wrote:

+1

In general, I think we should move to a model where all XML spec elements can be in the same or in separate files. This would unify recent discussions on external <Content> sections as well. The idea would be:
- <Locale src="http://foo.com/bar"/> would automatically inline or replace the contents of the <Locale> tag with the contents of http://foo.com/bar.
- <Content src="http://foo.com/bar"/> would do the same
- etc.

I don't think we should do this in the 0.8 or 0.9 timeframe, but would be great to unify these in the future, so +1 on this specific proposal for 0.8.

+1 from me as well, and I agree completely with Evan.
 

On Tue, Apr 15, 2008 at 4:24 PM, Henry Stapp <hst...@gmail.com> wrote:

Problem: The current spec requires that localized message bundles be
stored as external references. This may complicate development for
developers who wish to deal with a single file, and it also
complicates the serving of Gadget XML by containers, since multiple
XML files need to be hosted.

Proposed Solution: We propose that the Local element allow inline
message bundles, in addition to the current externally located
bundles. To use an inline message bundle, leave out the messages
attribute of the Locale element, and include the messagebundle element
within the Locale element.

Usage:
<Locale lang="en" country="us">
    <messagebundle>
         <msg name="title">This is the message title.</msg>
    </messagebundle>
</Locale>

Brian Frisch & Henry Stapp
MySpace

--
~Kevin

[Zhen Wang]

+1

I also think that the <Locale> tag should be a child of <ModulePrefs>.

On Tue, Apr 15, 2008 at 4:24 PM, Henry Stapp <hst...@gmail.com> wrote:
>

[Paul Walker]

+1

In general the support of flattening out any xml instance is a good
thing for text data that can be appropriately represented directly in
that instance.

Sans the caveat for icons/images/binary data that are referenced by URIs
(much as any html page response).

[Cassie]

Spec approved for flattening message bundles into the gadget xml.