You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the rise of web forms as a primary mechanism for contacting organisations, can we move away from insisting on an email address? We would have to replace this with a more complex/subtle requirement that either an email address or the URL of a web contact form has to be given.
Organisations are tending away from encouraging email contact towards the use of web forms, so that enquiries are entered straight into an incident management system. By insisting on providing email addresses, INSPIRE is behind the curve on this.
Change proposal description
Given the rise of web forms as a primary mechanism for contacting organisations, can we move away from insisting on an email address? We would have to replace this with a more complex/subtle requirement that either an email address or the URL of a web contact form has to be given.
Addressed TG
Metadata
Location
TG Requirement C.6: metadata/2.0/req/common/md-point-of-contact and TG Requirement C.10: metadata/2.0/req/common/responsible-organisation
Issue faced
Organisations are tending away from encouraging email contact towards the use of web forms, so that enquiries are entered straight into an incident management system. By insisting on providing email addresses, INSPIRE is behind the curve on this.
Proposed solution
Pull request
Additional information
Relevant legislation
Unfortunately, this is also a requirement in the Regulation: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32008R1205&rid=1 clause 9.1 and 10.1
Impact on IR
Unfortunately, this is also a requirement in the Regulation: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32008R1205&rid=1 clause 9.1 and 10.1
Impact on INSPIRE validator
Would also need amendment
Linked issue
Impact on INSPIRE XML schemas
None
Linked issue
Impact on INSPIRE code lists
None
Linked issue
Change proposer
Peter Parslow, Ordnance Survey Great Britain
References
The text was updated successfully, but these errors were encountered: