-
Notifications
You must be signed in to change notification settings - Fork 13
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
Update examples embedded in spec #163
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Warum ist hier
type
mit angegeben, beieducationalLevel
aber nicht?Ist beides korrekt, da
type
bei beiden Attributen angegeben werden KANN.(trifft auch auch
highered-course-part.json
zu.Frage mich, ob das eher verwirrt, wenn in den Beispielen mal so oder so mit optionalen Werten umgegangen wird oder die Beispiele möglichst vollständig sein sollten
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ich würde das auch ohne
type
machen. Habe das auch im OERSI ohnetype
umgesetzt.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In der genannten Datei steht
"type": [ "Concept" ]
auch beiabout
undaudience
.Da es im Schema explizit genannt wird, aber nicht
required
ist, finde ich es schon sinnvoll, wenn es in einigen – aber eben nicht allen – Beispielen auftaucht. Wenn, dann sollten wir das auch komplett aus dem Schema tilgen, womit ich d'accord wäre. Die genannten Informationen finden sich ja ohnehin im RDF, wenn die URI dereferenziert wird. Ich schlage vor, das hier erstmal zu mergen und die Frage in einem gesonderten Ticket zu diskutieren.