And other impenetrable acronyms.
It’s confusing to talk and think about these sorts of ideas, because to talk about metadata like this, you need to talk so very abstractly. We try to mean very precise things, but we don’t always have the precise words to describe them, or to be understood by people who may not mean the same things by the same words.
I’ve been confused by the DCAM for a while, myself. As I keep circling around and around trying to understand what’s going on, at this particular stage in my circling I’ve found this paper, Towards an Interoperability Framework for Metadata Standards, by Nilsson et al, to be very helpful, and I think I’m getting closer to understanding what DCAM is. When I go and look at my comments made to Pete Johnston’s blog post, linked above, around five months ago, already I wouldn’t ask those same questions now (although I can’t exactly answer them in clear language either–so tricky to talk about this stuff!)
I do start to wonder, though: Is DCAM trying to solve the _exact_ same problem RDF is? Is there any reason to have both? What does DCAM have that the “RDF suite” does not? Nilsson et al do say that “The RDF suite of specifications, however, follow a more similar pattern to the framework presented here.”