issues
search
MellonScholarlyCommunication
/
spec-orchestrator
The implementation requirements for the Ochestrator component.
https://MellonScholarlyCommunication.github.io/spec-orchestrator/
1
stars
3
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
A couple of typo fixes
#20
pietercolpaert
opened
1 year ago
0
Fix some small typos
#19
smessie
closed
1 year ago
0
Explain what happens when a policy can't be executed by the Orchestrator (e.g. due to errors)
#18
phochste
opened
2 years ago
0
Explain HTTP Signature and Linked Data Proof as methods for identify verification
#17
phochste
opened
2 years ago
0
Initialization of the Data Pod
#16
phochste
closed
2 years ago
2
Add tag v0.0.1 for milestone 1
#15
pheyvaer
closed
2 years ago
0
Check which issues need to be resolved for milestone 1
#14
pheyvaer
closed
2 years ago
0
Is SHACL required to in the orchestrator if there is a choice of a rulebook language?
#13
phochste
closed
2 years ago
1
How observe resource state changes in Solid?
#12
phochste
opened
3 years ago
3
How to specify a global schedule trigger ?
#11
mielvds
opened
3 years ago
0
What data pod authorizations does an Orchestrator need?
#10
mielvds
closed
2 years ago
1
Registration of inbox at initialization or in the policy?
#9
mielvds
opened
3 years ago
2
6.1 Make receving Linked Data Notifications in line with the use-case of COAR?
#8
phochste
closed
3 years ago
2
How important is synchronisation of messages?
#7
phochste
opened
3 years ago
0
replace the term Policy by Rulebook to avoid confusion?
#6
mielvds
closed
3 years ago
3
Triggers
#5
Dexagod
closed
3 years ago
0
Adding notify scenario 1
#4
phochste
closed
3 years ago
3
The orchestrator of the data pod can only read inbox + read/append to event log?
#3
phochste
closed
2 years ago
5
Automatic processing of random notifications
#2
Dexagod
opened
3 years ago
5
Inbox link on initialization
#1
Dexagod
closed
3 years ago
1