could we rename the package to all lowercase?

[maelle]

@salvafern Any thought? Lowercase is easier to type. Now is a good time to rename the package (as opposed to after a first CRAN release for instance)

https://devguide.ropensci.org/pkg_building.html#naming-your-package

[maelle]

@salvafern said yes

[maelle]

I am having second thoughts! "emodnetwfs" is probably not great for screen-reader users. What about "emodnetWFS"? or "emodnetfeatures"? Who else could we ask for a third opinion?

[maelle]

emodfeat

[maelle]

what I have no doubt about is that the current name is hard to type.

[maelle]

maybe emodnet.wfs since we'd have emodnet.wcs

[maelle]

emodnet.features

[maelle]

maybe even better would be an acronym

[maelle]

pufferfish = has P like package, f like feature, e like emodnet, s like service. and it inflates the amount of data you have.

[maelle]

starfish in honor of the EU flag

[maelle]

I still think we should get an opinion from others. A name related to the ocean, with a paired name for EMODnetWCS would be really nice.

[maelle]

or a boat name starting with f for WFS, one starting with c for WCS.

https://en.wikipedia.org/wiki/Category:Boat_types

[maelle]

• ferry (feature service for emodnet, in R)
• coble (coverage service for emodnet)

[maelle]

althought it might seem insulting than one of those boats is clearly smaller.

[maelle]

@salvafern thoughts?

[JoBeja]

Hey, I think that it would be good to clearly identify the packages as EMODnet... If I have any ideas I'll put them through

[salvafern]

Love the brainstrom :)

As a simple solution I would choose emodnetwfs: easy to write, remember, straight to the point.. and indeed no upper case. Not a big fan of those myself.

Or something that reflects that one serves vector and the other raster

I will drop more creative ideas as they come

[maelle]

@JoBeja that's a good point. Now, could it be enough to state this clearly in the documentation and metadata?

The problem with emodnetwfs is that it could at first look hard to pronounce and remember.

[JoBeja]

@maelle no I don't think it is enough. As I see it, it's mainly a matter of branding. I think our R packages don't have a lot of visibility and using a name that immediately identifies them as EMODnet is important.
Acronym pronounciation varies across the globe, some countries read each letter separately, others read it as if it was a word, we're not going to please everyone, whatever choice we make.

[maelle]

then what about emodnet.wfs? I don't like dotted names in general but I'd find that easier to remember than EMODnetWFS.

[salvafern]

Since a new gen of ogc services is coming and they seem to partially drop the WCS, WFS etc for OGC API - Coverages or Features, how about naming the package closer to these?

e.g. emodnetfeat, emodnetfeatures

likewise emodnetcov, emodnetcoverages etc

See https://ogcapi.ogc.org/#standards

[maelle]

👋 @here! I'm happy to go with whatever you two find the most appropriate for the project itself and for most likely users.

I'd like to submit the package in August after my summer vacation (the week of the 19th for instance). Could you two get back to me before then?

[JoBeja]

Hi,
As long as emodnet is in the package name, I don't mind whether it's wcs/wfs or features/coverages. You have more expertise on this than I do, so please go ahead with the option you think is best and written in the way you think is best too.

[maelle]

Thanks @JoBeja!

@salvafern what about emodnet.wcs or emodnet.features? Dotted names might not be the best in general but there's for instance aws.s3 and friends.

[bart-v]

I vote emodnetogc, then we can still use WFS, and move to OGC API whenever needed

[JoBeja]

@bart-v they are two packages which work independently, we need two names. Do you have a suggestion?

[bart-v]

Which 2 packages?

[JoBeja]

EMODnetWCS and EMODnet WFS

[maelle]

so they could be

• emodnet.wfs and emodnet.wcs
• emodnet.features and emodnet.coverage
• other propositions welcome

what I feel strongly about is not having a "complicated" lower-case/upper-case mix.

[maelle]

@annakrystalli tagging you too 😸

[annakrystalli]

No objection from me to shifting to all lowercase.

I prefer emodnet.wfs and
emodnet.wcs but would also be happy with emodnetwfs and emodnetwcs. Excited to see both on CRAN soon!! 😃

[maelle]

@annakrystalli let's get them through software-review first 😉

[bart-v]

Sorry Jo, OK, clear now.
I think the dots are better for search indexing and readability.
So I agree with emodnet.wfs and emodnet.wcs.

[salvafern]

Let's go with the dotted version? emodnet.wfs and emodnet.wcs

[maelle]

ok let's go for this one!