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

Allow linking concepts to external resources #140

Open
strogonoff opened this issue Sep 11, 2020 · 7 comments
Open

Allow linking concepts to external resources #140

strogonoff opened this issue Sep 11, 2020 · 7 comments
Labels
enhancement New feature or request

Comments

@strogonoff
Copy link
Contributor

Requirements (as discussed with @ronaldtse)

  • It is OK to restrict external resources to URIs only
  • This feature may use same (or similar) relationship types as in normal (internal) relationships
  • Fetch any structured data from the URI is not in scope for now

We may or may not use the Relationships panel for this.

I believe we should restrict the Relationships panel to Glossarist-managed concepts only, and generic external resources should be implemented on another level.

@strogonoff strogonoff added the enhancement New feature or request label Sep 11, 2020
@strogonoff
Copy link
Contributor Author

@ronaldtse is an external linked resource specific to a language-specific entry, or to concept as a whole? Can it be that English entry refers to some external resources, and Spanish entry refers to other resources?

@ronaldtse
Copy link
Member

@strogonoff good call. If we talk about SKOS, it is only about concept relationships. However, when we talk about designations and definitions, they can have other types of relationships (e.g. ISO authoritative source of definition). Can we list them out?

@strogonoff
Copy link
Contributor Author

strogonoff commented Sep 14, 2020

Per discussion outside Github, we might (for now) support external relationships on both levels, for top-level meaning units and for localized concept entries.

In future we will have top-level concepts and each language’s concept entries reside in their own registers, in which case we can have generic relationships on any concept item in concept register.

(NB: I believe designations are not supposed to have relationships at all. Concepts refer to units of meaning, while designations describe grammatical properties of words used to refer to concepts.

If it has something to do with meaning it can have relationships, but if it’s a description of a verbal/non-verbal designation I’m not sure it can refer to things🤔

Although there may be space for allowing to refer to resources as justifications/prior art for choosing a particular word as designation (?))

@strogonoff
Copy link
Contributor Author

strogonoff commented Sep 14, 2020

@ronaldtse do you think external references may be used for clarifying e.g. why a certain word was chosen to designate a certain concept? I wonder if there any examples like that in our existing concept systems

If those exist, we might want to support external relationships for designations as well

@strogonoff
Copy link
Contributor Author

Up until now, relationships are supposed to only be pertaining to definitions/meaning, not designations

@ronaldtse
Copy link
Member

(NB: I believe designations are not supposed to have relationships at all. Concepts refer to units of meaning, while designations describe grammatical properties of words used to refer to concepts.

I wonder if designations should be allowed to have relationships with other designations. i.e. this "designation comes from this external source".

@ronaldtse
Copy link
Member

We should first allow linking of concepts and the consider designations. The former is critical for the importing of SKOS #127 .

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

No branches or pull requests

2 participants