> That's actually not what I meant by type-specific metadata.I meant things > like whether a String property should be displayed as a single or multi-line > entry form. If you're going to be dynamically creating a UI, you need this > type of metadata. One (albeit not the only) approach to this problem is to > use Sling and statically define the UI in scripts specific to particular > node/resource types. That way you don't need the metadata (or you do, but > it's essentially embedded in your HTML pages).
This is exactly what I'm facing. My plan is to enforce some conventions on the NodeTypes that back my application level document types. I'll have a limited set of application level propertyTypes that will be mapped to the nodetype properties via some layer of meta-data. For starters, I'll probably just embed my meta-data into some naming conventions on the node properties. But if it get's to thick, I'll just have to introduce something else. Probably storing such meta-data in the repository itself. I need to find a few minutes to peruse Sling on the off chance that I could integrate it into my own framework; but that path never seems to work out for me.
