Hi, Phil.
On page
https://exiftool.org/TagNames/EXIF.html (https://exiftool.org/TagNames/EXIF.html)
I found link
https://web.archive.org/web/20190624045241if_/http://www.cipa.jp:80/std/documents/e/DC-008-Translation-2019-E.pdf (https://web.archive.org/web/20190624045241if_/http://www.cipa.jp:80/std/documents/e/DC-008-Translation-2019-E.pdf)
But exist CIPA DC-010-2020 Exif2.32 metadata for XMP on page
https://www.cipa.jp/e/std/std-sec.html (https://www.cipa.jp/e/std/std-sec.html)
Is this a newer document or is there some specifics that I don't know about?
That's for XMP tags, so you can find a link under XMP exif tags (https://exiftool.org/TagNames/XMP.html#exif).
It does point to the Archive.org cached copy of 2.31, as I don't believe there's a direct link available for 2.32. The differences are minimal, I believe.
Why are links given here to archive.org but not to the original standards sites?
Follow the link. It goes directly to the PDF. The cipa.ja site doesn't allow direct access.
A-ha... I see different two documents:
1. CIPA DC-010-2020 Exif2.32 metadata for XMP — https://www.cipa.jp/std/documents/download_e.html?DC-010-2020_E (https://www.cipa.jp/std/documents/download_e.html?DC-010-2020_E)
2. CIPA DC-008-Translation-2019 Exchangeable image file format for digital still cameras : Exif Version 2.32 — https://www.cipa.jp/std/documents/download_e.html?DC-008-Translation-2019-E
On EXIF Tags page link is given only to a copy of the second document, why?
Also, you can give links to the download pages of the specification on CIPA site, the difference will be only in two mouse clicks, but these will be originals that you can not download, but open in a browser. Is there a reason not to do this?
I just want to understand the details.
The first document is for XMP format so it isn't relevant for the ExifTool EXIF documentation.
Some of the ExifTool documentation links may be outdated because CIPA keeps moving things around. I'll consider updating them if you think you have better ones.
- Phil
I'm not completely sure of anything yet, I'm just studying the details, that's why I'm asking.
And how do specifications (for example, CIPA) get to archive.org?
Archive.org has web crawlers just like Google and Bing. Plus, they have a community similar to Wikipedians who use browser extensions to submit pages they read for archiving.
The Internet Archive is a non-profit library and they archive and digitize thousands of documents and other things (picture of their record digitizing setup (http://blog.archive.org/wp-content/uploads/2019/10/20190917_181336-1024x485.jpg)). They've built they're own cable backbone to connect their buildings in San Francisco. Obviously, something I'm a bit passionate about, just behind exiftool.
How quickly do copies of standards get archived for Phil to link to in his documentation?
Or does Phil himself monitor the release of a new standard and archive it himself and then link to it?
Depends upon when someone notices changes. There are multiple thread where someone notices a link has changed, usually in this part of the forums. Sometimes Phil is told ahead of time. For example, here (https://exiftool.org/forum/index.php?topic=10568.msg55976#msg55976) he mentions where he was told about a change before it was even published.
Phil himself looks at everything in the new specifications, he checks the changes himself? Isn't it very inconvenient and difficult? Or there are some APIs that are provided by the creators of the standards.
I rely on people telling me that there is a new standard. (And for standards which use ExifTool internally, I find out about this before the standard is released to the public.) Once I know about it, I implement the changes. Some standards provide a list of changes in the new version, which is very helpful. Otherwise I have to read the whole document to see what changed. ExifTool does not use external API's for any type of metadata.
- Phil
It seems there should be an API standard for metadata standards: reading tons text with copying/pasting into your software is strange.
This is an obvious thing that has not been done - it means that someone needs these inconveniences or is there something I don't know...
What will happen to Exiftool if Phil stops supporting him?
Who wants to study tons of standards text? ...and Perl.
Tell me, please, Phil, what do you think about all this?
Probably this topic should be moved to Metadata or Other Discussions?
Quote from: Jom on February 01, 2022, 08:27:59 AM
What will happen to Exiftool if Phil stops supporting him?
Send flowers. (RIP)
QuoteWho wants to study tons of standards text? ...and Perl.
Nobody in their right mind. ;)
- Phil
Phil, how do you have the energy to do this?
It's time consuming in a standards mess world.
Or is someone paying you for this work?
Yes it is time consuming. I'm not in this to make money, although some generous people do send donations. This is what I do for fun in my spare time.
- Phil
If I understand correctly, ExifTool is now the best solution for managing metadata and is used not only by individuals, but also by companies (am I right?).
Why then ExifTool is supported by one person and is not supported by any foundation or organization?
Did you receive offers?
Quote from: Jom on February 01, 2022, 11:25:47 PMbut also by companies (am I right?).
Flickr uses exiftool on the back end. See this page (https://code.flickr.net/2012/06/01/parsing-exif-client-side-using-javascript-2/). You can also see it on any photo page. There's a link that says "Show EXIF" and the listing is very obviously output from exiftool.
Imatch (https://www.photools.com/), an extremely good DAM, uses exiftool as well.
Why are links given here to archive.org but not to the original standards sites?
I've the same question.
It's a direct link to the file without having to deal with the disclaimer that CIPA uses to gatekeep the document. Plus it allows viewing directly in the browser without having to save it to disk first.