Skip to content

Resolve ambiguity on how to handle attributes #259

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.

Sign up for GitHub

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

Open
Silvanoc wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Resolve ambiguity on how to handle attributes #259

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions linkml_model/model/schema/meta.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1231,11 +1231,11 @@ slots:
multivalued: true
range: slot_definition
inlined: true
description: Inline definition of slots
description: Inline definition of class-scoped slots
comments:
- >-
attributes are an alternative way of defining new slots. An attribute adds a slot to the global space in the
form <class_name>__<slot_name> (lower case, double underscores). Attributes can be specialized via slot_usage.
Attributes are an alternative way of defining class-specific slots.
They are equivalent to slots that are only available within the scope of class and its descendants.
in_subset:
- SpecificationSubset
- MinimalSubset
Expand Down
Loading