Closed briesenberg07 closed 2 years ago
wht not xslt? You want to extract nodes and sort them, no? It seems like XSLT is a good tool.
I got it in my head that XQuery might create something like the results you get with the XPath Builder view (or a "Find all" operation). Not a generated document, but a clickable set of results allow you to navigate the instance.
See screenshots for XPath Builder** results--these are great, but I don't think I can add a sort here (maybe I'm wrong about this?).
** Noticing that this tool is "XPath/XQuery Builder". I think my next step here is to read some Oxygen documentation! Thanks for taking a look @gerontakos --
[1] Use XPath Builder to match on the properties I'm outputting to my template
[2] Get results
[3] Click on results to navigate the instance, check my work, and make changes as needed
Unless there's something I don't know, XQuery is similar to XSLT in that you generate output using some input. This location of a node in the input document and the ability to traverse the input document is, I believe, an oXygen service. However, you could simulate this in XSLT output easily enough. Pop it into HTML, provide a link in a strategic place in the extracted node, etc.
XPath now has fn:sort(). You might want to check it out. (I still haven't used it.)
This isn't important right now. Oxygen XQuery Builder is sufficient to move through implementation_sets when designing templates.
What's the best, easiest way to do this? I'm thinking of something that is not a stylesheet but can retrieve a set of results in much the same way that the Oxygen XPath Builder does, but I don't think I can include a sort when using XPath Builder. Is XQuery useful here? I don't know how to XQuery. Note to self @briesenberg07 ask @gerontakos