home.social

#iptc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #iptc, aggregated by home.social.

  1. europesays.com/dk/48124/ Tietoevry: Tieto: Compositions of the committees of the company’s Board of Directors #iptc:04003000 #mar #moic:IT #moic:IT30 #moic:IT3010 #Norway #Oslo #regulatory

  2. europesays.com/dk/43937/ ZENITH ENERGY LTD: Payment of 2026 multi-currency bond coupons #iptc:04005000 #moic:EN #moic:EN20 #moic:EN2030 #Norway #Oslo

  3. Full day with content credentials discussions, exploring ways to help media orgs to adopt and utilise the benefits and forging action plans for the nexts and following steps.

    Also super useful to meet people in person - much much easier to continue offsite and asynchronous talk with various orgs and people.

    Great day, and really good location and venue, too!

    #C2PA #ContentCredentials #ChainOfTrust #EBU #IPTC

  4. Full day with content credentials discussions, exploring ways to help media orgs to adopt and utilise the benefits and forging action plans for the nexts and following steps.

    Also super useful to meet people in person - much much easier to continue offsite and asynchronous talk with various orgs and people.

    Great day, and really good location and venue, too!

    #C2PA #ContentCredentials #ChainOfTrust #EBU #IPTC

  5. Full day with content credentials discussions, exploring ways to help media orgs to adopt and utilise the benefits and forging action plans for the nexts and following steps.

    Also super useful to meet people in person - much much easier to continue offsite and asynchronous talk with various orgs and people.

    Great day, and really good location and venue, too!

    #C2PA #ContentCredentials #ChainOfTrust #EBU #IPTC

  6. Full day with content credentials discussions, exploring ways to help media orgs to adopt and utilise the benefits and forging action plans for the nexts and following steps.

    Also super useful to meet people in person - much much easier to continue offsite and asynchronous talk with various orgs and people.

    Great day, and really good location and venue, too!

  7. Full day with content credentials discussions, exploring ways to help media orgs to adopt and utilise the benefits and forging action plans for the nexts and following steps.

    Also super useful to meet people in person - much much easier to continue offsite and asynchronous talk with various orgs and people.

    Great day, and really good location and venue, too!

    #C2PA #ContentCredentials #ChainOfTrust #EBU #IPTC

  8. so **each** key/value-pair of #metadata can be about 64kB.

    This is sufficient to hold most annotations stored as #EmbeddedMetadata currently present in most file formats.
    (eg #mp3, #mp4, #iptc, #tiff, #jpg, etc)

    But from then on, the file-format becomes irrelevant for this task!

    #ahalodeck #digipres #audiovisual #cataloging

  9. so **each** key/value-pair of #metadata can be about 64kB.

    This is sufficient to hold most annotations stored as #EmbeddedMetadata currently present in most file formats.
    (eg #mp3, #mp4, #iptc, #tiff, #jpg, etc)

    But from then on, the file-format becomes irrelevant for this task!

    #ahalodeck #digipres #audiovisual #cataloging

  10. #TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷‍♂️

    When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: exiftool.org/TagNames/

    #photography

    ⚓️ nicolas-hoizey.com/notes/2025/

  11. #TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷‍♂️

    When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: exiftool.org/TagNames/

    #photography

    ⚓️ nicolas-hoizey.com/notes/2025/

  12. #TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷‍♂️

    When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: exiftool.org/TagNames/

    #photography

    ⚓️ nicolas-hoizey.com/notes/2025/

  13. #TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷‍♂️

    When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: exiftool.org/TagNames/

    #photography

    ⚓️ nicolas-hoizey.com/notes/2025/

  14. #TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷‍♂️

    When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: exiftool.org/TagNames/

    #photography

    ⚓️ nicolas-hoizey.com/notes/2025/

  15. Naty @eclecticpassions ·

    Been busy deep diving into and ... But I've entered a deeper rabbit hole —my really messy photo ! Learnt a lot about and , and using (which is an amazing tool by Phil Harvey).

  16. Been busy deep diving into #digikam and #darktable... But I've entered a deeper rabbit hole —my really messy photo #metadata! Learnt a lot about #xmp #exif and #iptc, and using #exiftool (which is an amazing tool by Phil Harvey). #PhotoManagement #dam #photometadata

  17. Been busy deep diving into #digikam and #darktable... But I've entered a deeper rabbit hole —my really messy photo #metadata! Learnt a lot about #xmp #exif and #iptc, and using #exiftool (which is an amazing tool by Phil Harvey). #PhotoManagement #dam #photometadata

  18. Been busy deep diving into #digikam and #darktable... But I've entered a deeper rabbit hole —my really messy photo #metadata! Learnt a lot about #xmp #exif and #iptc, and using #exiftool (which is an amazing tool by Phil Harvey). #PhotoManagement #dam #photometadata

  19. Been busy deep diving into #digikam and #darktable... But I've entered a deeper rabbit hole —my really messy photo #metadata! Learnt a lot about #xmp #exif and #iptc, and using #exiftool (which is an amazing tool by Phil Harvey). #PhotoManagement #dam #photometadata

  20. Nouvelle version de Apnee dispo !
    Apnee c'est une app Mac pour modifier les #exifs et #iptc de vos photos.
    Vous pouvez également enregistrer des templates de metadatas et les appliquer...

    C'est gratuit et open-source.

    Donc, vous avez besoin de modifier vos exifs et juste ça, rien d'autre ? C'est disponible ici :
    codeberg.org/atlza/apnee

    Ah et, chose importante, le nom est un acroyme récusrisf :)
    Apnee Php Native Exif Editor

  21. Nouvelle version de Apnee dispo !
    Apnee c'est une app Mac pour modifier les #exifs et #iptc de vos photos.
    Vous pouvez également enregistrer des templates de metadatas et les appliquer...

    C'est gratuit et open-source.

    Donc, vous avez besoin de modifier vos exifs et juste ça, rien d'autre ? C'est disponible ici :
    codeberg.org/atlza/apnee

    Ah et, chose importante, le nom est un acroyme récusrisf :)
    Apnee Php Native Exif Editor

  22. About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.

    Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.

    Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.

  23. About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.

    Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.

    Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.

  24. About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.

    Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.

    Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.

  25. About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.

    Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.

    Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.

  26. About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.

    Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.

    Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.

  27. @Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition

  28. @Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition

  29. @Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition

  30. @Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition

  31. @Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition

  32. DINAX hat ein kostenloses Tool veröffentlicht, um auf einfach Weise, Copyright relevante IPTC Daten zu schreiben.

    #iptc #metadaten #copyright

    dinax.com/iptc/

  33. DINAX hat ein kostenloses Tool veröffentlicht, um auf einfach Weise, Copyright relevante IPTC Daten zu schreiben.

    #iptc #metadaten #copyright

    dinax.com/iptc/