Thanks, yes, this type of feedback is helpful. YAML was chosen primarily because it is a superset of JSON and is, on a very basic level, a method of storing structured data in a human friendly way. XML is hard to write because of the tags, and JSON is a bit noisier due to brackets.
Yes, it would probably be a good idea to define elements more explicitly, their format, and structure. The idea of writing a spec is daunting, and your questions make me rethink how I should approach this.
In my mind I like the idea of someone being able to create or edit this type of file by hand, primarily as a fast way of populating a Drupal database or some other CMS, and likewise as a way to export data in a way that isn't just a SQL dump or spreadsheet. I see it as document that is a combination of a sitemap + metadata, in that it intends to represent music data, but the ultimate destination is markup/HTML - for it to be imported/interpreted and displayed via a web browser. It would be something that could generate a discography website (like a config file?), as opposed to merely representing one that already exists. The target audience is a musician or record label that needs a way to easily manage their discography metadata, without getting tripped up or locked into specific CMS's, software packages, machine formats, etc.
Definitely need to think about this some more and figure out what the design constraints are...
Playlist mailing list
|Free forum by Nabble||Edit this page|