search

AOMediaCodec / av1-avif

AV1 Image File Format Specification - ISO-BMFF/HEIF derivative
https://aomediacodec.github.io/av1-avif/
BSD 2-Clause "Simplified" License
450 stars 40 forks source link

Use of `value` definition type for terms that are not CSS values #218

Open tidoust opened 8 months ago

tidoust commented 8 months ago

The spec uses value definition types for some of its definitions, e.g. av01.

It's tempting to use the value type for such values but, despite the generic name, that type was defined for CSS values, see Bikeshed's documentation. The use of value confuses tools that parse specs to extract semantic information, because that makes them think that the spec defines CSS terms.

There is no better definition type than dfn for now for such values. The possiblity to create one is being tracked in https://github.com/speced/spec-dfn-contract/issues/6

cconcolato commented 7 months ago

Are there tools that parse the AOM specifications? and that cannot associate a non-CSS semantic for "value" definitions?

tidoust commented 7 months ago

We added the AOM specs to browser-specs, which means they now get crawled to produce data in Webref. Webref powers the cross-references database used in Bikeshed and ReSpec. The data and CSS extracts in Webref are also used in some IDEs and analysis tools. Whether the use of value creates an actual problem for them, I do not know!

For the CSS extract, we're trapping the problem through a patch in Webref to forget about the values for now. The definitions still reach Bikeshed and ReSpec as CSS definitions. That's slightly incorrect but that should not create any major issue!