ePortfolio 2.0 luk vervenne

1. ePortfolio 2.0lukvervenne empowerment of the Human Factor trends & perspectives titel

2. HCSIT summit • Employers • globalisation: flexibility, agile, … • from make industry to project, services & knowledge economy • hiring & firing • managing inflow AND outflow • anticipate & plan for layoffs • regional embedding • Learners - Employees • employability awareness • lifelong and lifewide learning, reflection & competence development • informal learning • self-regulated learning • employability support infrastructure • Employability service providers • Schools training insititutes • Certification of acquired competencies (EVC/EBC) • Public/private employment services < HR services • Managing outflow of companies • Shared service centers - mobility centers titel

3. Dynamically created For a particular purpose From local and remote data For a particular system According to the required spec Technically the ePortfolio is a dynamically created view on distributed data. „The“ ePortfolio is… “The” ePorfolio technically

4. What does eportfolio 2.0 need? Social Innovation • The “meaningfull self” versus the society • Active Identities < the self-managing individual! • Support infrastructure < shared service centers • Public/private partnerships + change management! ‘Talent Production Technology’ • Eportfolio’s < employabilityPortfolios • Interoperability : adding semantics to syntax • Rethink the standards (and standards making!) • Open Service Oriented Architectures (SOA) • Trust : security, privacy, authentication, authorisation, dependability (end-user trust perception!) titel

5. Trends in standards making • The post-EDI era has arrived. Really, it did…Really! • Cross-domain standards & issues: lifelong+lifewide • Syntax + semantics • UN/Cefact has accepted to register data models represented as as semntic building blocks as ‘core components’. (version 3.0 April 2007). • Conceptual Core components shared by multiple standards Abstract …”The Core Components Technical Specification defines meta models and rules necessary for describing the structure and contents of conceptual and physical/logical data models, process models, and information exchange models. The CCTS is dependent on the Unified Modelling Language (UML) in terms of how it is expressed in this specification, but does not require UML in its implementation”… titel

6. UN/CEFACT Core Components Technical Specification (UN/CEFACT CCTS) • Describes + specifies a semantic-based approach to the well-understood problem of the lack of information interoperability within and between applications & databases in the e-business arena. It focuses especially on a dynamic, flexible and interoperable way of standardizing business semantics of libraries for electronic business data exchange. • Developing a common set of semantic building blocks that represent the general types of business data in use today, providing for the creation of new business vocabularies as well as restructuring of existing business vocabularies to achieve semantic interoperability of data. • Defines metamodels, and rules necessary for describing the structure and contents of conceptual, logical & physical data models that can be used for collaborative business processes and information exchange. • (“An ontological commitment is <mapping + constraints (rules)>”) UN/CEFACT Core Components Technical Specification

7. Core Components Technical Specification (CCTS) • A way to identify, capture & maximize the re-use of business information to support and enhance information inter-operability across multiple business situations. The specification focuses both on human-readable and machine-processable representations of this information. • More flexible than current data / information exchange standards because the semantic standardization is done in a syntax-neutral fashion. This syntax-neutral semantic based methodology allows for the richness inherent in natural language to be used to create data and information exchange models that are devoid of computer-driven syntax limitations and requirements. • Business process + core component solutions capture a wealth of information about the business reasons for variation in data model and message semantics and structure. In the past, such variations have introduced incompatibilities. The core components mechanism uses this rich information to allow identification of exact similarities and differences between semantic models. Core Components Technical Specification

8. CCTS focus areas CCTS has 2 focus areas: core components + business information entities: • Core Components. Core components are semantic building blocks that can be used for all aspects of data & information modelling and its exchange. Core components are the linchpin for creating interoperable business process models and business documents. Core components are conceptual in nature, they are used for creating context specific BIEs. • Business Information Entities. Core Components act as conceptual models that are used to define Business Information Entities (BIEs). BIEs are the expression of the conceptual core components as logical/physical data model objects and information exchanges. BIEs are created through the application of context and may be qualified to guarantee unique business semantics. A specific relationship exists between CCs and BIEs; BIEs are always derived from their source CC. titel

9. Cross-domain, specification-neutral “Employability Repository” IMS - HR-XML – EuroPass – Proprietary - ...etc ‘real’ standards based ePortfolio IMS New HR-XML! New HR-XML! Blatingly Non-standard process environment Called “portfolio” SCHOOL PORTFOLIO SOFT HR PORTFOLIO Find WORK PORTFOLIO Employment BACK OFFICE HR SYSTEM ERP Student admin system BACK OFFICE EDUCATION INDUSTRY P(R)ES

10. Lifelong – Lifewide Eportfolio’s • Exchanging eportfolio (information) between educational institutes is fine, but: • Still lack of IMS compliant software • Too big a standard for a single receiving business process • Exchanging EP info with industry is problematic • Different standards : industry and employment services use HR-XML or proprietary standards. • EP-information is often re-used for different(HR-)purposes • EP information is used in smaller chunks All of this requires a semantic interoperability with syntax & process neutral reuse of EP-components titel

11. Specification Neutral ePortfolios A short introduction Human Capital and Social Innovation Technology Summit

12. "a collection of authentic and diverse evidence… drawn from a larger archive, representing what a person or organization has learned over time, on which the person or organization has reflected, designed for presentation to one or more audiences for a particular rhetorical purpose." (Educause NLII) ePortfolios are… ePortlolios

13. Specification Neutral HR-XML IMS-LIP Eportfolio Repository Specification neutral

14. Dynamically created For a particular purpose From local and remote data For a particular system According to the required spec Technically the ePortfolio is a dynamically created view on distributed data. „The“ ePortfolio is… “The” ePorfolio technically

15. Fedora – an exampleEP as dynamic repository views • Fedora stores objects • Fedora objects consist of data streams • Object data streams hold data… • or links to remote data… • or links to data streams of other objects • Fedora objects may contain disseminators… • which aggregate views of data streams • Fedora knows relations between objects Fedora

16. What does this mean for eportfolio 2.0? titel

17. titel

18. titel