highsource / highsource/ogc-schemas
Incorrect namespace prefix assignments results in invalid documents
- Dominant language
- JavaScript
- Stars
- 84
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
I'm not entirely certain that this is the correct place to post this issue. If it isn't, please direct me to the proper venue.
There are two methods that accept data of type ANY in an SOS 2.0 Insert Observation document.
Via the JaxB API they are accessed by:
- InsertObservationType.getExtension()
- InsertObservationType.getObservation().get(0).getOMObservation().getResult()
The namespace prefixes of these elements are being corrupted when they are marshalled.
Example (with an excessive number of namespaces):
Consider the below SOS2 InsertObservation document...
>
>
>
>
>
>
>
> .
>
>
>
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the JAXB entry points InsertObservationType.getExtension(), InsertObservationType.getObservation().get(0).getOMObservation().getResult(), and the supplied unmarshalling/remarshalling examples. Reproduce the namespace-prefix collision and inspect the generated XML. Done means the remarshal preserves consistent namespace bindings and the resulting document passes validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100