Yes, fair points. How far does the term “data architect” sum up some of these? I guess it relates to being able to design schemas / transforms that take into account all of these. And the focus is on the data, and its structure here. In the library world, we pretty much call that cataloguing, or systems librarianship. But then our schemas move pretty slowly… From: Len Bullard [mailto:Len.Bullard@ses-i.com] Those are popular phrases but largely meaningless unless further defined by the processes and kinds and types of data to be integrated. For example, how much analysis is required of the integrated sources, how are they QA’d and does that occur before or after the XML is created given that XML is the final format for delivering an integrated product? len From: Michael Hopwood [mailto:michael@editeur.org] So the problem space is…? How does “information integration” or “data integration” sound? That is one of the phrases I hear bandied around at lot at present. From: Michael Kay [mailto:mike@saxonica.com]
It’s a general qualifications question: do you expect an XML professional to: There's no such thing as an XML professional, any more than you can be a screwdriver professional or a fork-lift truck professional. People who define their abilities by the tools they can use proficiently are not professionals, they are technicians; professionals define their capabilities in terms of the problem space, not the solution space. |