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

Expected result of p:cast-content-type for param-set #366

Closed
xml-project opened this issue Mar 15, 2020 · 3 comments
Closed

Expected result of p:cast-content-type for param-set #366

xml-project opened this issue Mar 15, 2020 · 3 comments
Assignees

Comments

@xml-project
Copy link
Contributor

@xml-project xml-project commented Mar 15, 2020

Currently the expected map type of <p:cast-content-type content-type="application/json" /> for c:param-set is not precicely defined. See xproc/3.0-test-suite#399

We should explicitly say that map(xs:QName, xs:string) is produced.

@xml-project xml-project self-assigned this Mar 15, 2020
@xatapult

This comment has been minimized.

Copy link
Contributor

@xatapult xatapult commented Mar 15, 2020

Why? A c:param-set is yaxd (yet another xml document). That's it a param-set doesn't make it special and IMHO shouldn't be treated special. Or am I missing something?

@xml-project

This comment has been minimized.

Copy link
Contributor Author

@xml-project xml-project commented Mar 15, 2020

@xatapult please see: xproc/3.0-test-suite#399
@ndw and me had different expectations about what is supposed to be the result. So will users, won't they?

@ndw

This comment has been minimized.

Copy link
Collaborator

@ndw ndw commented Mar 15, 2020

The only reason to support c:param-set as a special case in p:cast-content-type is to capture the XProc 1.0 semantics (for backwards compatiblity). If you look in the 1.0 spec, you'll see that the semantics are that each c:param element produces a QName by composing the name with a namespace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.