Hi Alastair, Yes - as you get into using the metadataTag different uses come to mind. The original intent was to record information about the profile that would be valuable in selecting among several similar profiles. For example - several different devicelink profiles all with the final profile for the same output device -- what makes them different, when to pick which one. On the other hand as you point out, a profile builder might also use a metadataTag to record 'I did it this way' kinds of information - as a record keeping mechanism. In general, the repository can contain metadata defined for either purpose -- as long as it is defined in a way that provides some usefulness to others. At minimum - a metadata item can be entered in the repository to ensure that the name remains case-insensitive unique. Best regards, Ann McCarthy Imaging Systems R&D Lexmark Imaging Solutions Division Lexmark International, Inc. <table width=100%> <tr valign=top> <td width=40%>"Alastair M. Robinson" <blackfive@fakenhamweb.co.uk> 04/05/2010 01:49 PM <td width=59%> <table width=100%> <tr valign=top> <td> <div align=right>To</div> <td>Ann L McCarthy <almccart@lexmark.com> <tr valign=top> <td> <div align=right>cc</div> <td>openicc@lists.freedesktop.org <tr valign=top> <td> <div align=right>Subject</div> <td>Re: [Openicc] Devicelink profiles and accompanying metadata</table> <table> <tr valign=top> <td> <td></table> </table> <tt>Hi :) Ann L McCarthy wrote: > The ICC has now fully approved an ICC profile metadataTag and > dictionaryType which might be > useful in this case.   Then each devicelink can contain its own record > of what it is made from etc. > Here is link to the spec for the new tag and type on the ICC website. Many thanks for that - I've just had a quick look and shall read it in more detail later. > Metadata to record the make contents of devicelink profiles can > certainly be useful to define and share. Definitely - though I see a distinction in scope between metadata fields which have broad applicability (for example, source and destination profiles for a devicelink) and fields which are of little use to anything but the defining application (i.e. black generation parameters - just knowing what they are tells you nothing unless you also know how the application will interpret them...)  For the latter type, where you just want to associate some data with the profile but don't expect other software to be able to make use of it, would you just register a key with for example "CMYKToolSpecific", "Meaning of Value=Custom" and, say, "Values=up to 30 characters" or something like that? All the best -- Alastair M. Robinson </tt>