3 ms·

I would first read Tim Bray's "Don’t Invent XML Languages" http://www.tbray.org/ongoing/When/200x/2006/01/08/No-New-XML-Languages http://www.tbray.org/ongoing/W

• deleted 16y ago
  [deleted]
• zdw 16y ago
  While I really dig Tim Bray's work, I tend to think it's very easy to get the wrong impression from his statements in that post. The point he's making is that, in most cases, you should use an existing XML schema instead of reinventing the wheel - it's bad to have a NIH attitude. For the post that started this discussion, an extension or modification on the iCalendar todo specification would make the most sense. The problem comes when you're trying to describe something totally new, or in a use case that deviates greatly from things that have come before - for example, I'm working on a network description schema for a project, and I haven't found anything similar, although it is informed by other schemas, from a variety of places (nmap's, and a few others mainly). Had there been prior work that matched what I was trying to do, I'd use it, but as there isn't, it's totally justified to create a new schema in this case.