Howdy, Odette. I was waiting to see if you posted this question on the Frameworx Community as Jonathan suggested but haven't seen it yet.
Deciding on how you want to categorize ResourceSpecifications (RS) is really up to you.
In the SID ResourceSpecificationType (RST) inherits from EntitySpecificationType (EST). This entity is in the Common Business Entities domain / Root Business Entities ABE. There is an EntitySpecificationTypeRelationship (ESTR) that allows a SID implementer to set up a tree/network of related ESTRs. So you could set up a tree of RSTs with a "Physical Resource" instance of EST as the top level and "Router", "Mobile Device",... related to it using ESTR. Or you could leave out the top level "Physical Resource" RST.
There is also a *-* association between RST and RS that allows a SID implementer to categorize a RS in many different ways.
------------------------------
John Reilly
John P. Reilly Sole Trader
------------------------------
Original Message:
Sent: May 29, 2018 09:30
From: Odette Tousignant
Subject: SID - Resource Specification Type
I will define the resource specification type. I read the SID Data Model , and I noticed many définitions to define the resource specification type.
1) Type will be Logical or Physical
2) Type will be more specific like Mobile Device, Router, VOD Title etc
What the best approach to use and do you recommend ?anks
Thanks
------------------------------
Odette Tousignant
Videotron G.P.
------------------------------