Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: How to indicate, show service licences? #125

Open
khawkins98 opened this issue Feb 28, 2018 · 0 comments
Open

Discussion: How to indicate, show service licences? #125

khawkins98 opened this issue Feb 28, 2018 · 0 comments
Labels

Comments

@khawkins98
Copy link
Contributor

khawkins98 commented Feb 28, 2018

There's a discussion happening in the Web Content Committee and within EMBL-EBI about:

  1. What licences are used by EMBL-EBI services; and
  2. How should we consistently indicate and present these.

Part 2 fits within the remit of the Web Guidelines Committee and the EBI Visual Framework. So, how can we best facilitate that?

After a little thinking, here's an idea that's held up:

  1. Indicate the licence with a meta tag:
    • <meta name="ebi:licence" content="cc-by-sa-4_0">
    • <meta name="ebi:licence-link" content="https://link-to-serivce-licence-info-page"> (optional)
  2. That can be machine read and be consumed by the EBI Visual Framework so it can be programatically injected in the footer:
    • image

We should also decide if this goes in the local footer or global.
A. Should the licence information stick together, or
B. should we maintain the page structure.

A probably makes more sense to users, B probably makes more sense internally.

We'll need to bubble up this to the page structure information at http://wwwdev.ebi.ac.uk/style-lab/websites/meta-patterns/page-structure.html

khawkins98 added a commit that referenced this issue Nov 20, 2019
.gitignore `!` flags are unreliable.

For #125
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant