Add a logo property

[linkmauve]

Fixes #40.

[kjetilk]

Looks good to me!

Now, we need a process to get it into the namespace document.

[linkmauve]

You mean take this change once it is merged and publish it at http://usefulinc.com/ns/doap#?

[kjetilk]

You mean take this change once it is merged and publish it at http://usefulinc.com/ns/doap#?

Yeah, currently, we don't have any automated means for that, so it depends on @ewilderj 's time.

[linkmauve]

Hi @ewilderj, any news on that?

[ewilderj]

I like the notion of this -- can you speak to the range of Container? I think the most expected thing would be for someone to reference an image file, or a list of image files. This PR would be best if it also incorporated an amended example to show usage?

[ewilderj]

I'm wondering about pursuing this in the same category as the #50 screenshot property. I don't think the range of sioc:Container is appropriate, given my reading of http://rdfs.org/sioc/spec/#term_Container -- however no objection to the property name, so it makes sense. I think we can usefully use terms from https://github.com/facebookarchive/open-graph-protocol/blob/master/ns/ogp.me.rdf

Unapproving so we can have the discussion about the range

[kjetilk]

Yes, sioc:Container may not be appropriate. There's foaf:Image, of course.

[Claudenw]

In practice many of the Apache projects have multiple logo files representing different sizes and formats. Would this link then work by the container then having multiple arbitrary image objects within the container?

[kjetilk]

Perhaps the best thing would be to have a range of a thing that may have properties of sizes and formats? https://schema.org/ImageObject , perhaps?`

So that you would simply have multiple doap:logo properties for different versions?