You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can imagine other conversion scenarios that pose similar questions:
triples to xml
xml to triples
json to xml
xml to json
as well as questions surrounding 'exclude-inline-prefixes' and what 'expand-text' may mean in our new syntax. I propose we add this to next meeting agenda item.
The text was updated successfully, but these errors were encountered:
xml to csv
should yield
though this works only if each document is an xml document with an address root.
Its an open question about how to handle 'foreach' in these scenarios or if we are able to perform xpath filter on the input, like the following:
Which is roughly equivalent to old syntax @select on p:input.
csv to xml
How can we make text selection easier in this scenario to yield the following ?
We can imagine other conversion scenarios that pose similar questions:
as well as questions surrounding 'exclude-inline-prefixes' and what 'expand-text' may mean in our new syntax. I propose we add this to next meeting agenda item.
The text was updated successfully, but these errors were encountered: