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

Oke #314

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Oke #314

wants to merge 12 commits into from

Conversation

hamrt
Copy link
Contributor

@hamrt hamrt commented Sep 11, 2024

All updates made to the specification based on the requirements for the OKE project.
All changes are documented in the changelog.md

Copy link
Contributor

@jelmerderonde jelmerderonde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hamrt thanks for all the hard work!

It is a big PR to review, so we might have to do this in changes. Or merge quite soon to a v6.0-dev folder as discussed and continue finetuning there.

This review is my first pass on all the changes. I might have to do another after we've talked some more about some of the design choices which I don't always understand fully.

Let's meet soon to discuss my review and figure out what to change and what to keep as-is.

@@ -0,0 +1,3 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deze file hoort wat mij betreft niet thuis in de spec. Je zou wel de .vscode folder aan .gitigignore kunnen toevoegen?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

eens

CHANGELOG.md Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ik denk dat we, naast de changelog, ook nog een wat verhalender tekstje moeten toevoegen wat samenvat wat al deze changes "verbind".

- denied
- associated
- queued
- finished
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding finished to the possible states of an association seems to conflate two things:

  • The state of the association
  • The state of the offering

The student remains associated with the offering, even when the offering is finished. I would suggest that this enumeration not be changed and to introduce a different mechanism for tracking the finished/unfinished state.

Some more explanation about what exactly finished means would also be welcome.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The offering itself is not finished the student is finished with his or her exam, meaning the assocaition has reached a ststus where a resutl can be expected, or where a situation where nog result but a not present or other situation has occurred, indicating a change in the status of the association it self. This additional information could be provided

- part-time
- dual training
- self-paced
- extraneous
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The modeOfStudy attribute describes the education, not the way of participation by a student. Why was this added here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NO it describes the type of study, the person can only enroll for an exam in this case there are no other modes of study available for the student

- denied
- associated
- queued
- finished
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also see my comment for associationState

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see earlier feedback

summary: PUT /offerings/{offeringId}
description: |
PUT / create an offering or update a single offering based on the offeringID provided.
You want to PUT a resource to the same URI you intend to GET it from. also check RFC 72314.3.4 PUT.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RFC7231 is obsoleted by RFC9110.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don' really understand yet how all these ComponentOfferingAssoications***.yaml files work together and why all are needed. Let's look at that together soon.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, lets plan

description: The first day this EducationSpecification is valid (inclusive).
type: string
format: date
example: 2024-12-15T08:50:00+01:00
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See other comments about date-time

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that is a valid remark, I am curious though how this is implemented. Maybe we should also check how the spec is implemented.

description: The day this EducationSpecification ceases to be valid (e.g. exclusive).
type: string
format: date
example: 2025-12-15T08:50:00+01:00
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See other comments about date-time

v5.1/spec.yaml Outdated
$ref: paths/DocumentInstance.yaml
/associations/{associationId}:
$ref: paths/AssociationInstance.yaml
/associations/{associationId}/url:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need this one

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

Successfully merging this pull request may close these issues.

2 participants