Comments on: A curious reader asks…about enterprise metadata http://jtonedm.com/2007/12/11/a-curious-reader-asksabout-enterprise-metadata/ James Taylor on Everything Decision Management Mon, 14 May 2012 18:05:17 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Enterprise Metadata for a curious reader | Smart (Enough Systems, the blog) http://jtonedm.com/2007/12/11/a-curious-reader-asksabout-enterprise-metadata/comment-page-1/#comment-1450 Enterprise Metadata for a curious reader | Smart (Enough Systems, the blog) Mon, 17 Dec 2007 19:12:02 +0000 http://jtonedm.com/2007/12/11/a-curious-reader-asksabout-enterprise-metadata/#comment-1450 [...] replied to my post about his question on enterprise metadata. He, like me, prefers David Marco's definition of metadata as "all physical data and knowledge [...] [...] replied to my post about his question on enterprise metadata. He, like me, prefers David Marco’s definition of metadata as “all physical data and knowledge [...]

]]> By: Mike Kavis http://jtonedm.com/2007/12/11/a-curious-reader-asksabout-enterprise-metadata/comment-page-1/#comment-1171 Mike Kavis Wed, 12 Dec 2007 03:57:56 +0000 http://jtonedm.com/2007/12/11/a-curious-reader-asksabout-enterprise-metadata/#comment-1171 1) The broader definition because the business rules pertaining to the data is important. 2)The end goal is to provide both end users (analytics and power users) and developers with access to the logical view of our data. I basically want to hide the complexity of the physical representation of the data and expose derived values. That way, whether people are writing code using SAS, Microstrategy, Java, .Net, or if they are using a query tool, they will all get the same answer. And when the business rules of a metric changes, we change it in one place. 3) Not really. We are using a MDM tool for our initial BPM/SOA projects but we are not currently addressing the enterprise. 1) The broader definition because the business rules pertaining to the data is important.

2)The end goal is to provide both end users (analytics and power users) and developers with access to the logical view of our data. I basically want to hide the complexity of the physical representation of the data and expose derived values. That way, whether people are writing code using SAS, Microstrategy, Java, .Net, or if they are using a query tool, they will all get the same answer. And when the business rules of a metric changes, we change it in one place.

3) Not really. We are using a MDM tool for our initial BPM/SOA projects but we are not currently addressing the enterprise.

]]>