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

Join Adjacent Text Nodes in the XDM of Step Results? #807

gimsieke opened this issue May 3, 2019 · 1 comment


None yet
2 participants
Copy link

commented May 3, 2019

@xml-project tried to specify an error for a p:hash result that replaces the “document element” with a text node. Now that we allow multiple top-level elements below a document node, p:hash might create multiple adjacent text nodes. Admittedly, this is a pathological case, but we need to specify more accurately what’s supposed to come out of a step.
When these adjacent text nodes are serialized, they are merged (see #722) according to S6 in sequence normalization.
But how does the XDM look after it has emerged from a step? I don’t think a full sequence normalization is in order here since for some serialization methods, sequence normalization must not be performed, and some normalization steps only make sense if the document is immediately going to be serialized.
The main issue here seem to be adjacent text nodes. Should we say that adjacent text nodes a) must be merged or b) may be merged before they emerge from a step?


This comment has been minimized.

Copy link

commented Jun 10, 2019

Adjacent text nodes in a single document must be merged per 6.7 in the XDM spec.

@ndw ndw closed this Jun 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.