the json is just in the DB not anywhere else, and the only "object store" that sqlite offers. Therefore the parser is already written, only the queries need adapting. This would allow to search (and potentially edit) any otherwise unknown XMP metadata by darktable. the person searching for needs to put the key and value to find what they are looking for - hence my use of "freestyle" because you need to know the precise key for searching. For editing the same applies, some type of freeform key/value editing UI e.g. excel table style maybe. But I guess the searching would already help tremendously, since the metadata is managed by third party app already.
Am Do., 16. Mai 2019 um 09:19 Uhr schrieb Remco Viëtor < [email protected]>: > On jeudi 16 mai 2019 08:14:54 CEST Michael Kefeder wrote: > > Why overengineer this, just dump IPTC info into JSON and use that for > > freestyle attributes. Sqlite even has an extension for fast parsing of > that > > https://sqlite.org/json1.html > > Because sidecars are what they are: XML serialisation of XMP format > metadata. > And that's not going to change any time soon either. > > So using json would require including yet another parser in any code > wanting > to use that data, and for the time being you can forget about > interoperability > (notably with the Adobe products). > > As stated elsewhere, the principal problem is not including those extra > metadata (enough ways to do that), but preserving, viewing and editing > them > *within darktable*. > > Remco > > P.S. I wouldn't call those IPTC data "freestyle", they have a rather > precise > definition, with defined codes for several of them. The same goes for many > of > the XMP elements. > > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to > [email protected] > > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
