XCRI is an agreed upon standard that allows institutions to build interoperable systems to share course information. The document discusses extending the use of XCRI to encode additional metadata required for academic validation and planning processes. It also notes that current validation documents use academic language that is not friendly for students or external stakeholders, and questions if validation documentation needs to be in academic language. Finally, it raises the possibility of using XCRI to provide multilingual course information to different audiences and concerns about whether currently collected data quality would support more advanced analysis and reuse.

1. The Further Role of XCRI – Why XCRI? XCRI is a powerful lever in institutions because it is an agreed standard You can build systems round XCRI

2. Extension Directions? Modules Elements within modules Learning outcomes Competencies Graduate attributes/skills Student activities? Encode what is currently required by QAA

3. Extensions (Minority concerns) Support academic planning and validation processes e.g.Business plan

4. Observations Validation documents are written in academic /administrative language Not student friendly Not employer/external validation panel member friendly Inhibits reuse of content for marketing, student handbooks, etc. Do we need approval/validation documentation in academic speak ? (probably not) Multiple audiences for Course Information Could XCRI support multilingual information, i.e. for specified audiences? Fears that the quality of data currently collected by validation may not support the envisaged level of analysis/reuse e.g. learning outcomes that cannot map to competencies