Defining a standard JSON-based exchange format for learning metadata Manon Haartsen.
9
Defining a standard JSON-based exchange format for learning metadata Manon Haartsen
-
Upload
lander-claessens -
Category
Documents
-
view
215 -
download
0
Transcript of Defining a standard JSON-based exchange format for learning metadata Manon Haartsen.
Defining a standard JSON-based exchange format for learning metadataManon Haartsen
Topics
• Json: what and why?
• Json and learning metadata
• Towards a standard Json exchange format
Json: what and why
JSON = JavaScript Object Notation
• Open standard format that uses human-readable text
to transmit data objects consisting of key:value pairs.
• It is used primarily to transmit data between a server and web
application, as an alternative to XML.
• Although originally derived from the JavaScript scripting language,
JSON is a language-independent data format, and code for parsing
and generating JSON data is readily available in a large variety of
programming languages.
Json and learning metadata
title: "Havo/vwo Examen Aardrijkskunde",
description: "De infoblokken, beeldbankclips en de
quiz op deze pagina zijn samengesteld voor het
examen aardrijkskunde voor havo/vwo 2013. Je
kunt ze gebruiken om je kennis van de
verschillende onderwerpen te testen. ",
keyword:
["eigenwijzer",
"aardrijkskunde",
"toetsen",
"informatie"
],
language:
["nl"
],
<czp:title><czp:langstring xml:lang="nl">Havo/vwo Examen Aardrijkskunde </czp:langstring>
</czp:title>
<czp:catalogentry><czp:catalog>MMBase Teleac
</czp:catalog>
<czp:entry><czp:langstring xml:lang="x-none">2825030
</czp:langstring>
</czp:entry>
</czp:catalogentry>
<czp:language>nl
</czp:language>
<czp:description><czp:langstring xml:lang="nl">De infoblokken, beeldbankclips en de quiz op deze pagina zijn samengesteld voor het examen aardrijkskunde voor havo/vwo 2013. Je kunt ze gebruiken om je kennis van de verschillende onderwerpen te testen.
</czp:langstring>
</czp:description>
<czp:keyword><czp:langstring xml:lang="nl">eigenwijzer
</czp:langstring>
</czp:keyword>
<czp:keyword><czp:langstring xml:lang="nl">aardrijkskunde
</czp:langstring>
And some more…
XSD
Used labels so farTitle
Description
Keyword / keywords
Coverage
Language
Aggregationlevel
Publisher (name, datetime, timestamp)
Author (name, datetime, timestamp, location)
Contributors (organization, role)
CreationDate
Status
Duration
Time
Format
Learningresourcetype / LearningResourceTypes
Intendedenduserrole / endUserRoles
Context / contexts
TaxonPaths
Typicalagerange
Typicallearningtime
Cost
Rights
Competency
Rights
Competency
Discipline
Educational level
Educational objective
Doctype
Embed
Thumbnail / generateThumbnail
Icon
Previewimage
startRecord
maximumRecords
EducationalLevels
Drilldowns
Records
Identifier
Config
Status
Caching
Search
tokenBlock
languageBlocks
Making it easier to build a search frontend
time:
{seconds: 1200,
human: “20 minutes"}
discipline:
{c001f86a-4f8f-4420-bd78-381c615ecedc: “Geography"}
cost: “Free“
accessrights: "Via login system Entree"
Human readable duration / time
Default caption
Interpreted for the end user
Making it easier to build a search frontend
mapped_format: "Afbeelding",
mapped_format_specific: "JPEG afbeelding",
mime_icon: "http://widget.edurep.nl/icon/mimetypes/openworld
/48/image/jpeg.png"
Aggregation of mime-type, with choice of depth
Added as a service
Towards a standard Json format
Comparison of existing JSON outputs
(Kennisnet, AgroKnow, others?)
Proposed example-binding
Standardization process within Ariadne…
Or will examplification be enough?
Any questions?
Manon Haartsen – product manager Edurep
e-mail: [email protected]
twitter: @edurep
Kennisnet.nl
twitter: @kennisnet
