Re: SLING-11865 - Conversion fails when initial content document does not include namespace declaration

2023-05-12 Thread Julian Reschke
On 12.05.2023 15:48, Robert Munteanu wrote: On Mon, 2023-05-08 at 18:27 +0200, Konrad Windszus wrote: Another option would probably be to pass parameters to cp2fm for declaring additional namespaces. Then downstream consumers could declare additional ones like “cq” and those would have known

Re: SLING-11865 - Conversion fails when initial content document does not include namespace declaration

2023-05-12 Thread Robert Munteanu
On Mon, 2023-05-08 at 18:27 +0200, Konrad Windszus wrote: > Another option would probably be to pass parameters to cp2fm for > declaring additional namespaces. > Then downstream consumers could declare additional ones like “cq” and > those would have known URLs then which would be taken into

RE: SLING-11865 - Conversion fails when initial content document does not include namespace declaration

2023-05-09 Thread Stefan Seifert
1 is definitely the better approach. as konrad mentioned as well, 1 could be combined with improved defaults in the downstream-tooling (e.g. aem analyser plugin). it should be possible to register the well-known namespaces used in AEM context there as default, that should cover most of the

Re: SLING-11865 - Conversion fails when initial content document does not include namespace declaration

2023-05-08 Thread Konrad Windszus
Hi, From a Sling perspective having initial content without explicit namespace declaration is totally fine. Therefore I wouldn’t call it ill-formed Sling initial content files. But the converted DocView file is ill-formed (violating the spec) but still imported fine. Having said this,