View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
what InLOC is● a model for representing and communicatinginformation about structures of learningoutcomes, competence, competencies, etc.– skills frameworks– occupational competence standards– professional development (etc.)● domain independent (“content”-free)● hasnt been done successfully before
why is InLOC significant?● adds value to work such as the European e-Competence Framework(e-CF) and many other skills frameworks, competence standards,structured sets of learning outcomes, etc.● provides a sound basis for genuinely useful technologies– putting together: skills frameworks and standards; e-portfolio tools; learning,education and training tools and systems; HR, recruitment and employmentservices; learning resources, towards new tools and services– communicating LOC structures – if public, expose to open search and query,with the components able to be reused and remixed– prompting people to assign identifiers (URLs, IRIs) to their LOC conceptdefinitions to enable linked data for the Semantic Web● thats the kind of reason why people in ITLET have been asking forthis kind of thing for several years
we have provided key solutions●we worked hard analysing stakeholder needs and sources● we are presenting three draft CWAs for potential standardization1.an Information Model that offers a coherent, genuine solution to how to representthis kind of structure2.Guidelines that explain both the model itself, and its application to widerEuropean Learner Mobility3.some Application Profile work, relevant to Europass●and a report, not yet for standardization, on bindings of that model– an XML binding, which people seem most interested in to start with– an RDF binding, which hold much promise for the future– a JSON binding, for easy communication between web tools
and done extra work on top● creating two prototype demonstration applications to workwith InLOC structures● these demonstrate that there are no problems translating themodel into a relational (or other) database and using it todrive web applications, that in turn will help towards theadoption of the model● creating transforms to convert between bindings● integrated our requirements with the Workshops ELMOproject, which takes forward EN15981 and EN15982towards practical implementation.
what is hard about this, and,what have we done about it?a little philosophical reflection …● different people simplify things in their own way●a realistic common model may look complex or abstract● weve chosen to make the model simple, accepting some abstraction– to help developers and implementers get into it most easily (they canmanage fine with abstraction)– they then produce the user tools that will make things easy tounderstand for the domain practitioners (who want their own languages)●you are unlikely to see anything else this simple that covers the ground –most models have to be broken into several pages
the modelin UML,for thepresent(this isreallysimple!)
the RDFversion ofthe modelfor thefuture(similarsimplicity:linked data,SemanticWeb)
the web sitehttp://wiki.teria.no/display/inloc/Home… with separate pages for the information modeland each model component, the guidelines withall the examples, the application profiles, thebindings, the background information, theanalysis …… connecting them all together with very richcross-linking and cross-reference …… an ongoing resource for implementation …
surprising challenges● getting interest and contributions● need for cleverer publicity, PR and marketing● being realistic about how prospectivestandardization works (or doesnt)
getting people to contribute● why should they?● because there is something in it for them – but what?● usually, they already have their own private businessmodels quite clear – what is their market orientation?● new entrepreneurs may see the opportunities – but how dowe reach them?● policy drivers – who might mandate InLOC?● market motivation– to provide better features, particularly between applications– use InLOC as good model to save time– collective commitment to common good
need for more publicity● we didnt have a big PR campaign as no onededicated on the team● weve created a great specification – this iswhat the project required – but it is not all thatis needed for a successful standard● we need you to help spread the word● reach framework owners and tool builders● put over the benefits
being realistic● InLOC has been a forward-looking project– “anticipatory”, “prospective” etc.● these are hard to make successful● we need to convert our excellent ideas intoreal adoption● we will propose recommendations to differentparties● all help and suggestions welcomed!
Recommendations● encourage framework publication in InLOC● signpost expertise● tool builders must allow users to refer toInLOC● try integrating with schema.org using RDFa● embed integration with InLOC into projects● extend InLOC to APIs and structural terms● judge best time for formal standardization
thanks for your interest in InLOCkeep in touchlets work together in the email@example.com@asimong