Markup, ECM and Social (De)Construction
I write this little post as I work with some guys to create an integration (mashup? composite application? where are the lines exactly?) between Oracle ECM and a markup/viewer/annotation engine from another part of the Oracle tech stack.
I got to thinking about what makes redline markup, version comparison and anotation so different from tagging and discussion threadding? After all, redlining, anotation, compare features have been part of apps for quite some time (e.g. "track changes" in MS Word).
Is it the fact that tagging is typically a bit "farther away" from the artifact all that separates the concepts? Tags are often stored as metadata (either actually or metaphorically) while markup is often stored as a separate file and then presented as an overlay layer on the artifact (if it is not stored directly in the artifact (e.g. "track changes")
You can already see a blending of anotation style markup with tagging (e.g. facebook's imagemap based tagging of parts of photos).
So while I see a value to the "deep" editorial and collaborative review style capabilities of redlining/anotation/viewing technologies, I'm wondering where is the difference between these and a more generic tagging? Difference of kind or just degree?
