home.social

#balisage — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #balisage, aggregated by home.social.

fetched live
  1. New mailing list to discuss making an international organisation for XML (IXO??), a new home. The future of declarative markup, perhaps.

    lists.psu.edu/cgi-bin/wa?SUBED

    An upcoming zoom call on 25th September is also open.

    #XML #XMLisNotDead #XSLT #XQuery #XPath #foundation #XML_Foundation #declarativeMarkup

    Discussions started around #Balisage2026 #Balisage this year.

  2. New mailing list to discuss making an international organisation for XML (IXO??), a new home. The future of declarative markup, perhaps.

    lists.psu.edu/cgi-bin/wa?SUBED

    An upcoming zoom call on 25th September is also open.

    #XML #XMLisNotDead #XSLT #XQuery #XPath #foundation #XML_Foundation #declarativeMarkup

    Discussions started around #Balisage2026 #Balisage this year.

  3. The #Balisage2026 conference is over, not for another year but forever.

    We knew it was coming, but it’s still very emotional - it’s the last in a series of conferences i first went to in 1989.

    Balisage did not end because markup is no longer a good idea - the organisers are retiring. Markup is more useful now than it has ever been.

    #XMLisAlive #XML #Balisage

  4. The #Balisage2026 conference is over, not for another year but forever.

    We knew it was coming, but it’s still very emotional - it’s the last in a series of conferences i first went to in 1989.

    Balisage did not end because markup is no longer a good idea - the organisers are retiring. Markup is more useful now than it has ever been.

    #XMLisAlive #XML #Balisage

  5. ›Bibliografische‹ Daten zu den Digital Humanities, in #XML codiert und als Online-Datenbank aufbereitet. Das funktioniert dank #SaxonJS mittels #XSLT (3.0 !) lokal im Webbrowser -- als ›static website‹ ohne weitere Server-Interaktion ... (frühe Betaversion, Code und Daten alsbald auf GitLab).

    dh-fx.de/dhc/dhc.html

    #DHd #DigitalHumanities #Balisage #ProgrammingHistorian #ZfdG #GND

  6. ›Bibliografische‹ Daten zu den Digital Humanities, in #XML codiert und als Online-Datenbank aufbereitet. Das funktioniert dank #SaxonJS mittels #XSLT (3.0 !) lokal im Webbrowser -- als ›static website‹ ohne weitere Server-Interaktion ... (frühe Betaversion, Code und Daten alsbald auf GitLab).

    dh-fx.de/dhc/dhc.html

    #DHd #DigitalHumanities #Balisage #ProgrammingHistorian #ZfdG #GND

  7. The end of an era (at least for me): This year's Balisage conference will be the last:
    balisage.net/index.html
    I've been to the conference from 2008 to 2012 and it was great fun. I will miss the #balisage folks although my focus of work has changed away from XML some years ago.

  8. Call for papers: balisage.net/index.html

    Information representation is about more than HTML and JSON...

    Balisage is the most theoretical of the markup conferences (Nothing is more practical than a good theory). And this is the last.

    No! While that tree stands, our scholar-gypsy is not gone! as Vaughan Williams quoted Matthew Arnold.

    Don’t miss your last chance! to speak, to listen, to learn, to teach, to be.

    #XML #MarkupMonday #Balisage2026 #Balisage #markup

  9. Call for papers: balisage.net/index.html

    Information representation is about more than HTML and JSON...

    Balisage is the most theoretical of the markup conferences (Nothing is more practical than a good theory). And this is the last.

    No! While that tree stands, our scholar-gypsy is not gone! as Vaughan Williams quoted Matthew Arnold.

    Don’t miss your last chance! to speak, to listen, to learn, to teach, to be.

    #XML #MarkupMonday #Balisage2026 #Balisage #markup

  10. Two markup/XML conferences announced today

    XML Prague - xmlprague.cz/ in... er... Prague... and

    26th annual meeting of the Text Encoding Initiative (TEI) tei2026.tei-c.org/ in Vancouver.

    Don’t forget also Balisage - balisage.net/

    #MarkupMonday #TEI #tei2026 #XML #XMLPrague #XML_Prague #conference #balisage #markup #digitalHumanities #techDoc

  11. Two markup/XML conferences announced today

    XML Prague - xmlprague.cz/ in... er... Prague... and

    26th annual meeting of the Text Encoding Initiative (TEI) tei2026.tei-c.org/ in Vancouver.

    Don’t forget also Balisage - balisage.net/

    #MarkupMonday #TEI #tei2026 #XML #XMLPrague #XML_Prague #conference #balisage #markup #digitalHumanities #techDoc

  12. Yesterday i received a lovely card with a thank you note for speaking at conference, with a detailed comment praising something from the talk i gave.

    It’s always been an honour and a pleasure to speak at Balisage, and I always love getting these cards.

    #Balisage #Balisage2025 #xml #conference #thankYouLetter #classAct

  13. Yesterday i received a lovely card with a thank you note for speaking at conference, with a detailed comment praising something from the talk i gave.

    It’s always been an honour and a pleasure to speak at Balisage, and I always love getting these cards.

    #Balisage #Balisage2025 #xml #conference #thankYouLetter #classAct

  14. #balisage HC: More to do

    Guidelines themselves need to be made more accessible.

    Add more language support.

    Some content from old site not in new site yet. Want to be selective and prune cruft.

    Incrementally improve: which is now easier to do than in the Wordpress world.

  15. #balisage HC: More to do

    Guidelines themselves need to be made more accessible.

    Add more language support.

    Some content from old site not in new site yet. Want to be selective and prune cruft.

    Incrementally improve: which is now easier to do than in the Wordpress world.

  16. #balisage HC:

    So: is this better?
    A: It is for me [HC]

    Seems better for users: these users are nerds, find editing Markdown easier than Wordpress. Lots of mental overhead.

    Likely better support for internationallization.

    Much more accessible.

  17. #balisage HC:

    So: is this better?
    A: It is for me [HC]

    Seems better for users: these users are nerds, find editing Markdown easier than Wordpress. Lots of mental overhead.

    Likely better support for internationallization.

    Much more accessible.

  18. #balisage HC:

    Documentation is separate repo, so mount as subproject and pull it in during build

  19. #balisage HC:

    Documentation is separate repo, so mount as subproject and pull it in during build

  20. #balisage HC:

    Documentation repository
    TEI XML files
    Needs to be integrated website in a couple of places, render to HTML

    So extend 11ty to support TEI XML; use CETEIcean to do that

  21. #balisage HC:

    Documentation repository
    TEI XML files
    Needs to be integrated website in a couple of places, render to HTML

    So extend 11ty to support TEI XML; use CETEIcean to do that

  22. #balisage HC:

    TEI guidelines has separate and complex build system with multiple targets, but does have to integrate with website (unlike the vault); same menu structures etc.

  23. #balisage HC:

    TEI guidelines has separate and complex build system with multiple targets, but does have to integrate with website (unlike the vault); same menu structures etc.

  24. #balisage HC:
    What wasn't managed by CMS?
    TEI guidelines themselves
    The Vault (but all static, fixed)
    The Documentation repository

  25. #balisage HC:
    What wasn't managed by CMS?
    TEI guidelines themselves
    The Vault (but all static, fixed)
    The Documentation repository

  26. #balisage HC: recap

    Handcrafted static HTML =>
    Static HTML generated from XML =>
    Dynamically processed HTML from XML =>
    Same, managed by CMS =>
    HTML goop =>
    Static HTML generated from source

  27. #balisage HC: recap

    Handcrafted static HTML =>
    Static HTML generated from XML =>
    Dynamically processed HTML from XML =>
    Same, managed by CMS =>
    HTML goop =>
    Static HTML generated from source

  28. #balisage HC:

    Sept 3rd 2024: New website!

    Think it looks better.

    Responsive sizing
    Static site => vastly harder to hack

    Built using Eleventy (11ty.dev)
    Sources on github repository (github as CMS)
    Most sources in Markdown now

  29. #balisage HC:

    Sept 3rd 2024: New website!

    Think it looks better.

    Responsive sizing
    Static site => vastly harder to hack

    Built using Eleventy (11ty.dev)
    Sources on github repository (github as CMS)
    Most sources in Markdown now

  30. #balisage HC:

    2019-2024 Wordpress still

    Find it not nearly as easy as it was supposed to
    Wordpress makes terrible markup
    Every week new and exciting exploits so have to keep updating plugins

    Proposed in 2023 to migrate to static site, ETA 1 year

  31. #balisage HC:

    2019-2024 Wordpress still

    Find it not nearly as easy as it was supposed to
    Wordpress makes terrible markup
    Every week new and exciting exploits so have to keep updating plugins

    Proposed in 2023 to migrate to static site, ETA 1 year

  32. #balisage HC:

    2019: More churn
    Needed to find stable home => Huma-Num but ended up doing it in more of a rush than we had expected

  33. #balisage HC:

    2019: More churn
    Needed to find stable home => Huma-Num but ended up doing it in more of a rush than we had expected

  34. #balisage HC:

    Time for content management systems

    2007: mildly hacked OpenCMS (for next decade); edited via Java applet

    mid 2018: Move to WordPress

    Feb 8th, 2018: DISASTER!
    Catastrophic disk failure (backups, but restoration took a very long time) moved to new infrastructure

  35. #balisage HC:

    Time for content management systems

    2007: mildly hacked OpenCMS (for next decade); edited via Java applet

    mid 2018: Move to WordPress

    Feb 8th, 2018: DISASTER!
    Catastrophic disk failure (backups, but restoration took a very long time) moved to new infrastructure

  36. #balisage HC:

    1999 1st consortium webpage:
    Very straightforward HTML

    2001 more professional appearance; tables for layout; "this was generated from XML master"

    2005 new design; XML pages dynamically rendered with Apache Cocoon ("where possible")

  37. #balisage HC:

    1999 1st consortium webpage:
    Very straightforward HTML

    2001 more professional appearance; tables for layout; "this was generated from XML master"

    2005 new design; XML pages dynamically rendered with Apache Cocoon ("where possible")

  38. #balisage HC: History of the website

    Background: TEI (Text Encoding Initiative) began in 1987, consortium formed in 1999

    Parts of TEI website predate consortium:
    (From archive.org) hand-crafted HTML

  39. #balisage HC: History of the website

    Background: TEI (Text Encoding Initiative) began in 1987, consortium formed in 1999

    Parts of TEI website predate consortium:
    (From archive.org) hand-crafted HTML

  40. #balisage Q&A suggests looking at OpenLyrics as a target

  41. #balisage Q&A suggests looking at OpenLyrics as a target

  42. #balisage EB:
    In text analysis course?

    Requires encountering multiple cultures in text analysis: flat strings/token streams vs structuralists: useless to be exposed to that

    More of an adventure for students

    Continue to teach? I think so

  43. #balisage EB:
    In text analysis course?

    Requires encountering multiple cultures in text analysis: flat strings/token streams vs structuralists: useless to be exposed to that

    More of an adventure for students

    Continue to teach? I think so

  44. #balisage EB:
    What did we learn?
    Was it worth it?

    Greatly enhanced command line upskilling
    Grammar-writing encourages appreciation of meaningful structures
    Learning as an art form

    IXML vs regex search/replace
    more elegant, harder, less sequential, more installations, more declarative

  45. #balisage EB:
    What did we learn?
    Was it worth it?

    Greatly enhanced command line upskilling
    Grammar-writing encourages appreciation of meaningful structures
    Learning as an art form

    IXML vs regex search/replace
    more elegant, harder, less sequential, more installations, more declarative

  46. #balisage MS:

    Look at iXML over ChordPro

    Getting rid of ambiguity relied on special nullableText which also excluded meta charactrers

  47. #balisage MS:

    Look at iXML over ChordPro

    Getting rid of ambiguity relied on special nullableText which also excluded meta charactrers

  48. #balisage MS:

    MEI focused on presentation of sheet music
    MusicXML also to much so
    ChordPro is non-XML markup, but closer to what we want and there is UltimateGuitar to ChordPro converter at ultimate.ftes.de

    Discovered this after semester, but would have been much better for us

  49. #balisage MS:

    MEI focused on presentation of sheet music
    MusicXML also to much so
    ChordPro is non-XML markup, but closer to what we want and there is UltimateGuitar to ChordPro converter at ultimate.ftes.de

    Discovered this after semester, but would have been much better for us

  50. #balisage MS:

    Weren't able to find good way to distinguish chord lines from text lines in iXML; just anything-that-isn't-eol

    Ended up with "monster regex" in XSLT

  51. #balisage MS:

    Weren't able to find good way to distinguish chord lines from text lines in iXML; just anything-that-isn't-eol

    Ended up with "monster regex" in XSLT

  52. #balisage MS:

    Source => iXML => XSLT => output XML | output lyrics| output chords

    Initially looked at Music Encoding Initiative but that is focused on sheet music so didn't work well for us

  53. #balisage MS:

    Source => iXML => XSLT => output XML | output lyrics| output chords

    Initially looked at Music Encoding Initiative but that is focused on sheet music so didn't work well for us

  54. #balisage MS:

    e.g.

    Am Ammaj9 Am7 D/F# FMaj7 G Am

    Lyrics below

    Sometimes just lyrics, sometimes just chords