Re: Conflict between specification and Test Suite

Hi Karl,
     Yes we saw this line, our interpretation of that was, that the 
default value of linebreak should be "lf", but not that the *optional* 
attribute must be added with the default value if not found.
Adding the attribute is semantically different than the behavior 
specified in the quoted section. While the spec sets a default value for 
the attribute it doesn't say anything about injecting the attribute into 
the output when not in the input. Therefore, there is an inconsistence 
between the expected output files, which have the attribute, and the 
input files which do not. If the injection behavior is the desired 
behavior, then this should be explicitly stated in the spec.

As per the table at: 
http://www.w3.org/TR/its20/#datacategory-description the StorageSize has 
no default value if the injection behavior be desired should that not be 
reflected in the table for this category.

On 04/03/13 13:00, Karl Fritsche wrote:
> Hi Philip,
>
> "An optional |lineBreakType| attribute. It indicates what type of line 
> breaks the storage uses. The possible values are: |cr| for CARRIAGE 
> RETURN (U+000D), |lf| for LINE FEED (U+000A), |crlf| for CARRIAGE 
> RETURN (U+000D) followed by LINE FEED (U+000A), or |nel| for NEXT LINE 
> (U+0085). The default value is |lf|."
>
> I think you missed this sentence from the spec. The default is lf. So 
> the tests are correct.
>
> Cheers,
> Karl
>
> On 04.03.2013 13:53, Philip wrote:
>> Hey all,
>> there appears to be conflict between the its 2.0 specification and 
>> the expected output files for the storage size category.
>>
>> The StorageSize category defines an optional attribute, 
>> lineBreakType, which has a default value of "lf".
>> The specification explicitly states that this data category has no 
>> default values.
>> The lineBreakType attribute appears in each of the expected outputs, 
>> regardless of the absence of the lineBreakType attribute in the input 
>> file.
>>
>> This behavior is not defined in the specification, 
>> http://www.w3.org/TR/its20/#storagesize, and seems to be a conflict 
>> as no defaults are specified for this category.
>> Is this an issue with the spec or an issue with the expected outputs 
>> from the ITS Test Suite?
>> Can someone clarify what the behavior is with data categories that 
>> have optional attributes with default values?
>> Thanks,
>> Philip
>>
>>
>