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

We need to say more about p:document-properties (and friends) #511

xml-project opened this issue Aug 23, 2018 · 2 comments · Fixed by #912


Copy link

@xml-project xml-project commented Aug 23, 2018

By implementing p:document-properties() and friends, some questions and problems came up to me. As it is a rather long story to tell, I created a wiki-page. I hope you don't mind.


This comment has been minimized.

Copy link

@ndw ndw commented Sep 4, 2018

Thank you for the thoughtful analysis. I'm sure we'll talk about this over the next couple of days, but just a passing observation: with respect to having functions that only operate on the context node, you say that this means the $variable case will go away. I don't think that's true:

<p:variable name="properties" select="$variable/p:document-properties()" />

I don't think we gain anything by removing the argument. I think the answer is that the implementation is required to keep some sparkle around. If you pass (explicitly or via the context item) an item that has as it's ancestor a node that was an XProc document with properties, you get those properties.

I don't feel strongly, at the moment, about non-XProc documents. I think users will be least surprised if properties are manufactured for content type and (where applicable) base URI.

@ndw ndw self-assigned this Sep 6, 2018

This comment has been minimized.

Copy link

@ndw ndw commented Nov 9, 2019

The 'base-uri' and 'content-type' properties will always return a value; for a node, the base URI property will be returned if it has one and the content type will be appropriate for that node type; for maps, arrays, and other atomic values, the base-uri and content-type are ().

ndw added a commit to ndw/3.0-specification that referenced this issue Nov 17, 2019
@ndw ndw closed this in #912 Nov 17, 2019
ndw added a commit that referenced this issue Nov 17, 2019
Fixed #511 and a few minor markup errors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.