On 09/30/10 10:26 AM, Alok Aggarwal wrote:
On Thu, 30 Sep 2010, Dermot McCluskey wrote:
but Keith's suggestion of having some new XML sub-element to contain
each
filename is better:
<arg name="uncompressed_files">
<li>file1</li>
<li>file2</li>
<li>file3</li>
</arg>
This is also more consistent with other parts of the new schema. Eg,
we changed
a comma-separated list of pkg names in the old schema:
<ai_install_packages>
<pkg name="SUNWcsd, SUNWcd"/>
</ai_install_packages>
to a list of sub-elements in the new schema:
<software_spec ... >
<name>SUNWcsd</name>
<name>SUNWcs</name>
</software_spec>
The <li></li> suggestion works and seems to be the
most readable.
Should the <li> be called, say, <value> instead? That
just seems to read better.
Alok
I chose "li" simply for example purposes (it's the HTML tag for a list
item). I think it'd make sense to have the tag imply 'list' somehow -
value might be confusing in that someone might try to use it for a
checkpoint argument that expects a single item:
<arg name="foo">
<value>bar</value>
</arg>
<!-- results in the checkpoint failing since it's expecting a string,
not a list -->
So a tag such as "list_item", or "li" or "list" or something of the sort
might be better. Alternatively, we could have separate <arg> and
<arglist> tags. <arg> would not have any subelements, and <arglist>
would allow subelements (<value> or <item>). That would probably be
easier to define in the schema, as well.
<arg name="foo">bar</arg>
<arglist name="foo_list">
<item>bar1</item>
<item>bar2</item>
</arglist>
- Keith
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
