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

Identifying different link usages #1947

Open
egekorkan opened this issue Dec 21, 2023 · 1 comment
Open

Identifying different link usages #1947

egekorkan opened this issue Dec 21, 2023 · 1 comment
Labels
Has Use Case Potential The use case can be extracted and explained Needs discussion more discussion is needed before getting to a solution Semantics Semantics-related issues

Comments

@egekorkan
Copy link
Contributor

We are seeing that link has two different usages from TD designers:

  1. Basic linking: linking to the UI, pdf, alternative representation, icon
  2. "Semantic" linking: collection, controlledBy, tm:extends

This is annoying for TD consumers since they need to handle two styles very differently. If I am building a graph of related Things, I cannot blindly parse through the links.

Since these two different mechanisms, I think we can discuss splitting those.

@github-actions github-actions bot added the needs-triage Automatically added to new issues. TF should triage them with proper labels label Dec 21, 2023
@egekorkan egekorkan added Needs discussion more discussion is needed before getting to a solution Semantics Semantics-related issues and removed needs-triage Automatically added to new issues. TF should triage them with proper labels labels Dec 21, 2023
@benfrancis
Copy link
Member

This is not dissimilar to how HTML uses <link> tags. They may be used to link to other HTML documents (e.g. <link rel="next"> and <link rel="canonical">), to alternate representations of an HTML document (e.g. <link rel="alternate">) or to related non-HTML resources (e.g. <link rel="icon">, <link rel="manifest">, <link rel="stylesheet">).

Is there a reason that a Consumer can not use the rel and type members to distinguish between different types of links, like those described in section 5.6.2 of WoT Profile? Did you have an alternative solution in mind?

@egekorkan egekorkan added the Has Use Case Potential The use case can be extracted and explained label Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Has Use Case Potential The use case can be extracted and explained Needs discussion more discussion is needed before getting to a solution Semantics Semantics-related issues
Projects
None yet
Development

No branches or pull requests

2 participants