- From: Sarah Wilkin <swilkin@apple.com>
- Date: Tue, 28 Oct 2003 09:39:21 -0800
- To: Jonathan Robie <jonathan.robie@datadirect.com>
- Cc: public-qt-comments@w3.org
Thanks for the other fixes. The basic issue with this comma problem
(and the whitespace mentioned elsewhere), is these oddities make
extraction from the use cases for testing much more difficult. I
understand the comma is not text. It seems it should still be there
because the output is still a sequence; it is not inside another
element which would make the elements be children.
For example, if the query were
<result>
{
<section_count>{ count(doc("book.xml")//section) }</section_count>,
<figure_count>{ count(doc("book.xml")//figure) }</figure_count>
}
</result>
then I would not expect commas in the result.
Perhaps a separate document should be available that lists the expected
and actual results in their normative form. The other two sections that
are basically impossible to extract are the SGML section and the
relational data section. It seems odd that a query must be written to
"reconstruct" the xml from the html data tables presented.
Cheers,
--Sarah
On Oct 27, 2003, at 7:36 PM, Jonathan Robie wrote:
> At 02:09 PM 10/15/2003, Sarah Wilkin wrote:
>
>> Expected result is written as:
>> <section_count>7</section_count>
>> <figure_count>3</figure_count>
>>
>> it should be:
>> <section_count>7</section_count>,
>> <figure_count>3</figure_count>
>>
>> (comma after section_count element)
>
> I suspect you are using Galax, which does format the output with a
> comma.
>
> This query has two element constructors, separated by a comma. This
> comma is not text, it separates the two constructors. The output
> should not have a comma.
>
> Jonathan
Received on Tuesday, 28 October 2003 12:39:11 UTC