Sorry I was unable to provide input on this thread prior to this point and I am glad you were able to progress in your journey with a level of success.
Two type of attribute linkages are User Data Linkages (UDLs) and DMRS linkages. DMRS linkages are special linkages that if the User bit of the header is not set then the linkage (ID 0) is used and respected, where typically set for UDL processing you require a "magic number" assigned by Bentley in the 2nd word of the linkage header (e.g. like 0x57FA/0d22522 assigned to Pelican Forge). Once Bentley assigns a unique ID we do not know how each application developer proceeds to implement their own custom data structure(s). We simply maintain a unique registry of IDs to avoid conflict between applications and record original requestor contact details.
My "safe coding" recommendations would be to investigate which Bentley products (and APIs or SDKs) may be able to provide access to your industry/market specific data in a reliable manner allowing you to take control of that valuable business data/intelligence and leverage within your operations and workflows.
So IMHO the question should possibly be:
Is there a Bentley product and API/SDK available that can properly access and decode my Industry/Market specific Application data so I can access, transform, and perform event-based processing of the data within my business systems?
If the originating application is a Plant, Piping, Raceway, etc. industry/market type of application; consider looking into Bentley product offerings for a given similar market to determine if a.) the product supports the originating data format , and b.) ask if that product also provides an API or SDK allowing programmatic access.
HTH,
Bob
Two type of attribute linkages are User Data Linkages (UDLs) and DMRS linkages. DMRS linkages are special linkages that if the User bit of the header is not set then the linkage (ID 0) is used and respected, where typically set for UDL processing you require a "magic number" assigned by Bentley in the 2nd word of the linkage header (e.g. like 0x57FA/0d22522 assigned to Pelican Forge). Once Bentley assigns a unique ID we do not know how each application developer proceeds to implement their own custom data structure(s). We simply maintain a unique registry of IDs to avoid conflict between applications and record original requestor contact details.
My "safe coding" recommendations would be to investigate which Bentley products (and APIs or SDKs) may be able to provide access to your industry/market specific data in a reliable manner allowing you to take control of that valuable business data/intelligence and leverage within your operations and workflows.
So IMHO the question should possibly be:
Is there a Bentley product and API/SDK available that can properly access and decode my Industry/Market specific Application data so I can access, transform, and perform event-based processing of the data within my business systems?
If the originating application is a Plant, Piping, Raceway, etc. industry/market type of application; consider looking into Bentley product offerings for a given similar market to determine if a.) the product supports the originating data format , and b.) ask if that product also provides an API or SDK allowing programmatic access.
HTH,
Bob