On 10/26/05, Jann Forrer <[EMAIL PROTECTED]> wrote: > On Wed, 26 Oct 2005, Michael Wechner wrote: > > Jann Forrer wrote: > >> <dc:format>image/gif 505 x 48 pixels</dc:format> > > I think something like > > <img:height>...</img:height> > > <img:width>...</img:width> > > <mime-type>...</mime-type> > > would be more handy, because it requires less parsing ;-) > That is certainly true but that would mean to have a mix of dublincore and > non dublincore metadata as: > <dc:metadata xmlns:dc="http://purl.org/dc/elements/1.1/";> > <dc:format>image/jpeg</dc:format> > <img:height>...</img:height > <img:width>...</img:width> > </dc:metadata> > But as you said that requires less parsing :-)
dc:format is currently defined as something usable as a Content-Type header. The examples make the "100x40 pixels" acceptable, but not when dealing with HTTP data. Content-Type defines parameters in this format: "image/gif; width=100; height=40" After meeting external specs, please make it as useful as possible. The above formats are not XSL-friendly. It is better for Lenya to provide XSL-friendly information than make every developer add parsing code in every XSL that needs the height and width. Always make everything as easy as possible, and this time it is very evident that additional tags would make development much easier. Recording the width and height twice will not significantly change storage or processing requirements. That said, I do not care which of these additional tags are used: <img:width>100</img:width><img:height>40</img:height> <lenya:width>100</lenya:width><lenya:height>40</lenya:height> <lenya:img-width>100</lenya:img-width><lenya:img-height>40</lenya:img-height> >From a maintenance perspective, the second reduces the number of namespaces and tags required, because the "lenya" namespace is already used, and the "width" and "height" tags might be overloaded for other purposes. XSL can decide which tags are images with: starts-with(dc:format, 'image') solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
