We *NEED* to save #xslt !
I read this article (https://wok.oblomov.eu/tecnologia/google-killing-open-web/) and cannot thing but the fact there’s a precise will to kill the free internet and make it a product.
RE: https://oldbytes.space/@drscriptt/116219403988667257
TIL I learned about #XML namespaces `select`ing them in #XSLT <xsl:… select=“…”/> statements.
What was particularly entertaining was the fact that the nodes weren’t prefixed.
Instead a namespace was set at — I don’t know what to call it — the same way the stylesheye is referenced in a <? … ?> statement up above the <!DOCTYPE/>.
Once I figured that out and how to select it, things started clicking.
TIL that #xsltproc (on my system) only supports #XSLT version 1.1.
I learned this because the `replace( … )` function apparently requires XSLT version 2.0.
I want the `replace( … )` function because #IANA put two comma separated addresses in one record while all the others are a single address.
The node the addresses are in is named “address” which seems singular to me.
But IANA put `192.0.0.170/32, 192.0.0.171/32 ` in an <address/> node.
Thanks IANA. 😒
<registry>
<registry>
<!-- … -->
<record>
<address>…</address>
<!-- … -->
</record>
<!-- … -->
</registry>
</registry>
No, I have no idea why <registry/> is nested the way that it is.
https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xml
Pls Snd Hulp
I willingly wrote an #XSLT (.xsl) file to parse an Oracle 11i #XML log file.
I had to normalize the XML log file first:
- Prepend opening root node
- Append closing root node
- Substitute ' (apostrophe) in place of '
The XSLT select="..." statements are making more sense.
Today added compound requirements and working with ancestor::* nodes.
RE: https://genart.social/@davidcarew/116178444886600923
I absolutely agree with @davidcarew about usefulness of #sed and #awk.
I am starting to dabble with #xsltproc for some #XML aware bulk modification.
I used #XSLT to convert an XML file into #wget commands to download additional XML files I needed for a project. (First file listed the base name of additional files, each in an element / node.)
I … I think I fell into a hole.
Said hole seems to be #XML + #XSLT shaped.
XSLT’s ability to translate XML into #HTML and / or plain text … is — in a word —AMAZING to me.
Combine #XPath selection and … WOW!
I feel like this is going to be a game changer for some things that I do. Similar to #regularExpressions were 25+ years ago.