OIRs - .id vs not .id

[MikeLockwood]

OTB, many OIR AttrValue and AttrConstraint elements include both, for example:

folder, folder.id

teamTemplate, teamTemplate.id

lifecycle, lifecycle.id

organization, organization.id

I put in an innocent-sounding tech support call 2 months ago - why have both? What do they each do? This evidently led to quite a few discussions within PTC (per tech support) andno one at PTCcould provide the answer. Then, I asked a few long-term folks in PTC directly - no one knows. There is an SPR being written for R&D to investigate and possibly clean this up (remove one or the other) in the future if in fact that can be done.

Meanwhile, we're attempting to simplify, clean up and streamline OIR's where possible. Does anyone know why both are used? Not a big deal in the grand scheme of things, but can one be used and not the other?

[ddemay]

It has to do with persistence. believe they resolve to the same thing these
days. Never got curious enough to peek at the logic other than if you were
a java programmer and use WTIntrospection you'd see both. .id classically
references the ida2a2 of the object identifier or the long primitive value
of the ObjectIdentifer.



When OIRs get stored in the database, they are blobbed, so it could be
something to do with serialization and the introspection, again just
throwing that on out there. I think you have asked about these before,
will have to add that one to the list, but my hunch tells me it's related to
one of these.



Doubt it'll get cleaned up per se.