Re: Spec review request: CSV on the Web

> [snip]
> pattern:
> Could you write "und" instead of und (unquoted)? For those of us
> reading the document with a Screen Reader or similar tool (actually a
> plain text serializer in my case), the monospace formatting is lost.

monospace formatting is used in a number of places, and double-quoting this one in particular doesn’t seem consistent; you’d need to double-quote many other cases as well, which would be a substantial stylistic change. Could this be solved with a CSS style for an appropriate @media selector? Are there some uses of <code> you think should be handled different than others? Can we do this through CSS?

>> [snip]
> 
> Offhand, figure 1 [3] was generated at a resolution which is too small
> to read at 100%; text runs together... Also, the gray background is
> unhelpful.

This is pretty standard ReSpec formatting for examples. Could this be addressed using a media-specific style?

> [snip]
>> A boolean atomic property taking a single value
> 
> isn't `taking a single value` redundant for `boolean`?

Consistent with wording for other properties wins, IMO.

> [snip]
>> This property is irrelevant if the separator is null or undefined, but this is not an error.
> 
> `but this is not an error` doesn't make sense / read well

Scans okay to me; do you have a specific suggested wording that would improve it?

I took care of the rest of the comments from this email in a pull request [1]. I’ll leave comments on the conversion documents to one of the editors of those documents.

Thanks for such great attention to detail.

Gregg

[1] https://github.com/w3c/csvw/pull/690

Received on Friday, 17 July 2015 23:52:26 UTC