Strings in Process.responsibleParty.RelatedParty
The INSPIRE Community Forum is now part of the INSPIRE helpdesk system, based on GitHub (https://github.com/INSPIRE-MIF), so please start there any new discussions.
The current platform will remain available in read only mode in its current form and URL address until 31/01/2021, then its content will be archived and then published in a different URL which will be announced when it becomes available.
Tags:
According to the implementing rules (https://eur-lex.europa.eu/legal-content/DE/TXT/PDF/?uri=CELEX:02010R1089-20141231&qid=1585807762468&from=DE), RelatedParty.individualName, RelatedParty.organisationName and RelatedParty.positionName have PT_FreeText as type.
PT_FreeText is also used for some metadata fields. There are discussions going on concerning the correct use of PT_FreeText (https://github.com/inspire-eu-validation/metadata/issues/121 and https://github.com/inspire-eu-validation/community/issues/145) which state that it only makes sense to use PT_FreeText when providing an additional value to the 'original' string value in the data.
As I think that the rationale there makes perfect sense, I would like to know if it is absolutely necessary to provide the three attributes of RelatedParty as PT_FreeText or if they can also be provided as ChracterString? Note: The Validator accepts both.
Thank you for your input and all the best
Johanna
Hi Johanna,
I admit I hadn't even thought of using PT_FreeText here. Is there any additional information you wish to provide together with the text string? Organization name in different languages?
If no, CharacterString is so much easier to provide and consume!
:)
Kathi
Hi Kathi,
Me neither until I saw how the attributes are defined in the implementing rules. As I do not have any additional information, I would be very happy to use CharacterString.
I am just hesistant as that does not seem to be compliant to the implementing rules.
All the best
Johanna
I've looked through the various models, from what I can see, some Themes used PT_FreeText in cases where multiple language representations would make sense, others just ignored it. Where PT_FreeText is specified, it would hurt interoperability if some data providers use PT_FreeText, others CharacterString.
I've been hearing rumors that some of the more painful additions required by INSPIRE such as multilinguality may soon be watered down, to my view this would make sense as these options are rarely utilized by MS.
It would be interesting to get some general guidance on the use of PT_FreeText vs. CharacterString, but that's difficult to get. It might be easiest to put in an issue in the validator github that it SHOULD check this, see what happens then!
:)
Hi Kathi,
You're right. Strictly speaking, this is an unexpected behavior of the validator in case the PT_FreeText type is demanded by the IR. I therefore createad https://github.com/inspire-eu-validation/community/issues/349.
All the best
Johanna