Re: [office-comment] RFE: Colour space capability within OpenDocument

[Patrick Durusau <patrick@durusau.net>]

Alex,

Thanks for the comments!

The mailing list archives, proposals, TC minutes, etc., are all 
available on the TC website:

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office

We don't have a defined process for handling comments but comments are 
acknowledged and passed onto the TC for further action (where necessary).

Such as in your case. Since you are obviously familiar with the area, do 
you have any other references that you could share to relevant resources?

Thanks again!

Hope you are having a great day!

Patrick

Alex Hudson wrote:

>(Just as an aside: is it possible for someone to outline the process by
>which comments on this list are considered by the TC, so that I might
>follow future discussion on specific features?)
>
>The OpenDocument specification references colours in a number of ways
>and places, unexhaustively:
>
>      * 15.4.3 Color, which references XSL 7.17.1;
>      * the color datatype defined to be #\hex{6} within the RelaxNG;
>      * 13.1.4 Animate Color;
>
>Currently, colour management is a real problem - particularly for
>high-end or professional printing - since the format is only aware of
>colour specified as RGB, and doesn't specify a colour space.
>
>13.1.4 is notable for mentioning a HSL colour model, although obviously
>it's not that relevant to printing, but everywhere else assumes RGB.
>This causes a number of problems that I hope can be fixed in the future.
>
>In particular, the following features would be extremely useful:
>
>     1. ability to specify colours in terms of CMY, CMYK;
>     2. ability to specify an RGB colour space (e.g., sRGB) for
>        conversion purposes;
>     3. ability to load images etc. in formats such as CMYK, and retain
>        RGB conversions for future use (that is, for RGB display
>        purposes), since different applications will convert them
>        differently (or be unable to convert them);
>     4. support for ISO 15076 (ICC Color Profiles) - see, e.g., the work
>        in CSS3: http://www.w3.org/TR/css3-iccprof;
>     5. some degree of support for Pantone(?)
>
>While it's not terribly necessary that applications be able to do
>reasonable conversions, it is absolutely key that images / colours set
>in CMYK get passed through without being touched so that, for example,
>output to PDF works.
>
>I have little confidence that 5) above is possible per se, although it
>would be useful to be able to mark a certain colour reference as being a
>particular Pantone colour, even if the colour isn't close.
>
>3 & 4 I see as less important; where conversions occur, it would be good
>to have them "saved" for consistency (without getting rid of the non-RGB
>original!), but to a large extent that can be mostly left up to
>applications. OpenDocument might simply advise on best practice.
>
>Many thanks,
>
>Alex.
>
>
>This publicly archived list offers a means to provide input to the
>OASIS Open Document Format for Office Applications (OpenDocument) TC.
>
>In order to verify user consent to the Feedback License terms and
>to minimize spam in the list archive, subscription is required
>before posting.
>
>Subscribe: office-comment-subscribe@lists.oasis-open.org
>Unsubscribe: office-comment-unsubscribe@lists.oasis-open.org
>List help: office-comment-help@lists.oasis-open.org
>List archive: http://lists.oasis-open.org/archives/office-comment/
>Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
>List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
>
>
>
>
>  
>

-- 
Patrick Durusau
Patrick@Durusau.net
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model
Member, Text Encoding Initiative Board of Directors, 2003-2005

Topic Maps: Human, not artificial, intelligence at work!