- From: Paul Deschamps <pdescham49@gmail.com>
- Date: Sun, 14 Feb 2016 12:10:28 -0500
- To: Simon Bächler <b@chler.com>
- Cc: public-universalimages@w3.org
- Message-ID: <CACPLTHjPnkEv7S6ywccXwQCeLsX31FaYQ55sLRi-OHuayMkevQ@mail.gmail.com>
Hi Simon, This is all great stuff however are you suggesting that the planet use a server or rather a collection of servers to process imagery for responsive design? There are a few considerations in this approach that I think need to be called out. - Bandwidth costs - Infrastructure costs - setting up a world wide CDN - SLA on response times - Legal ramifications - if something 'happens' that is undesirable. IMHO what is needed here is an adoption of a responsive file format that some of the rules you've called out on for handling the cropping scaling of the raster; not a webservice. Though this may be a good model for a "commercial" product to handle a unique way to resolve some of the issues of responsive design. I don't feel it belongs in the W3C. There is no way to offer this as a "free" service since the infrastructure costs would be quite something. Just my two cents. Paul On Sun, Feb 14, 2016 at 11:19 AM, Simon Bächler <b@chler.com> wrote: > Dear members > > I spent the last few weeks creating prototype implementations of software > that uses the XMP rmd draft standard > <https://github.com/universalimages/rmd>. > > The results can be seen on this demo page: > <http://sbaechler.github.io/universalimages-demo/> > http://sbaechler.github.io/universalimages-demo/ > > You can try out the image server yourself here: > > http://thumbor.stellanera.com/unsafe/320x/filters:rmd()/http://stellanera.com/universalimages/monks.jpg. > Just increase the image width to 360 or 480 and see the crop region adjust > for the new width. You can also use your own images as a source. > The server is running on a EC2 micro instance and is not protected. Please > don’t abuse it. > > I had to make some small adjustments to the schema while developing the > prototypes. But now I think it holds up pretty well. > The big advantage of using a XMP schema is that it is completely > independent of the image format. > > The first tool is a Metadata UI Extension for Adobe products. It allows > editing the responsive metadata by hand using the „File information“ > dialog. It is available on Github under the universalimages organization: > <https://github.com/universalimages/rmd-extension> > https://github.com/universalimages/rmd-extension. > > The next tool is a Adobe Photoshop plugin for Photoshop CC that provides a > graphical user interface for setting responsive metadata information. The > package can be downloaded here: > https://github.com/sbaechler/ps-rmd-plugin/releases. > > In the newest version of Photoshop, Adobe stopped support for the > Extension manager and requires that all plugins be installed via the Adobe > Exchange cloud platform. I submitted the package and it is currently in > review. I can give anyone who is interested a preview access. Just send me > your email address (that has a creative cloud account) and I can add you to > the testers group. > > For cropping the images, I created a plugin for the Python based > open-source image server Thumbor <http://thumbor.org/>. The plugin > currently only runs on a fork of Thumbor because it needs access to the XMP > metadata. > The repository is available here: > https://github.com/sbaechler/thumbor-universalimages. I added a UML > activity diagram > <https://github.com/sbaechler/thumbor-universalimages/blob/master/docs/uml/Activity-diagram-rmd.pdf> > to the repo that explains the cropping process. It got quite complex with > all the rules and combinations of them. > > > Best Regards > > Simon > >
Received on Sunday, 14 February 2016 17:10:56 UTC