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

NEDS-202: Add TRADEMARK.md #88

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from
Open

NEDS-202: Add TRADEMARK.md #88

wants to merge 3 commits into from

Conversation

diemartin
Copy link
Contributor

No description provided.

5. Open-source license vs trademarks. The open-source EUPL-1.2 License allows you to redistribute and use the software
under certain conditions. Nevertheless, the EUPL-1.2 License does not include an implied right or license to use a
trademark related to the licensed software or other materials. The trademarks and logos need to be used consistent
with trademark law.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Subpoint 6 is missing - it should be:

  1. The Harmony eDelivery Access documentation is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.

TRADEMARK.md Outdated
product or service so long as such use is not likely to cause unnecessary consumer or public confusion (e.g.,
untruthful advertising, false/misleading promotional materials, etc.).
3. The following are two common types of fair use:
1. When you are specifically referring to NIIS products, for example, Harmony eDelivery Access® Access Point
Copy link
Contributor

@petkivim petkivim Jan 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Harmony trademark is registered for NIIS:

  1. When you are specifically referring to NIIS products, for example, Harmony eDelivery Access® software is used in company XYZ for data exchange. Harmony eDelivery Access® is a registered trademark of NIIS.

1. When you are specifically referring to NIIS products, for example, Harmony eDelivery Access® Access Point
software is used in company XYZ for data exchange. Harmony eDelivery Access® is a registered trademark of the
Estonian Information System Authority.
2. When you indicate that a NIIS product is compatible with another product, for example, XYZ product is compatible
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also here, the Harmony trademark is registered for NIIS.

TRADEMARK.md Outdated
Comment on lines 121 to 122
1. **Question**: Does this also mean that if I, for example, compile Harmony eDelivery Access® Access Point (without changing any actual code) and create my metapackages to distribute in a country, for instance, I should always modify the frontend code and remove the Harmony eDelivery Access logos?
1. **Answer**: In this case, you don’t need to remove the Harmony eDelivery Access logos from the frontend because you’re still using the original Harmony eDelivery Access software. However, the national data exchange service that’s built using Harmony eDelivery Access should be called something else.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This example is very X-Road specific and therefore, it's better to change it. For example, we could use this instead:

  1. Question: Does this also mean that if I, for example, compile Harmony eDelivery Access® Access Point including my own changes to the source code and publish a modified version of the software for distribution, for instance, I should modify the frontend code and remove the Harmony eDelivery Access logos?
    1. Answer: In this case, you need to remove the Harmony eDelivery Access logos from the frontend because you're not using the original Harmony eDelivery Access software anymore.

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

Successfully merging this pull request may close these issues.

2 participants