Create New Classes for Software Components

[mosoriob]

We need to create a new class structure for handling different types of software components. This involves creating a superclass SoftwareComponent and two subclasses TapisSoftwareComponent and WCMSoftwareComponent.

Tasks

1. Create the SoftwareComponent superclass:

   • This will serve as the base class for different software components.

2. Create the WCMSoftwareComponent subclass:

   • This class will inherit from SoftwareComponent.
   • Add a property Location which will be an aggregation of all the files needed to execute the component. Typically, this is a zip file that includes the run script, support scripts, and specification files.

3. Create the TapisSoftwareComponent subclass:

   • This class will inherit from SoftwareComponent.
   • Add the following properties:
     • appVersion
     • appId
     • tenant

[dgarijo]

Hi, some comments:

• Software Component seems akin to software configuration. What would the difference be?
• The Location property exists. It's called hasComponentLocation: https://knowledgecaptureanddiscovery.github.io/SoftwareDescriptionOntology/release/1.9.0/index-en.html#hasComponentLocation. It has the same definition you are providing.
• There is a property for https://w3id.org/okn/o/sd#hasVersion to capture the version.
• There is a property for https://w3id.org/okn/o/sd#identifier to capture the identifier. I am not sure what a tenant is.
• WCMSoftwareComponent and TapisSoftwareComponent seem to be quite specific. What about creating an extension of the ontology including them?

[mosoriob]

Thank you for getting back to me.

At present, MINT utilizes the hasComponentLocation property to retrieve the component containing the run file and source code in Wings format. I am looking to expand support to include Tapis, another execution engine similar to Wings.

The issue I am facing with the hasComponentLocation property is that I am unable to differentiate whether the component is a Wings or Tapis component.

However, your response has prompted me to reconsider. I agree that TapisComponent appears to be quite specific. Perhaps the URL can contain information to distinguish between the components.

[dgarijo]

Hi Max! Yeah, I would distinguish by the component class (tapis component vs regular component), keeping the same property (has component location) for both. Unless a component can have 2 component locations for different systems, in which case maybe the location should be optionally a class instead of a URL (this would be less ideal because it could bring breaking changes). Happy to discuss this further if you have examples. I detected a typo in the ontology, so I can contribute doing a new release. El lun., 17 jun. 2024 7:22 p. m., Maximiliano Osorio < ***@***.***> escribió:

…

Thank you for getting back to me. At present, MINT utilizes the hasComponentLocation property to retrieve the component containing the run file and source code in Wings format. I am looking to expand support to include Tapis, another execution engine similar to Wings. The issue I am facing with the hasComponentLocation property is that I am unable to differentiate whether the component is a Wings or Tapis component. However, your response has prompted me to reconsider. I agree that TapisComponent appears to be quite specific. Perhaps the URL can contain information to distinguish between the components. — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALTIGT4UQWT4LW7NGTFF33ZH4LNXAVCNFSM6AAAAABJOKC56GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZTHE2DCOBZGQ> . You are receiving this because you commented.Message ID: <KnowledgeCaptureAndDiscovery/SoftwareDescriptionOntology/issues/20/2173941894 @github.com>