KhronosGroup / KhronosGroup/KTX-Specification
Support XMP metadata
- Dominant language
- CSS
- Stars
- 81
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The current key-value storage is suitable for KTX-specific metadata entries but using it for storing generic information such as copyright and authorship is not practical. Common image formats (such as PNG and JPEG) support embedded XMP blocks that can provide interoperable metadata for integration with other systems.
An XMP block is either an XML or a JSON-LD document as defined in ISO 16684-1 or ISO 16684-3 respectively. Since it's text-based and may be quite verbose, zlib or zstd compression may be reasonable.
Contributor guide
Research direction
The issue does not identify a file, test, or entry point. First review the KTX specification's metadata and key-value sections alongside the referenced ISO XMP definitions; define the representation and compression requirements before implementation. Done means the specification clearly describes interoperable XMP storage and includes any needed validation examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, xml
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100