What's the difference between "native" and "color"?

[jpstroop]

... I see: "Color: The image is returned in full color, typically using 24 bits per pixel." Are we encouraged to downsample to 24 bits?
Should we oversample if the source is lower?
When would a user ever opt for 'color' over 'native'? _Answer:#level0
_Also: REMOVE 24 bits from the text

[jpstroop]

New idea, inspired by http://www.semanticdesktop.org/ontologies/2007/03/22/nfo/#colorDepth

what if instead of 'color','grey', etc. we used 1,8,24, and added the value 'unknown', which is what I think we really mean by 'native'.

[azaroth42]

Ouch, backwards incompatible change to the image URLs :(
Agree that native is "unknown", from the client's perspective. Or "the best
you've got".

So ... what's the benefit that outweighs the cost of changing every
implementation?

On Tue, Apr 15, 2014 at 4:18 AM, Jon Stroop notifications@github.comwrote:

New idea, inspired by
http://www.semanticdesktop.org/ontologies/2007/03/22/nfo/#colorDepth

what if instead of 'color','grey', etc. we used 1,8,24, and added the
value 'unknown', which is what I think we really mean by 'native'.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-40470445
.

Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305

[zimeon]

I really don't like "unknown", this seems a very odd thing to write from a client p.o.v.. Perhaps "default"?

[azaroth42]

Agree with default being better, but not worth backwards incompatibility to change at this stage (and hence ever).

[zimeon]

Jon/Rob/Simeon - agreement that native is the wrong word but that the pain for implementers to change it at this point doesn't justify. Will fix with documentation