[ckan-dev] differences in ISO19139 profiles

[Elena Camossi]

Hi everyone,

What are the differences in the spatial validation profiles supported by the
CKAN spatial extension: iso19139, iso19139eden, iso19139ngdc?
Does it make sense to specify in the configuration file more than one
profile, like 

ckan.spatial.validator.profiles = iso19139,iso19139eden,iso19139ngdc

and, in this case, what would be the expected behavior?

Another doubt is on harvested APIs metadata (services). Is there any
validation profile for that, such as ISO 19119? 

Thanks in advance.
Kind regards,
-Elena