-
Notifications
You must be signed in to change notification settings - Fork 6
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
shortcut attribute to define document properties #146
Comments
The committee has mixed feelings about doing this now. If it turns out to be very common, then probably. Can you provide some explicit use cases? |
I don't remember the specific use case I had in mind, but basically use cases would be exactly the same where you'd use |
I think the sticking point is that the properties are naturally key/value pairs and having a shortcut attribute to set them would require having to microparse the attribute value. The current standing certainly isn't "no, we're not doing that"; it's more a case of finding out how common the case is whether it's really worth the effort. |
Fair enough. But since properties are |
Oh, indeed. Brain cramp on my part. It would just be a map and we have a constructor syntax for maps. #facepalm |
Haha. BTW, I'm not super familiar with XPath 3, but a quick glance shows maps are introduced in XPath 3.1, and neither 3.0 nor 3.1 are referenced from XProc 2.0. Should #30 be reopened? |
Can it be considered to add a
properties
attribute to document-loader elements and steps (p:inline
,p:document
,p:load
) to set the document's properties as a shortcut of later invokingp:set-properties
?The text was updated successfully, but these errors were encountered: