aeo-image - npm Package Compare versions

Comparing version 1.1.0 to 1.1.1

package.json

 {
   "name": "aeo-image",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Write descriptive + rights metadata (captions, keywords, alt text, creator, license) into WebP, AVIF, HEIC, JPEG & PNG — self-describing images that Google Images reads and recommends embedding, built for the AI-search era. The only pure-JS, zero-dependency library that writes XMP to AVIF/HEIC. Byte-preserving; runs on Node, Bun, Deno & edge.",
@@ -5,0 +5,0 @@ "type": "module",

README.md

@@ -77,2 +77,18 @@ # aeo-image
 
+## Standards & conformance
+
+`aeo-image` writes metadata as an **Adobe XMP** packet (the modern serialization) — **not** the legacy IPTC-IIM binary block. This is what Google and current tooling read.
+
+Fields conform to the **[IPTC Photo Metadata Standard 2025.1](https://iptc.org/standards/photo-metadata/iptc-standard/)** (the current revision), specifically the descriptive, accessibility, and rights/licensing subset, across these namespaces:
+
+| Namespace | Prefix | Used for |
+| --- | --- | --- |
+| Dublin Core | `dc:` | description, title, subject/keywords, creator, rights |
+| IPTC Core | `Iptc4xmpCore:` | `AltTextAccessibility` (IPTC **2021.1**+) |
+| Adobe Photoshop | `photoshop:` | credit, copyright |
+| XMP Rights | `xmpRights:` | web statement (license URL) |
+| PLUS | `plus:` (ns 1.0) | licensor (license-acquisition link) |
+
+**Not yet implemented:** IPTC 2025.1's AI-generation provenance properties (AI Prompt Information, AI System Used, …) — tracked in the roadmap.
+
 ## Install
@@ -79,0 +95,0 @@

No alert changes

Improved metrics

Total package byte prevSize

115892

0.86%

Number of lines in readme file

221

7.8%

No dependency changes