Is there an API for GUID-based Workflows?

Just wondering if anyone is using GUID-based workflows in their apps.

This thread mentions something called 'Cross Diciplinary Coordination Services' xDCS, which is apparently and outgrowth of ISM, Design Sync...which looks like a devlopment of the old Design History API. There doesn't seem to be much in the forums about xDCS. Any info online about what it does?

IFC is also based on GUIDs, as does Aecosim and OpenPlant. Mstn has its ElementID.

Aecosim's old Triforma Drawing Extration Manager (DEM) will persist the GUID from the orginal 3d element that produces a 2d proxy graphic in an extraction if the 'Preserve 3d Data' option is ticked. I think that the DV's also provide a similar link when a CVE is generated. Element/Display Handlers?

Recently, Prostructures has offered up the ability to track changes made in Aecosim, and automatically update its rebar objects. Presumably, this is done through reading the GUID's generated by Aecosim.

I also notices this thread, where ideally, the elements in one file would merge with another automatically. Similar to the way PS updates its rebar to suit a change made to an Aecosim wall, it would be good to have a 'smart' merge or copy 'associative' tool, which would allow the GUID's to be saved and used to track updates.

Can the ISM or Design History API be used to provide a generalised tool to 'copy and swap' selectively using the same interface as the Structural Synchronizer?

The app would offer the user to assign a GUID to an object (via the Item Types tool?), that would allow the user to 'copy monitor' objects that are copied into the model.

Maybe, the GUID dependency graph would be stored centrally by ProjectWise? Or in an ISM?

GUID's seem to be useful for tracking things, which must be something that will be increasingly needed in the data-centric BIM world?