← Prev in month
← Prev in thread
XML Design Choices
Hi,
I'm working a a blog XML format I hope to be logical and future proof.
The problem is the design of the mark-up itself.
For example: http://dev.speeple.com/blogs/examples/example.xml?year=2008&month=4&day=2&title=roma-0-2-manchester-united-arsenal-1-1-liverpool-fenerbahce-2-1-chelsea
I have a small urge to rap /blog/post/tag nodes into a container <tags> and ditto for /blog/post/related, but technically this doesn't increase extensibility and creates more overhead (more data and redundancy).
Would you agree adding <tags> etc wrappers would be redundant and not increase accessibility/extensibility?
I'm working a a blog XML format I hope to be logical and future proof.
The problem is the design of the mark-up itself.
For example: http://dev.speeple.com/blogs/examples/example.xml?year=2008&month=4&day=2&title=roma-0-2-manchester-united-arsenal-1-1-liverpool-fenerbahce-2-1-chelsea
I have a small urge to rap /blog/post/tag nodes into a container <tags> and ditto for /blog/post/related, but technically this doesn't increase extensibility and creates more overhead (more data and redundancy).
Would you agree adding <tags> etc wrappers would be redundant and not increase accessibility/extensibility?
← Prev in month
← Prev in thread