Fwd: [learningreg-dev] Illinois publishing using JSON-LD

16 views
Skip to first unread message

Joshua Marks

unread,
Feb 22, 2016, 2:08:56 PM2/22/16
to lr...@googlegroups.com
Cross posting to LRMI group.

-Joshua
---------- Forwarded message ----------
From: Jerome Grimmer <jgri...@siuccwd.com>
Date: Mon, Feb 22, 2016 at 9:07 AM
Subject: [learningreg-dev] Illinois publishing using JSON-LD
To: "learnin...@googlegroups.com" <learnin...@googlegroups.com>


All,

Late last week, Illinois switched over to publishing resources using JSON-LD instead of the older, but equally valid microdata+json format.  Our subjects and career clusters are now published as educational alignments; educationalRole is now a property of audience, which we’ve overridden so that instead of using schema.org’s Audience type, we’re using their EducationalAudience type; our group types are published using the audienceType of EducationalAudience; grade levels are now published as educational alignments with an alignment type of “educationLevel”, we publish licensing information using both schema.org’s license property and LRMI’s useRightsUrl property; this should satisfy those who are using strict schema.org as well as those who are using strict LRMI; and finally, our “assessment types” have been merged with learning resource type.

 

This leaves three properties which we use and couldn’t find and equivalent for in schema.org:

1.       Requires from DC,

2.       mediaType (this is DC’s “format” property – an older version of LRMI called it mediaType), and

3.       accessRights from DC.

 

This makes our @context block and type property look like this:

 

"@context": {

  "@vocab":"http://schema.org/",

  "requires":"http://purl.org/dc/terms/requires",

  "mediaType":"http://purl.org/dc/terms/format",

  "accessRights":"http://purl.org/dc/terms/AccessRights",

  "useRightsUrl":"http://purl.org/dcx/lrmi-terms/#useRightsUrl",

  "audience":{

    "@id":"audience",

    "@type":"EducationalAudience"

  }

},

"@type":"CreativeWork"

 

These changes more closely follow the standards, and hopefully will make it easier for people to consume our stuff.

Jerome Grimmer

Southern Illinois University Carbondale

2450 Foundation Drive Suite 100

Springfield, IL

Phone: 217-786-3010 ext. 5857

Toll-free: 1-800-252-4822 ext. 5857

NOTE: My E-mail address has changed

jgri...@siuccwd.com

This email sent using 100% recycled electrons.

 

--
You received this message because you are subscribed to the Google Groups "Learning Registry Developers List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to learningreg-d...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Dan Brickley

unread,
Feb 23, 2016, 5:02:13 AM2/23/16
to lr...@googlegroups.com, jgri...@siuccwd.com
Just a quick aside:
In schema.org's JSON-LD context definition we define a lot of common RDF namespace prefixes, based on those at https://www.w3.org/2011/rdfa-context/rdfa-1.1 including
        "dc": "http://purl.org/dc/terms/",
this should make it easier to draw upon Dublin Core terms e.g. dc:accessRights expanding to http://purl.org/dc/terms/accessRights

I haven't double-checked that these short names also work for types/classes but thought this might be of use in some circumstances.

cheers,

Dan

You received this message because you are subscribed to the Google Groups "Learning Resource Metadata Initiative" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lrmi+uns...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages