You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! I am opening this issue to suggest two things:
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.
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.
The text was updated successfully, but these errors were encountered:
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.
Hi there! I am opening this issue to suggest two things:
Asset
andParticipant
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.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 inAssetProvision
, let me know.The text was updated successfully, but these errors were encountered: