tonyl/pillarsoftware wrote:
How do you believe Metadata changes should be approached in theI don't think there's a major difference. In each case the questions are the same:
following cases?
1) If the reason for the Metadata change is the introduction of a new
business rule that will require code changes.
2) If the reason for the Metadata change is simply to capture more data
that is non-essential to any transaction processing.
How do we retroactively update existing content?
How do get people to add the metadata and when
To what do we attach the metadata?
etc.
I recommend thinking about it for longer :-)The last idea on this thread was that EVERY thing should be in database...I thought about that for like 1 nanosecond and agreed. Because that
There are many practical difficulties with putting everything in the database - I know, I have to deal with them.
Why would you want to do that? Surely we should strive for independance between these things, not rolling them all up into one horribly complex lump. Do you want to store your class libraries in the database too?! Version control for content should not be tied to version control for code. Vignette et. al. please take note :)way...a version stamp could be applied that "pinned" the XML, the XSD, the XSL and the actual processing code (ASP, JAVA, PHP, whatever)
So is it ok to use this list for peer design review questions???? I hope so.
I'm technical so it's fine by me. List mom's please speak up! -- Jonathan Peterson Technical Manager, Unified Ltd, +44 (0)20 7383 6092 [EMAIL PROTECTED] -- http://cms-list.org/ more signal, less noise.
