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

Disable resolve of xlink:href for codelist values #747

Closed
DirkThalheim opened this issue Aug 23, 2016 · 2 comments · Fixed by #787
Closed

Disable resolve of xlink:href for codelist values #747

DirkThalheim opened this issue Aug 23, 2016 · 2 comments · Fixed by #787
Assignees
Labels
enhancement enhancement or improvement medium ready
Milestone

Comments

@DirkThalheim
Copy link

INSPIRE uses xlink:href attributes to specify codelist values as URLs. For example:

  • <gn:nativeness xlink:href="http://inspire.ec.europa.eu/codelist/NativenessValue/endonym"/>
  • <gn:nameStatus xlink:href="http://inspire.ec.europa.eu/codelist/NameStatusValue/official"/>

deegree however interprets every xlink:href as complex feature and tries to resolve those references. When importing data as GML this extremely slows down the process as for every URL a request is performed to resolve the reference (which of course fails).

It should be possible to disable the default behaviour of reference resolving for a configurable set of URL paths.

@tfr42 tfr42 added enhancement enhancement or improvement contributions welcome asking for contribution (time and money sponsor) funding welcome financial sponsoring wanted (money) labels Aug 23, 2016
@tfr42 tfr42 added this to the 3.4.1 milestone Aug 23, 2016
@tfr42 tfr42 changed the title xlink:href Disable resolve of xlink:href for codelist values Aug 23, 2016
@tfr42 tfr42 added the medium label Nov 8, 2016
@tfr42
Copy link
Member

tfr42 commented Dec 6, 2016

It should be possible to disable the default behaviour of reference resolving for a configurable set of URL paths.

To be defined:

  • which configuration file should have this option?
  • which format for defining the URL path should be used?
    • regex pattern style or simple by defining a base URL path

@tfr42 tfr42 added the needs discussion requires discussion with contributor label Dec 6, 2016
@tfr42 tfr42 self-assigned this Dec 9, 2016
@tfr42 tfr42 added in progress and removed contributions welcome asking for contribution (time and money sponsor) funding welcome financial sponsoring wanted (money) labels Dec 9, 2016
@tfr42 tfr42 added ready and removed in progress labels Dec 15, 2016
@tfr42 tfr42 mentioned this issue Oct 23, 2017
10 tasks
@tfr42
Copy link
Member

tfr42 commented Nov 6, 2017

Please verify expected behavior against recent release candidate 3.4-RC5 and report your results here.

@tfr42 tfr42 modified the milestones: 3.4.1, 3.4 Nov 6, 2017
@tfr42 tfr42 removed the needs discussion requires discussion with contributor label Nov 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement enhancement or improvement medium ready
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants