-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create non-functional-requirements.md
- Loading branch information
1 parent
e096e95
commit 46d9303
Showing
1 changed file
with
15 additions
and
0 deletions.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# Non-functional requirements | ||
|
||
Metadata can come in many different flavors and therefore should allow to be used in multiple contexts. | ||
|
||
## 1) Supported serialization formats | ||
|
||
In general, metadata in a RDF format is preferred since it enables it to be stored in triple store databases. | ||
This means the preferred serialization formats are RDF/XML, JSON-LD, Turtle, N3 and Ntriples. | ||
|
||
|
||
Nevertheless, other standardized formats as XML, JSON, YAML and TOML are also valid and can be used. | ||
|
||
## 2) Provided schema files | ||
|
||
Schema files shall be provided as Turtle/Notation3 and as JSON schema. Both for standard JSON and JSON-LD?! |