Devise URL strategy for CLARIAH services

[mmisworking]

url strategy for service dev different kind of stages.
which url will we use for the upcoming years
Who is able to decide
Who can we request for comments

[jblom]

@mmisworking to be able to have a URL strategy it's nice to know what services we are talking about. I'd say a first list of services is:

• Dataset registry
• Tool registry
• Vocabulary registry?
• Annotations service (elucidate)
• Jupyter Hub
• A bunch of SPAQRL endpoints?
• Couple of generic DANE sandbox environments (e.g. DANE ASR, DANE keyframe extraction, DANE shot detection...)
• more...

Also there might be some services, which are only for internal use (VPN access), they should have a different domain name (or subdomain of xyz).

And the of course we should decide which services need a DEV, TEST or ACCEPTANCE environment.

[roelandordelman]

Sounds like a topic for the Tech Board?

[proycon]

We are the Tech Board aren't we? That's why we raise it here ;)

I don't think we need to in detail plan the full URLs of all services, but we do need to agree on things like putting everything under $appname.clariah.nl and indeed on some kind of distinction between environment like @jblom suggested, like dev.$appname.clariah.nl for dev environments. It may also be worth agreeing on what potentially ambiguous or high-value names like annotation.clariah.nl are tied to.

I'm already going on the assumption that we use clariah.nl as main domain (seems logical to me), but of course that too is debatable and we may have to take the successor project into consideration

[roelandordelman]

I mean the formal route: as a Tech Board we should formulate a proposal to have it approved and/or amended by the CLARIAH board and other stakeholders.

[mmisworking]

@roelandordelman is something decided during the TC meeting?

[roelandordelman]

@mmisworking During the Tech Day we briefly discussed that the URL strategy is important, also wrt clusters running elsewhere and being part of the C-infra. If we could have a proposal ready based on the above on 07/03, we can have it discussed in the board meeting of March.