Generalize image to Agent?

[lecoqlibre]

Currently, only the Enterprise concept have an image field (logo).

I propose to replace this by an image field in the Agent concept.

This way, a Person could have a profile picture.

[mkllnk]

It looks like this was implemented:

ontology/src/DFC_BusinessOntology.rdf

Lines 2545 to 2553 in ab5897a

	<!-- https://github.com/datafoodconsortium/ontology/releases/latest/download/DFC_BusinessOntology.owl#logo -->
	<owl:DatatypeProperty rdf:about="https://github.com/datafoodconsortium/ontology/releases/latest/download/DFC_BusinessOntology.owl#logo">
	<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#FunctionalProperty"/>
	<rdfs:domain rdf:resource="https://github.com/datafoodconsortium/ontology/releases/latest/download/DFC_BusinessOntology.owl#Agent"/>
	<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#anyURI"/>
	<rdfs:label xml:lang="en">logo</rdfs:label>
	<rdfs:label xml:lang="fr">logo</rdfs:label>
	</owl:DatatypeProperty>

It's still missing in the Connector though.

[lecoqlibre]

@mkllnk I've pushed the implementation in the next branch of the data-model-uml repo (commit).

Could you try it?

[mkllnk]

Yes, perfect.

[mkllnk]

Our enterprises also have a promo_image which is a wider banner at the top of the "about us" page. Would it be possible to include that as well?

[lecoqlibre]

The logo is present on Agent so on Enterprise and Person too.

I guess we could use the logo property of Person to store the profile picture although this is not the same meaning as 'logo'. Perhaps 'picture' would be more accurate?

About the promo_image of @mkllnk I think we could have an image property on Agent?

Another solution would be to have an image taxonomy containing things like (profile, logo, banner, etc). This taxonomy would be applied to any image property. This way, the standard can define new image types without changing the ontology which would give more flexibility.

What do you think @Alcoz?

[mkllnk]

If you go down the path of creating a taxonomy then it could be useful to add some metadata like size of the image, content type, label. That would help the client to choose the right size to display, for example with <img sizes="..." srcset="..."/>.

[mkllnk]

And maybe there's existing work already? Maybe another standard we can use?

[lecoqlibre]

Yes good idea to have a size and content type @mkllnk. Could you provide some examples of values these properties could hold?

If a standard exists we should align with it. We definitely need @Alcoz on this.

[mkllnk]

Content type would be MIME types. Our app currently has these values:

 "image/svg+xml",                                                                                                                      
 "image/png",                                                                                                                          
 "image/webp",                                                                                                                         
 "image/gif",                                                                                                                          
 "image/jpeg",                                                                                                                         
 "image/tiff",                                                                                                                         
 "image/bmp"]                                                                                                                          

The dimensions are most commonly expressed as width and height in pixels. That can be translated to HTML srcset values.