I took a break from work over the holidays -- actually shut off my work PC -- but of course my brain kept chewing away on the matter of metadata metamodels. So, I sat down last night and cranked out the following PV model:
The metadata element itself is modeled as a class with the prefix MD_. Within the class is a single attribute whose properties shall be set to reflect the canonical definition of the element. That attribute, if appropriate, can be associated with validating business objects; for example, the ‘Project Number’ metadata element validates against the projectNumber attribute of the Project class (which itself is a canonical representation). Business Object(s) having the metadata element as an attribute are shown simply associated with the element.
I think this approach respects the overall PV metamodel semantics. Of course, I'll have to work with it for a while to make sure.
This afternoon I used this metamodel to model the metadata element set for one of my company's SharePoint-based document libraries. It worked, but I found I spent most of my time defining the design details of the elements because they'd been implemented as static SharePoint LOVs. I think one integration challenge for us will be assigning underlying sources for the LOVs and dynamically updating the LOVs along with the source. I wonder if that's been done...
Anyway, until I get some feedback from my colleagues I'm calling this one done.
0 comments:
Post a Comment