Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
saref4wear
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
SAREF
saref4wear
Repository
562cd3ed481e18af1317dd5e33dc728c97e6b4c7
Select Git revision
Branches
13
develop-v2.1.1
default
protected
release-v1.1.1
protected
prerelease-v1.1.1
protected
develop-v1.1.1
protected
issue-2
issue-22
issue-15
fix-DP-list
issue-11
issue-12
issue-10
33-promotion-of-triggers-and-istriggeredby
31-delete-s4wear-hascommand
13 results
saref4wear
ontology
saref4wear.ttl
Find file
Blame
Permalink
4 years ago
562cd3ed
Now the user of a wearable can be any feature of interest.
· 562cd3ed
Raul Garcia-Castro
authored
4 years ago
Closes
#18
.
562cd3ed
History
Now the user of a wearable can be any feature of interest.
Raul Garcia-Castro
authored
4 years ago
Closes
#18
.
Code owners
Assign users and groups as approvers for specific file changes.
Learn more.
