Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding a picture and potentially a short description field to Asset and Participant objects #1

Open
xamcost opened this issue Nov 18, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@xamcost
Copy link

xamcost commented Nov 18, 2024

Hi there! I am opening this issue to suggest two things:

  1. the addition to the Asset and Participant object of a picture field, which would be a url pointing to an image. The idea of this is to enable them to illustrate an Asset or Participant display in the marketplace with a logo. It is a low hanging fruit and would make the marketplace more appealing.
  2. the addition of a short_description field in the Asset object, which would just be text. Its goal is to be a one sentence summary of what should be in the longer description field. This is to enable prospective consumer to have a quick overview of the asset in the offering.

I suggested adding these fields in Asset, but if you think it fits better elsewhere, such as in AssetProvision, let me know.

@xamcost xamcost added the enhancement New feature or request label Nov 18, 2024
@juanrasantana
Copy link

Hi!

I agree with point (1). We could add the foaf:img property to the ontology as part of the Participant class. This field could be recommended but not mandatory.

The same applies to the short_description property. A non-mandatory property could be added to the ontology. However, TBH, I’m not that keen on adding “duplicated” fields, as they introduce an additional "burden" for users. While I understand the reasoning behind displaying such information in the GUI, as a provider with multiple assets, I’d likely avoid adding two descriptions per asset. That said, as mentioned, we can always add it as a non-mandatory property.

If @telsaleh agrees, we update the ontology with those two properties.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants