[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Template representation [was Re: Collection Item Represenations]




5. Templates - Let's maximize the reuse and let
   templates be entries also.

Why should templates ever be differentiated from Ťother resourcesť? Because they're mostly textual? What if I want to upload an HTML document which is a resource (i.e. an example page) to my entry? Shouldn't that deserve its own wrapping as well?


Nah. Resources are resources, and they can all be managed natively without any wrapping, no matter if they're textual or not. I think templates should be managed exactly the same way as images, HTML files, text documents, and so on.

For those who disagree with this: why should we _not_ manage templates the same way as other resources? What kind of management does templates need that images, text documents, HTML files, videos etc., doesn't also need (if we look hard enough)?

The wrapper may not provide any value in the core, but without an XML wrapper, we might have trouble adding extensions in the Atom Way. At Six Apart our tools do store some other information with each template, which clients might want to manipulate.


Is this a place where extensibility is needed?

Ezra