Much like the Cooke /i spec fore lens metadata, there's a core set of capabilities and then one can add one's own non-core extensions. But /i is very hardware-tied; this is not.
On the plus side, some work may already have been done for us. Are there CxF communities out there that might have published extension schemae for what CxF calls 'Custom Resources'? Take the Esser TE266 chart that Image Engineering sells, for example. And not only might this save us work, but we could read in and parse apart a file containing such resources, then write out what we thought was a file containing the same information and compare them to see if we round-tripped.
On the minus side, what if we pick up and redistribute something that seems like a common enough thing that it deserves to be a custom resource, and the creator of the thing we are describing with that resource feels that somehow a CxF3 custom resource for it is a copyright violation, something not covered under 'fair use'. Should custom resources be in their own repo, much as for Colour there's a Colour-data repo? That way, worst case, the CxF custom resource repo gets taken out, but the open-source CxF parser we develop is preserved.
Is there a CxF user community out there with a catalog of extension schemae for 'Custom Resources' that has already figured this out? Is there a conference (maybe a print-centric conference) regularly attended by people who might have dealt with this issue already?
Much like the Cooke /i spec fore lens metadata, there's a core set of capabilities and then one can add one's own non-core extensions. But /i is very hardware-tied; this is not.
On the plus side, some work may already have been done for us. Are there CxF communities out there that might have published extension schemae for what CxF calls 'Custom Resources'? Take the Esser TE266 chart that Image Engineering sells, for example. And not only might this save us work, but we could read in and parse apart a file containing such resources, then write out what we thought was a file containing the same information and compare them to see if we round-tripped.
On the minus side, what if we pick up and redistribute something that seems like a common enough thing that it deserves to be a custom resource, and the creator of the thing we are describing with that resource feels that somehow a CxF3 custom resource for it is a copyright violation, something not covered under 'fair use'. Should custom resources be in their own repo, much as for Colour there's a Colour-data repo? That way, worst case, the CxF custom resource repo gets taken out, but the open-source CxF parser we develop is preserved.
Is there a CxF user community out there with a catalog of extension schemae for 'Custom Resources' that has already figured this out? Is there a conference (maybe a print-centric conference) regularly attended by people who might have dealt with this issue already?