Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TG Metadata - recognise the move from email to web form as a key contact method #86

Closed
PeterParslow opened this issue Jan 19, 2023 · 3 comments
Labels
duplicate The change proposal is similar to another change proposal

Comments

@PeterParslow
Copy link

PeterParslow commented Jan 19, 2023

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

@fabiovinci
Copy link
Collaborator

Dear @PeterParslow,

thank you for the change proposal, I leave it open, at the moment, even though the same proposal is already present.

Duplicate: #72

@fabiovinci fabiovinci added impact on IR The change proposal has an impact on the IR. impact on validator The change proposal has an impact on the INSPIRE validator. duplicate The change proposal is similar to another change proposal for Sub-group The change proposal is to be assessed by the Sub-group labels Jan 19, 2023
@PeterParslow
Copy link
Author

PeterParslow commented Jan 19, 2023

Sorry - I didn't spot #72 - this is an attempt to close this one.

@fabiovinci
Copy link
Collaborator

Dear @PeterParslow,

the sub-group approved this change proposal and will therefore be voted on at the next MIG-T meeting.

I will close this issue, considering it duplicates issue #72, and the progress on this change proposal will be posted on the original issue.

@fabiovinci fabiovinci removed for Sub-group The change proposal is to be assessed by the Sub-group impact on IR The change proposal has an impact on the IR. impact on validator The change proposal has an impact on the INSPIRE validator. labels Apr 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate The change proposal is similar to another change proposal
Projects
None yet
Development

No branches or pull requests

2 participants