We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is an aggregation of the discussion on "Describe context for understanding variables and options" (Issue 80 of the xproc/1.0-specification)
Opened by: ndw on 2014-10-08, 14:20h
Note also the as attribute ala XSLT. In section 2.5 or thereabouts.
motivated by discussion here XProc Minutes 8 Oct 2014http://www.w3.org/XML/XProc/2014/10/08-minutes
This issue is really about what happens when supplied options don't have the required type.
On 2015-06-12, 11:13h: ndw referenced this issue.
In the absence of ^; the type of shortcut option values is "xs:untypedAtomic" so they will be coerced to atomic types by the processor.
On 2015-06-12, 11:14h: ndw added the proposed-resolution label. On 2015-10-07, 14:40h: ndw added this to the XProc 2.0 Next PWD milestone.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe context for understanding variables and options
Opened by: ndw on 2014-10-08, 14:20h
ndw said on 2014-10-08, 14:20h:
Note also the as attribute ala XSLT. In section 2.5 or thereabouts.
xquery said on 2015-06-10, 14:59h:
motivated by discussion here XProc Minutes 8 Oct 2014http://www.w3.org/XML/XProc/2014/10/08-minutes
ndw said on 2015-06-11, 12:57h:
This issue is really about what happens when supplied options don't have the required type.
ndw said on 2015-06-12, 11:14h:
In the absence of ^; the type of shortcut option values is "xs:untypedAtomic" so they will be coerced to atomic types by the processor.
The text was updated successfully, but these errors were encountered: