We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Blog: David Loshin Subscribe to this blog's RSS feed!

David Loshin

Welcome to my BeyeNETWORK Blog. This is going to be the place for us to exchange thoughts, ideas and opinions on all aspects of the information quality and data integration world. I intend this to be a forum for discussing changes in the industry, as well as how external forces influence the way we treat our information asset. The value of the blog will be greatly enhanced by your participation! I intend to introduce controversial topics here, and I fully expect that reader input will "spice it up." Here we will share ideas, vendor and client updates, problems, questions and, most importantly, your reactions. So keep coming back each week to see what is new on our Blog!

About the author >

David is the President of Knowledge Integrity, Inc., a consulting and development company focusing on customized information management solutions including information quality solutions consulting, information quality training and business rules solutions. Loshin is the author of The Practitioner's Guide to Data Quality Improvement, Master Data Management, Enterprise Knowledge Management: The Data Quality Approachand Business Intelligence: The Savvy Manager's Guide. He is a frequent speaker on maximizing the value of information. David can be reached at loshin@knowledge-integrity.com or at (301) 754-6350.

Editor's Note: More articles and resources are available in David's BeyeNETWORK Expert Channel. Be sure to visit today!

Recently in Metadata Nusings Category

Do the structures described within XML schemas correspond to classes and objects described in Java or C++, or to entity relationship models? There seems to be a little bit of a debate on the topic. As an example, there does seem to be a correlation, which leads to the ability to automate the generation of Java classes that mimic XML schemas (see The Sun Java XML Binding Compiler for details).

On the other hand, the flexibility in defining schemas allows a clever (albeit, devious) practitioner to define structures that would challenge any object-oriented programmer.

I am currently looking at a project where we are reviewing the way XML schemas are defined in a way that eases the design of its supporting software. I have some definite ideas about this, but I'm interested in hearing some ideas from you readers. I will follow up on this topic, perhaps in an upcoming article.

Posted August 16, 2005 9:07 PM
Permalink | No Comments |

Occasionally, I attend meetings on behalf of one of my government clients. Today I was at one with a set of mixed topics, although the typical agendas focus on metadata. The usual meeting attendees are individuals involved in deploying metadata registries based on the ISO/IEC 11179 standard on Metadata Registries, but today's meeting featured a presentation by Mike Daconta, who is spearheading the effort to refine the Federal Enterprise Architecture's Data Reference Model.

What is interesting about the FEA DRM, as it is called, is that it is the last piece of the Federal Enterprise Architecture to b eput in place. Confused that an enterprise architecture can be defined without focusing on data first? Join the crowd...

In fact, only recently had there been any real movement in the Data Reference Model arena, and what had been released was an XML model intended to represent a way to register data sets for the purposes of data exchange. Now, considering that Mr. Daconta comes from the Department of Homeland Security, it is not surprising that the desire to effectively share information among government agencies is helping to drive the effort forward. One consideration, though, is that the rest of the FEA focuses more on assessing and documenting government investment in technology infrastructure and how that infrastructure is put to use to improve the way Federal agencies manage their IT investments. Because of this, my perception is that there is a bit of a disconnect between the rest of the FEA and the Data Reference Model part of it.

Luckily, our friends from the Federal Data Registry Users Group are pretty smart, and were able to direct some good questions to those defining the DRM, and Mike Daconta spent some time today addressing some of those questions. The conclusion was very inspiring, in that there may be a good opportunity to inject some good ideas and guidance into the use and value of metadata into a process that affects most, if not all, agencies in the Federal Government.

For more information on the continuing saga of the FEA DRM, see the project's Wiki.

Posted August 9, 2005 7:22 PM
Permalink | 1 Comment |


Search this blog
Categories ›
Archives ›
Recent Entries ›