Re: EOCred: Identify the level of a credential

On 08/02/18 17:38, Stuart Sutton wrote:
> In an earlier message in this thread, I suggested that this 'level' 
> property could be thought of as a characteristic of the audience for 
> the credential. In that sense it aligns with schema.org/audience 
> <http://schema.org/audience> when the aspect of audience is 
> constrained to the education/training/experience level for which the 
> credential is intended or useful. That's the approach the CTDL took 
> with its audienceLevelType 
> <http://credreg.net/ctdl/terms#audienceLevelType> property and 
> accompanying AudienceLevel <http://purl.org/ctdl/terms/AudienceLevel> 
> skos vocabulary (latter perhaps a bit US-centric).

That name seems a bit tricky given the way audience is used in 
schema.org, and the way credentials are intended for people who acquire 
them and people like employers who wish some form of assurance about the 
abilities of those people. Who is the audience for your Driver's License?

I think given previous discussions we would want to take 'Type' off of 
'audienceLevelType'?

We might just be left with 'level' as a name, though that seems a little 
bare.  Whatever it is called, I think it would be equivalent in intent 
with the CTDL:audienceLevelType.

In Europe established practice is to align educational/occupational 
credentials with the educational level associated with the learning 
outcomes required to earn them, much as you would align Courses or 
learning resources to an educational level. For example, there are the 
levels of the European Qualifications Framework 
<http://ecahe.eu/w/index.php/European_Qualifications_Framework#The_levels_in_the_EQF>, 
also the SCQF levels descriptors 
<http://scqf.org.uk/wp-content/uploads/2014/03/SCQF-Level-Descriptors-WEB-Aug-2015.pdf> 
(pdf) [somewhere I think there is a mapping from SCQF to EQF, so that 
people from Italy know what level a Scottish HND is].

>
> On Wed, Feb 7, 2018 at 4:27 AM, Phil Barker <phil.barker@pjjk.co.uk 
> <mailto:phil.barker@pjjk.co.uk>> wrote:
>
>     The next use case I would like to discuss is around identifying
>     the level of an educational / occupational credential currently
>     stated as: it should be possible to search or review results of a
>     search by specific credential level, e.g. post-graduate, High
>     school, entry, intermediate, advanced.
>
>     To do this we need to be able to relate an educational /
>     occupational credential to a description or representation of an
>     educational level. I see two options for this:
>
>     A. we do the same as is currently done for learning resources and
>     courses and use the educationalAlignement
>     <http://schema.org/educationalAlignment>property to point to an
>     AlignmentObject <http://schema.org/AlignmentObject> which in turn
>     points to and/or describes an educational level.
>
>     B. we add a new property educationalLevel which could point to
>     either an AlignmentObject or directly to a DefinedTerm for the
>     educational level.
>
>     I'm interested in anyone's thoughts on which they would prefer.
>
>
>     =A bit of background to the AlignmentObject.=
>
>     - the educationalAlignment / AligmentObject pairing is useful when
>     you don't want to pre-define and thus limit types of alignments
>     involved by having a few properties for specific alignments
>     (that's at the root of why LRMI introduced it, here we have a
>     specific alignment type we know we want.)
>
>     - the AlignmentObject is useful when the thing to which you are
>     aligning is not properly defined a a firstclass schema.org
>     <http://schema.org> object; it allows you to refer to it by
>     description
>
>     - the AlignmentObject is useful when you want to say things about
>     the alignment itself (e.g. describe who asserts the alignment is
>     true and how they came to this judgement) though this ability is
>     under developed and to my knowledge not used
>
>     - research <https://dl.acm.org/citation.cfm?id=3054160>[*] into
>     LRMI schema.org <http://schema.org> markup in the wild suggests
>     that the AlignmentObject (and relatively more complex / abstract
>     approaches in general) are used less frequently than simpler
>     property - value [literal] relationships.
>
>     - the Open Badges spec uses an alignment property to point from a
>     badge class to an AlignmentObject representing objectives or
>     educational standards (which is slightly different to this use
>     case, though we several use cases for aligning to competencies)
>
>
>     Please let me know your thoughts.
>
>     Phil
>
>
>     * open access copy of that paper at
>     https://blogs.pjjk.net/phil/confpaper/analysing-improving-embedded-markup-learning-resources-web/
>     <https://blogs.pjjk.net/phil/confpaper/analysing-improving-embedded-markup-learning-resources-web/>
>
>
>     -- 
>
>     Phil Barker <http://people.pjjk.net/phil>. http://people.pjjk.net/phil
>     PJJK Limited <https://www.pjjk.co.uk>: technology to enhance
>     learning; information systems for education.
>     CETIS LLP: a cooperative consultancy for innovation in education
>     technology.
>
>     PJJK Limited is registered in Scotland as a private limited
>     company, number SC569282.
>     CETIS is a co-operative limited liability partnership, registered
>     in England number OC399090
>
>
>
>
> -- 
> Stuart A. Sutton, Metadata Consultant
> Associate Professor Emeritus, University of Washington
>    Information School
> Email: stuartasutton@gmail.com <mailto:stuartasutton@gmail.com>
> Skype: sasutton
>
>

-- 

Phil Barker <http://people.pjjk.net/phil>. http://people.pjjk.net/phil
PJJK Limited <https://www.pjjk.co.uk>: technology to enhance learning; 
information systems for education.
CETIS LLP: a cooperative consultancy for innovation in education technology.

PJJK Limited is registered in Scotland as a private limited company, 
number SC569282.
CETIS is a co-operative limited liability partnership, registered in 
England number OC399090