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

xproc / 3.0-steps

Repository for change requests to the standard step library and for official extension steps

10 stars 7 forks source link

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

Closed xml-project closed 4 years ago

xml-project commented 4 years ago

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

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

xatapult commented 4 years ago

❓ 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 commented 4 years ago

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

ndw commented 4 years ago

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.