W3C home > Mailing lists > Public > www-font@w3.org > April to June 2010

Re: WOFF and extended metadata

From: Tal Leming <tal@typesupply.com>
Date: Wed, 26 May 2010 15:57:43 -0400
Cc: Jonathan Kew <jfkthame@googlemail.com>, Vladimir Levantovsky <Vladimir.Levantovsky@MonotypeImaging.com>, "robert@ocallahan.org O'Callahan" <robert@ocallahan.org>, Adam Langley <agl@google.com>, John Daggett <jdaggett@mozilla.com>, Christopher Slye <cslye@adobe.com>, "www-font@w3.org" <www-font@w3.org>, "public-webfonts-wg@w3.org" <public-webfonts-wg@w3.org>
Message-Id: <FF110C45-5577-4436-89DF-65B424B85150@typesupply.com>
To: Sylvain Galineau <sylvaing@microsoft.com>

On May 25, 2010, at 2:47 PM, Sylvain Galineau wrote:

> Unless implementations of the metadata block format already exist, or large
> numbers of fonts have been distributed that use the format currently specified,
> there would seem to be limited interop risk to reopening this. This
> is probably our last chance.

Fonts are out there with metadata in place.

> <property name="FontName" value="Comic Sans++" />
> <property name="FontVendor" value="Funny Fonts, SARL" />
> <property name="LicenseURL" lang="en" value="http://funnyfonts.com..." />
> <property name="LicenseURL" lang="fr" value="http://funnyfonts.com..." />
> ...(lots more stuff)...

I did some thinking about this. As a test, I converted the example we have in the WOFF spec to follow your format:

	<?xml version="1.0" encoding="UTF-8"?>
	<metadata version="2.0">
		 <property name="uniqueid" value="com.example.fontvendor.demofont.rev1234" />
		 <property name="vendorname" value="Font Vendor" />
		 <property name="vendorurl" value="http://fontvendor.example.com" />
		 <property name="description" lang="en">
				A member of the Demo font family.
				This font is a humanist sans serif style designed
				for optimal legibility in low-resolution environments.
				It can be obtained from fontvendor.example.com.
		 </property>
		 <property name="license" lang="en">A license goes here.</property>
		 <property name="license" lang="fr">Un permis va ici.</property>
		 <property name="licenseurl" value="http://fontvendor.example.com/license" />
		 <property name="copyright" lang="en">Copyright ©2009 Font Vendor</property>
		 <property name="copyright" lang="kr">저작권 ©2009 Font Vendor</property>
		 <property name="trademark" lang="en">Demo Font is a trademark of Font Vendor</property>
		 <property name="trademark" lang="fr">Demo Font est une marque déposée de Font Vendor</property>
		 <property name="trademark" lang="de">Demo Font ist ein eingetragenes Warenzeichen der Font Vendor</property>
		 <property name="trademark" lang="ja">Demo FontはFont Vendorの商標である</property>
		 <property name="licensee" value="Wonderful Websites, Inc." />
	</metadata>

This is everything except the credits element and its credit child-elements. The key/value model breaks down there. As best as I can figure, this is what it would look like:

	<property name="credit" value="Font Designer" />
	<property name="role" value="Lead" />
	<property name="crediturl" value="http://fontdesigner.example.com" />
	<property name="credit" value="Another Font Designer" />
	<property name="role" value="Contributor" />
	<property name="crediturl" value="http://anotherdesigner.example.org" />
	<property name="credit" value="Yet Another" />
	<property name="role" value="Hinting" />

It seems to me that trying to coordinate the associated credit, role and crediturl will be a problem.

Tal
Received on Wednesday, 26 May 2010 19:58:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:34 UTC