- From: Jonathan Kew <jfkthame@googlemail.com>
- Date: Wed, 26 May 2010 23:23:43 +0100
- To: Sylvain Galineau <sylvaing@microsoft.com>
- Cc: Tal Leming <tal@typesupply.com>, Jonathan Kew <jfkthame@googlemail.com>, Vladimir Levantovsky <Vladimir.Levantovsky@MonotypeImaging.com>, Christopher Slye <cslye@adobe.com>, "www-font@w3.org" <www-font@w3.org>, "public-webfonts-wg@w3.org" <public-webfonts-wg@w3.org>
On 26 May 2010, at 23:18, Sylvain Galineau wrote: >> From: Tal Leming [mailto:tal@typesupply.com] > >> It seems to me that trying to coordinate the associated credit, role >> and crediturl will be a problem. > > More on this. First, as to why these need to be 'coordinated'. > As in, you want to convey that these things belong together without > depending on the generator to write them one after the other, right ? > Then we could add a group attribute e.g. > > <property group="credits" name="credit" value="Font Designer" /> > <property group="credits" name="role" value="Lead" /> > <property group="credits" name="crediturl" value="http://fontdesigner.example.com" /> > <property group="credits" name="credit" value="Another Font Designer" /> > <property group="credits" name="role" value="Contributor" /> > <property group="credits" name="crediturl" value="http://anotherdesigner.example.org" /> > <property group="credits" name="credit" value="Yet Another" /> > <property group="credits" name="role" value="Hinting" /> > > Thus all these properties are explicitly put in the same bucket name, but without allowing > arbitrarily deep nesting. (I'd rather have some kind of a use-case to show arbitrarily deep > nesting is necessary for metadata). I think this misses the point, in that it does not indicate the associations between credit, role, and crediturl properties. JK
Received on Wednesday, 26 May 2010 22:24:21 UTC