Error in user YAML: (<unknown>): did not find expected key while parsing a block mapping at line 1 column 3
---
- playList: Autumnalist
creator: [RMBLRX](https://keybase.io/rmblrx)
date: 20171023
numTracks: 8
gist: 06cab21b7999f706124dcb703922858c
trackList:
- track: Habit
artist: Uniform
album: Wake in Fright
musicBrainz: f206bcba-e25f-4159-acff-099e71469418
- track: Anthem for No State, Pt. III
artist: Godspeed You! Black Emperor
album: Luciferian Towers
musicBrainz: d616f4c1-0d9c-45fc-8914-bd60e86a903f
- track: Anti Body
artist: Gazelle Twin
album: Out of Body
musicBrainz: c3b83d5f-6335-4302-ade1-70580a38bb21
- track: The Hacker
artist: Johnny Jewel
album: The Hacker
musicBrainz: 4820e0a1-f717-42ef-a899-dbc09a549b7b
- track: Discovery
artist: KCE Japan Sound Team
album: Metal Gear Solid
musicBrainz: f5bf00cc-1b1f-4c0b-916e-2fb5bd38bc17
- track: Rain of Ruin
artist: Suicide
album: A Way of Life
musicBrainz: 86d851f5-26b5-4492-8b53-7ca65e0c02a8
- track: Anthem for No State, Pt. I
artist: Godspeed You! Black Emperor
album: Luciferian Towers
musicBrainz: f5fb80ee-6bf1-4174-8289-972e7d63e8ba
- track: Gayane Ballet Suite (Adagio)
artist: Симфонический оркестр Санкт-Петербургской филармонии, Геннадий Николаевич Рождественский
album: 2001: A Space Odyssey
musicBrainz: 2dc25b73-50c8-403e-aa13-1f61182511bd
---
A dissipation of energies--this playlist ushers in the cold and the dead at great expense of those passions yet latent from the Summer. It is a battening down for the harder wisdoms of Winter.
This is my first attempt at creating a simple, human-readable playlist format utilizing YAML frontmatter, inspired by this post by Katy Decorah. My intention is for this to be readily convertible to XSPF and perhaps observing Schema standards or, more importantly, accomplishing both. The content after the frontmatter should be interpreted as the annotation, and everything else should be rather straightforward to convert to XSPF, but I could imagine a more complicated scheme for interpreting multiple playlists from one file in which the annotation is specified in the frontmatter or else somehow designated in the content through tagging.
One change I already have in mind is to use markdown link format to put the musicBrainz info right up with the track title, instead of using a separate field. I would then just have to automatically interpret whether the included info is in fact for Music Brainz or perhaps some other form of metadata archiving (JAAK, for instance, or some Swarm or IPFS hash, maybe). Then we could also include a hierarchy of source links that could be used to resolve content for some sort of web or web-based player (I can imagine embedded widgets, chrome extensions, or desktop applications built on, say, Electron); though if the player uses metadata to resolve content through its own battery of resolvers, it could maybe just use that source list as suggestions (obviously if the track is available locally, that would typically take precedence).
Anyway, just spit-balling at this point.