https://bugs.documentfoundation.org/show_bug.cgi?id=119563
V Stuart Foote <vstuart.foote@utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rb.henschel@t-online.de,
| |vstuart.foote@utsa.edu
--- Comment #4 from V Stuart Foote <vstuart.foote@utsa.edu> ---
What has OASIS and the ODF TC worked out from past sessions?
Delving too far into Exif or XMP for the benefit of raster images, with no
appreciable support for other graphics seems kind of short sighted.
I'd much rather see a fully fleshed out treatment of Dublin Core [1] as the
basis for metadata attribute assignment in XML of all objects held in ODF, not
just raster images.
Might be doable with XMP. But, I don't think we want the overhead of
manipulating Exif/TIFF binary headers for images that we convert and manipulate
internally in SVM/BMP anyhow.
IHMO keeping track of metadata during the image/graphic object lifecycle would
be better handled as with the rest of an object's properties and all objects
with common methods.
That has benefit of allowing us to "anonymize" the objects attributes when that
is preferred/required for privacy.
=-ref-=
[1] https://en.wikipedia.org/wiki/Dublin_Core
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 119563] When importing media (eg images) to libreoffice it would be friendly to save some metadata · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.