74
5 Applications of the Metadata Standards
process. Moreover, it cannot be ensured at the syntax level that only information on the
scenario is included. Instead, JavaScript Object Notation (JSON) is often preferred,
particularly in its JSON Linked Data (JSON-LD) variety which was specifically
designed for the purpose of exchanging semantically characterized information on
objects and their relations. In JSON-LD format, the example scenario becomes
{
"@context": {
"ccso": "https://w3id.org/ccso/ccso#",
"ical": "https://www.w3.org/2002/12/cal/icaltzd#",
"otras": "https://purl.vimmp.eu/semantics/otras/otras.ttl#",
"swimm": "https://purl.vimmp.eu/semantics/example/swimm.ttl#",
"vico": "https://purl.vimmp.eu/semantics/vico/vico.ttl#",
"xs": "http://www.w3.org/2001/XMLSchema#"
},
"@id": "swimm:SUMMER_SCHOOL",
"@type": "otras:course",
"ccso:csName": "CECAM SWiMM 2021",
"otras:has_syllabus": {
"@id": "swimm:COURSE_SYLLABUS",
"@type": "otras:syllabus",
"ccso:hasInstructor": {
"@id": "swimm:INSTRUCTOR",
"@type": "otras:instructor",
"vico:has_first_name": "Jean-Pierre",
"vico:has_last_name": "Minier"
}
},
"otras:has_training_unit": {
"@id": "swimm:TRAINING_UNIT_1",
"@type": "otras:training_unit",
"ccso:csName": "Salome/YACS",
"otras:has_event": {
"@id": "swimm:EVENT_1",
"@type": "ccso:TeachingEvent",
"ical:location": "CECAM, EPFL, 2 Avenue Forel, Lausanne",
"ical:dtstart": "2020-03-15T14:40:00+01:00",
"ical:dtend": "2020-03-15T17:40:00+01:00"
}
}
}
There, every pair of curly braces encloses the description of an object (except the
value of @context, which includes the IRI prefix definitions), given as a sequence
of key-value pairs. The individual names are provided as values corresponding to
the key @id, while the instantiated concept names are indicated by the key @type.
The other keys are relation names, and the associated values are the third elements
of the respective triples, as can be seen from the direct correspondence between the
TTL and JSON-LD examples given above.
Additionally, domain-specific solutions on the basis of the hierarchical data format
HDF5 facilitate combining a greater volume of data, including binary data, with the
5 Applications of the Metadata Standards
process. Moreover, it cannot be ensured at the syntax level that only information on the
scenario is included. Instead, JavaScript Object Notation (JSON) is often preferred,
particularly in its JSON Linked Data (JSON-LD) variety which was specifically
designed for the purpose of exchanging semantically characterized information on
objects and their relations. In JSON-LD format, the example scenario becomes
{
"@context": {
"ccso": "https://w3id.org/ccso/ccso#",
"ical": "https://www.w3.org/2002/12/cal/icaltzd#",
"otras": "https://purl.vimmp.eu/semantics/otras/otras.ttl#",
"swimm": "https://purl.vimmp.eu/semantics/example/swimm.ttl#",
"vico": "https://purl.vimmp.eu/semantics/vico/vico.ttl#",
"xs": "http://www.w3.org/2001/XMLSchema#"
},
"@id": "swimm:SUMMER_SCHOOL",
"@type": "otras:course",
"ccso:csName": "CECAM SWiMM 2021",
"otras:has_syllabus": {
"@id": "swimm:COURSE_SYLLABUS",
"@type": "otras:syllabus",
"ccso:hasInstructor": {
"@id": "swimm:INSTRUCTOR",
"@type": "otras:instructor",
"vico:has_first_name": "Jean-Pierre",
"vico:has_last_name": "Minier"
}
},
"otras:has_training_unit": {
"@id": "swimm:TRAINING_UNIT_1",
"@type": "otras:training_unit",
"ccso:csName": "Salome/YACS",
"otras:has_event": {
"@id": "swimm:EVENT_1",
"@type": "ccso:TeachingEvent",
"ical:location": "CECAM, EPFL, 2 Avenue Forel, Lausanne",
"ical:dtstart": "2020-03-15T14:40:00+01:00",
"ical:dtend": "2020-03-15T17:40:00+01:00"
}
}
}
There, every pair of curly braces encloses the description of an object (except the
value of @context, which includes the IRI prefix definitions), given as a sequence
of key-value pairs. The individual names are provided as values corresponding to
the key @id, while the instantiated concept names are indicated by the key @type.
The other keys are relation names, and the associated values are the third elements
of the respective triples, as can be seen from the direct correspondence between the
TTL and JSON-LD examples given above.
Additionally, domain-specific solutions on the basis of the hierarchical data format
HDF5 facilitate combining a greater volume of data, including binary data, with the