1. Interoperability frameworks for exchange of information between diverse management systems Interoperability frameworks for exchange of information between diverse management systems Luis Anido-Rifon – University of Vigo (ES) Niall Sclater – University of Strathclyde (Sco) CEN/ISSS Workshop Learning Technologies, October 6-7. Vienna

2. Agenda Interoperability frameworks for exchange of information between diverse management systems Project objectives Project Schedule and Current State. Decisions from Tessaloniki Final CWA-1/report Final CWA-2 Draft CWA-3 Next Steps

3. Project Objectives Interoperability frameworks for exchange of information between diverse management systems – To provide interoperability specifications for a range of information exchange, initially aimed at school systems but also applicable in a wider lifelong learning context. This work item will support the outputs of the OASIS (Open Architecture and Schools in Society) project that enable different applications and systems to share information. – OASIS is developing a European version of the US School Interoperability Framework (SIF) – The main task of the PT should be to act as a gateway between OASIS and the WS. An overall objective should be to publish one or more CWAs containing results from OASIS.

4. Agenda Interoperability frameworks for exchange of information between diverse management systems Project objectives Project Schedule and Current State. Decisions from Tessaloniki Final CWA-1/report Final CWA-2 Draft CWA-3 Next Steps

5. Project Schedule (i) Interoperability frameworks for exchange of information between diverse management systems Organised around the three deliverables: 1.- SIF Infrastructure, Architecture, Message Processing and Transport Layer 2.- Internationalisation of SIF and Harmonisation with other specs/standards 3.- Adaptation of the SIF data model to a European context

6. Project Schedule (ii). Current State Interoperability frameworks for exchange of information between diverse management systems DocumentDraft version due byFinal version due by Document 1ent 1July 2003October 2003 Document 2cument 2July 2003October 2003 Document 3 3October 2003December 2003 No new documents from OASIS WP2 since June!!

7. Agenda Interoperability frameworks for exchange of information between diverse management systems Project objectives Project Schedule and Current State. Decisions from Tessaloniki Final CWA-1/report Final CWA-2 Draft CWA-3 Next Steps

8. Decisions from Tessaloniki (i) Recommendations in both document 1 and document 2 should only include: - The need - Action Interoperability frameworks for exchange of information between diverse management systems

9. Decisions from Tessaloniki (ii) Document 1: “SIF Infrastructure, Architecture, Message Processing and Transport Layer” cannot be accepted as a CWA in its current form. The PT had to re-write this document and focus its contents on recommendations to SIF and SIF-based initiative rather than specific comments to OASIS. An eventual decision on wheter the document should be publish as a CWA or report will be taken in the Vienna meeting. Interoperability frameworks for exchange of information between diverse management systems

10. Agenda Project objectives Project Schedule and Current State. Decisions from Tessaloniki Final CWA-1/report Final CWA-2 Draft CWA-3 Next Steps

11. SIF Infrastructure, Architecture, Message Processing and Transport Layer New organization for the final document: 1.- Introduction 2.- SIF Infrastructure, Architecture, Message Passing and Transport Layer 3.- Review on SIF Infrastructure, Architecture, Message Passing and Transport Layer 4.- CEN/ISSS WS-LT Recommendations 6.- Appendixes 7.- References Interoperability frameworks for exchange of information between diverse management systems

12. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 1 The need: What is “Architecture” and what is “Infrastructure” is a complex issue that always implies a certain degree of subjectivity. Nevertheless, there are several cases where both concepts are clearly mixed in the original SIF specification. Interoperability frameworks for exchange of information between diverse management systems

13. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 1 Action: Re-organize the SIF specification, in particular the section dealing with Architecture, in order to clearly separate the specification on the SIF “Architecture” and the SIF “Infrastructure”. Interoperability frameworks for exchange of information between diverse management systems

14. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 2 The need: Message Processing and Passing business logic is specifed in SIF using the natural language. Textual descriptions with some graphics are used to describe how messages should be exchanged and how they should be processed by the different parties involved. A formalization of this description is needed Interoperability frameworks for exchange of information between diverse management systems

15. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 2 Action: To formally specify the SIF message model including message format and message processing rules. For this, the use of UML or BPEL4WS may be considered. Interoperability frameworks for exchange of information between diverse management systems

16. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 3 The need: The specification of a common API would promote the development of reusable components, which, in turn, could be used by those developing SIF- compliant software. This API would encapsulate the business logic for message processing and passing, which should be formally defined according to Recommendation 4.2. Interoperability frameworks for exchange of information between diverse management systems

17. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 3 Action: To specify a common interface encapsulating the business logic for message processing and passing. The OMG’s Interface Definition Language (IDL) is a technology-independent language for interface definition that may be considered as an initial approach. Interoperability frameworks for exchange of information between diverse management systems

18. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 3 Action (Cont.): Once the Application Programming Interface were specified at the conceptual level the next step should be to bind this conceptual interface to concrete interfaces for particular implementation environments and programming languages (e.g. Java, C++, etc.). Interoperability frameworks for exchange of information between diverse management systems

19. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 4 The need: The SIF specification defines in its section 3.6 its own mechanism to encapsulate SIF messages using the HTTPS protocol. Currently, there exists and open and widely used technology that supports the same functionality: SOAP. The use of SOAP would ease the implementation of SIF-compliant tools. Interoperability frameworks for exchange of information between diverse management systems

20. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 4 Action: To adopt the use of W3C’s SOAP as the mechanisms to encapsulate and exchange messages over HTTPS in the SIF infrastructure model. Interoperability frameworks for exchange of information between diverse management systems

21. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 5 The need: The SIF specification limits queries to a subset of logical conditions (at present, only equality is defined as a test mechanism). A wider mechanism, including other logical conditions, would improve object queries in SIF. Interoperability frameworks for exchange of information between diverse management systems

22. SIF Infrastructure, Architecture, Message Processing and Transport Layer 4.- CEN/ISSS WS-LT Recommendation 5 Action: To define alternative logical operations to the equality and a more elaborated language for SIF objects queries. Interoperability frameworks for exchange of information between diverse management systems

23. Open Question Should this report become a CWA? The PT’s answer is YES. A good set of recommendations (both from OASIS and the PT) may be included in a CWA on SIF Infrastructure, Architecture, Message Processing and Transport Layer that could be useful for SIF and other SIF-based initiatives Final decission? Interoperability frameworks for exchange of information between diverse management systems

24. Agenda Project objectives Project Schedule and Current State. Decisions from Tessaloniki Final CWA-1/report Final CWA-2 Draft CWA-3 Next Steps

25. Internationalization of SIF and harmonisation with other specs/standards Organization of the final document: 1.- Foreword 2.- Introduction to SIF 3.- Scope 4.- Abbreviations 5.- Stakeholders 6.- SIF Data Model Interoperability frameworks for exchange of information between diverse management systems

26. Internationalization of SIF and harmonisation with other specs/standards Organization of the draft document: 7.- Internationalisation of the SIF data model (Updated) 8.- Harmonisation of SIF with other Standars and Specifications (Updated) 9.- Detailed analysis of SIF Data Model (New) 1o.- Recommendations (Updated) 11.- References Interoperability frameworks for exchange of information between diverse management systems

27. Internationalization of SIF and harmonisation with other specs/standards 7.- Internationalisation SIF 7.3 Actions on Language elements 1.- Adopt a standard wider than Z39.50. For example ISO 639-2:1988, which is a three-letter code for the representation of languages. This standard covers, for example the above mentioned dialect of Spanish. Interoperability frameworks for exchange of information between diverse management systems

28. Internationalization of SIF and harmonisation with other specs/standards 7.- Internationalisation SIF 7.3 Actions on Language elements 2.- Although ISO 639-2:1988 covers a wider set of languages than the currently used in SIF Z39.53, there are situations where this is not enough: 2.1.- Variations of the same language depending on the country where it is spoken cannot be managed using only the ISO standard. For example, there should be a mechanism to distinguish between the Mexican Spanish or the Spaniard Spanish, or the US English and the British English. Interoperability frameworks for exchange of information between diverse management systems

29. Internationalization of SIF and harmonisation with other specs/standards 7.- Internationalisation SIF 7.3 Actions on Language elements 2.2. Variations of the same language depending on the region where it is spoken cannot be managed using only the ISO standard. For example, the following French variants: Norman, Picard, Wallon, Angevin, Berrichon, Bourbonnais, Bourguignon, Franc-Comtois, Gallo, Lorraine, Poitevin, Santogeais) do not have an ISO code. Interoperability frameworks for exchange of information between diverse management systems

30. Internationalization of SIF and harmonisation with other specs/standards 7.- Internationalisation SIF 7.3 Actions on Language elements The following format is proposed as an initial starting point: Langcode(“-“Subcode(“-“Variant)) where Langcode: Three letter code according to the standard ISO 639- 2:1988 Subcode: Two letter code for identification of countries ISO 3166-1:1997 Variant: Code for the variation of the language identified by the previous two codes. Interoperability frameworks for exchange of information between diverse management systems

31. Internationalization of SIF and harmonisation with other specs/standards 7.- Internationalisation SIF 7.3 Actions on Language elements Thanks to John Cowan! The RFC 3066 proposes a similar format: Language-Tag = Primary-subtag * ( “-“ Subtag ) Primary-subtag = 1*8ALPHA Subtag = 1*8(ALPHA / DIGIT) The productions ALPHA and DIGIT denote respectively the characters A to Z in upper or lower case and the digits from 0 to 9. The character “-” is HIPHEN-MINUS. Interoperability frameworks for exchange of information between diverse management systems

32. Internationalization of SIF and harmonisation with other specs/standards 7.- Internationalisation SIF 7.3 Actions on Language elements The primary subtag may be either a 2-letter code from ISO 639 standard or a 3-letter code from ISO 639-2 standard (languages) The second subtag may be a 2-letter code from ISO 3166 standard (countries), a dialect, a region identification, etc. There are no further rules for the third and subsequent subtags The first format proposed is a particular case of this second one Interoperability frameworks for exchange of information between diverse management systems

33. Internationalization of SIF and harmonisation with other specs/standards 8.-Harmonisation (Updated) 8.2 Identified issues 3.- The common data element MeetingTime defines a time slot for a specific course. The specifications vCalendar and the improved iCalendar which is an enhanced version of vCalendar specified by IETF, could be used. Applications supporting iCalendar should support vCalendar, but the reverse may not occur. iCalendar defines a MIME content type for exchanging electronic calendaring and scheduling information.

34. Internationalization of SIF and harmonisation with other specs/standards 9.-Detailed analysis of the SIF data model ElementAttributeComment Demographics Ethnicity TypeNo action CodeApply recommendations 10.8, 10.9 y 10.11 Ethnicity/ProportionNo action GenderApply recommendation 10.8 BirthDateApply recommendation 10.5 BirthDateVerificationApply recommendation 10.8, 10.9 and 10.11 This section describes a the SIF data model identifying for every element which recommendations are applicable Every single SIF data element (more than 240) has been analysed and reported in the CWA

35. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.1 Recommendation 1.- Incomplete or not suitable data objects and elements The need: There are several data objects that show the need of adaptation of the SIF Data Model when used in a different educational/cultural setting. Some of them are Address, Name, SchoolInfo, StudentSectionEnrollment, TermInfo, etc

36. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.1 Recommendation 1.- Incomplete or not suitable data objects and elements Action: To adapt these objects to each different cultural environment changing the necessary elements or adding/removing elements

37. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.2 Recommendation 2.- Data coding The need: The SIF specification does not identify the character set repertoire that should be used to represent textual information and this is an important issue when dealing with multi-lingual environments. Besides there is no way to specify the writing styles (left to right/right to left or horizontal/vertical).

38. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.2 Recommendation 2.- Data coding Action: Update the SIF specification to define a repertoire character set wide enough to cope with as many languages as possible. A possible starting point would be to analyse the ISO/IEC 10646 and UNICODE. An alternative would be to define, for each cultural environment where a SIF-based specification is to be used, which repertoire set is needed to properly represent the concrete language/s used in that context.

39. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.3 Recommendation 3.- Language elements The need: The value space for Language (Demographics object) and LanguageOfInstruction (SectionInfo object) is the ANSI/NISO Z39.53-2001: Codes for the Representation of Languages for Information Interchange. This language representation has several disadvantages for its use in a worldwide environment. This format does not allow the use of dialects or variations. For example, a variation/dialect of Spanish, Asturian, is not included in Z39.50.

40. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.3 Recommendation 3.- Language elements Action: To define the use of a standard wider than Z39.50. The PT proposes the use of ISO 639-2/B

41. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.4 Recommendation 4.- Variations of the language The need: Variations of the same language depending on the country where it is spoken cannot be managed using the current format to represent languages in SIF. Variations of the same language depending on the region where it is spoken cannot be managed using only the ISO standard either.

42. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.4 Recommendation 4.- Variations of the language Action: To adopt the following format (based on CWA LOM Int. and RFC 3066): Langcode(“-“Subcode(“-“Variant)) where Langcode: Three letter code according to the standard ISO 639-2:1988 Subcode: Two letter code for identification of countries ISO 3166-1:1997 Variant: Code for the variation of the language identified by the previous two codes.

43. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.5 Recommendation 5.- Date-value elements The need: SIF Data Model does not specify how dates should be represented. The only reference in the specification to date format is in the section where encapsulation of SIF messages over HTTP is presented. Specification of dates formats should be done at the conceptual data level.

44. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.5 Recommendation 5.- Date-value elements Action: To explicitly define the date format in the conceptual data model description section within the SIF specification. For this, an initial proposal may be a widely used standard like ISO 8601. The proposed format by this PT is in the form YYYY-MM-DD, as ISO 8601:2000 recommends. To add an extension to the specification of the DateTime item in order to give the possibility to use a Localized Date-Time when it can be relevant for a particular cultural context. The extension recommended by this CWA is reported at section 7.4 of this document.

45. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.6 Recommendation 6.- Currency-based values The need: There are several elements in the SIF Data Model that are defined to encapsulate numbers representing money (e.g. BilledAmount in the object BillingObject).

46. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.6 Recommendation 6.- Currency-based values Action: The previously presented objects should be extended to allow the specification of the particular currency being used to indicate each amount. An initial solution could be to create an aggregate data element (e.g. monetaryamount) with two sub-elements (e.g. amount, currency) being the latter the identifier of the currency being used. The identifier for the currency must follow a widely used standard. An initial approach may be to use ISO 4217:2001. Codes for the representation of currencies and funds.

47. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.7 Recommendation 7.- Measurement-type values The need: The SIF Data Model makes no reference to the possibility of using objects whose value represents measurements in an environment where several measurement formats are used (e.g. kilometres and miles).

48. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.7 Recommendation 7.- Measurement-type values Action: To extend those data objects to allow the specification of the particular measurement type being used (e.g. miles, feet, pounds, kilometres, kilos). An initial approach, is to create an aggregate data element (e.g. measurement) with two sub-elements (e.g. amount, unit). The identifier for the measurement must follow a widely used standard. An initial approach may be to use ISO 31:1992, Quantities and Units. Part 0: General Principles, Units and Symbols. Part 1: Space and time.

49. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.8 Recommendation 8.- Internationalisation of Vocabularies The need: Many SIF data elements use vocabularies defined by the SIF specification or externally defined in two sets of codes. These codes are composed of an abbreviation and a textual description of its meaning in the English language.

50. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.8 Recommendation 8.- Internationalisation of Vocabularies Action: To translate descriptions into other languages. This action may be taken by the own SIF community following a gradual translation process. Translations should be carried out in the short term for those languages more widely spoken worldwide. An alternative to this option may be to put this responsibility on each SIF-based initiative.

51. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.9 Recommendation 9.- Proposals for Vocabularies The need: Many SIF vocabularies may provide a set of values that are not suitable or do not cover completely the specific scope out of a US school environment.

52. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.9 Recommendation 9.- Proposals for Vocabularies Action: To extend/modify vocabularies for each particular educational/cultural/political setting.

53. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.10 Recommendation 10.- Harmonization of Personal Information The need: The main information involved in message exchange is related to student management data and administration services. Most SIF objects contains elements with personal data.

54. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.10 Recommendation 10.- Harmonization of Personal Information Action: To harmonise personal data information included in SIF specification using any of the following standards/specifications: IMS LIP (Learner Information Package), PAPI (Public And Private Information Learner) or vCard.

55. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.11 Recommendation 11.- Harmonization of Vocabularies The need: Many SIF data elements use vocabularies, defined by the SIF specification or externally defined in two sets of codes. The space value covered by this vocabularies may have been previously defined in other existing initiatives.

56. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.11 Recommendation 11.- Harmonization of Vocabularies Action: To take into account existing initiatives to develop taxonomies and vocabularies for the educational domain within their context. In Europe there exist several well-known providers of educational vocabularies in its wider sense (e.g. ETB (European Treasury Browser) [9] or CEDEFOP (European Centre for the Development of Vocational Training)[10]).

57. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.12 Recommendation 12.- iCalendar The need: The common data element MeetingTime defines a time slot for an event within a section or a course. This element can be harmonised with other standards.

58. Internationalization of SIF and harmonisation with other specs/standards 10.-Recommendations 10.12 Recommendation 12.- iCalendar Action: To take into account existing specifications like iCalendar, which provides a suitable data model to be used here.

59. Internationalization of SIF and harmonisation with other specs/standards Final document delivered through the WS mailing list in August 8th requesting comments before endorsement. Number of comments received: 1 (John Cowan) Interoperability frameworks for exchange of information between diverse management systems

60. Internationalization of SIF and harmonisation with other specs/standards Can this CWA enter a electronic endorsement process?

61. Agenda Interoperability frameworks for exchange of information between diverse management systems Project objectives Project Schedule and Current State. Decisions from Tessaloniki Final CWA-1/report Final CWA-2 Draft CWA-3 Next Steps

62. Adaptation of the SIF data model to a European context This document should contain a review of what should have produced the OASIS WP2 team. No data model has been produced so far. First drafts are expected by October 23rd.

63. Adaptation of the SIF data model to a European context Organization of our draft document: 1. Foreword 2. Introduction 3. Scope 4. Abbreviations 5. Stakeholders 6. Data Model 7. References 8. Appendixes

64. Adaptation of the SIF data model to a European context. Data Model To develop this draft version we took into account recommendations from the CWA “Internationalisation of SIF and Harmonisation with other specs/standards”. Specifically: Rec.1 : Incomplete or unsuitable objects and elements

65. Adaptation of the SIF data model to a European context. Data Model To develop this draft version we took into account recommendations from the CWA “Internationalisation of SIF and Harmonisation with other specs/standards”. Specifically: Rec.3 and 4 : Language elements and variations

66. Adaptation of the SIF data model to a European context. Data Model To develop this draft version we took into account recommendations from the CWA “Internationalisation of SIF and Harmonisation with other specs/standards”. Specifically: Rec. 5: Date-value elements

67. Adaptation of the SIF data model to a European context. Data Model To develop this draft version we took into account recommendations from the CWA “Internationalisation of SIF and Harmonisation with other specs/standards”. Specifically: Rec. 6: Currency-based values

68. Adaptation of the SIF data model to a European context. Data Model To develop this draft version we took into account recommendations from the CWA “Internationalisation of SIF and Harmonisation with other specs/standards”. Specifically: Rec. 7: Measurement-type values

69. Adaptation of the SIF data model to a European context. Data Model To develop this draft version we took into account recommendations from the CWA “Internationalisation of SIF and Harmonisation with other specs/standards”. Specifically: Rec. 9: Proposals for vocabularies

70. Adaptation of the SIF data model to a European context. Data Model To develop this draft version we took into account recommendations from the CWA “Internationalisation of SIF and Harmonisation with other specs/standards”. Specifically: Rec. 10: Harmonisation with existing vocabularies

71. Adaptation of the SIF data model to a European context. Data Model To develop this draft version we took into account recommendations from the CWA “Internationalisation of SIF and Harmonisation with other specs/standards”. Specifically: Rec. 11: Harmonisation with iCalendar

72. Adaptation of the SIF data model to a European context. Data Model Common elements: Address: This element identifies an address. – AdministrativeTerritorialUnit (State, Province, etc.) DateTime: This element represents a Date, a Time or both. New Object based on CWA “Internationalisation of SIF and Harmonisation with other Specs/Standards”

73. Adaptation of the SIF data model to a European context. Data Model Common elements: Demographics: Demographics information about any person. This object occurs within objects such as StudentPersonal, StudentContact, etc. – Ethnicity element removed. – AdministrativeTerritorialUnit – Language element improved (based on CWA 14590 Description of Language Capabilities) Email: This element represents a personal or work e-mail address and occurs in objects such as StudentPersonal, StaffPersonal, etc.

74. Adaptation of the SIF data model to a European context. Data Model Common elements: GridLocation: This element contains a map location. The GridLocation element is utilized within other objects and elements, such as BusStopInfo and Address. Measurement: This element represents a measurement and occurs in the RoomInfo element – New Object based on CWA “Internationalisation of SIF and Harmonisation with other Specs/Standards” MeetingTime: This element represents the meeting times and periods for a course, and occurs within objects such as SectionInfo and StudentSectionEnrollment. – Completely new. Based on iCalendar

75. Adaptation of the SIF data model to a European context. Data Model Common elements: MonetaryAmount: This element identifies an amount of money. It occurs within objects such as Cash within StudentMeal, Billing, etc. – New Object based on CWA “Internationalisation of SIF and Harmonisation with other Specs/Standards” Name: This element can belong to a student, staff member, contact, etc. It occurs within objects such as StudentPersonal, StudentContact, etc. – Surname is a composite element (First part + Second Part)

76. Adaptation of the SIF data model to a European context. Data Model Common elements: OtherId: Lists all “other” IDs associated with objects. This element occurs in objects such as StudentPersonal and StaffPersonal, etc. – Vocabulary to be further studied PhoneNumber: This object represents a phone number and occurs within objects such as StudentPersonal, StaffPersonal, etc.

77. Adaptation of the SIF data model to a European context. Data Model Food Services WG objects: StudentMeal: This element’s purpose is to communicate the current meal status of a given student. – Some elements’ value spaces have been updated using the new common objects introduced by this PT.

78. Adaptation of the SIF data model to a European context. Data Model Human Resources & Financials WG objects: Billing: This object contains an amount to be billed to an outside entity. – Some elements’ value spaces have been updated using the new common objects introduced by this PT. Payment: This object contains information about the payment of a billing object. – Some elements’ value spaces have been updated using the new common objects introduced by this PT.

79. Adaptation of the SIF data model to a European context. Data Model Library Automation WG objects: LibraryPatronStatus: This object reports the current library status for the requested student or staff member. – Some elements’ value spaces have been updated using the new common objects introduced by this PT.

80. Adaptation of the SIF data model to a European context. Data Model Student information WG objects: AttendanceCodeInfo: This object provides information about a particular attendance code, allows applications to synchronize each other’s attendance code tables, or to provide a dynamic list of attendance codes. RoomInfo: This object contains all of the information about a school’s room. – Some elements’ value spaces have been updated using the new common objects introduced by this PT.

81. Adaptation of the SIF data model to a European context. Data Model Student information WG objects: RoomType: This object identifies the type of room, i.e. Gym, Cafeteria, Standard Classroom, etc. SchoolCourseInfo: This object contains course information SchoolInfo: This object contains information about the school. - Some vocabularies to be further extended

82. Adaptation of the SIF data model to a European context. Data Model Student information WG objects: SectionInfo: This object provides information about the section – the specific time period a session of the course meets. – Some elements’ value spaces have been updated using the new common objects introduced by this PT and recommendations from CWA on “Internationalisation of SIF and Harmonisation with other Specs/Standards” – Some vocabularies to be further extended StaffPersonal: This object contains all the personal information relating to a staff member.

83. Adaptation of the SIF data model to a European context. Data Model Student information WG objects: StudentContact: This object contains the student’s contact information. - Some vocabularies to be further extended StudentDailyAttendance: This object provides daily attendance information for a particular student in a particular school on a particular date. - Some elements’ value spaces have been updated using the new common objects introduced by this PT StudentPersonal: This object contains all the information related to the student. - Some elements’ value spaces have been updated using the new common objects introduced by this PT

84. Adaptation of the SIF data model to a European context. Data Model Student information WG objects: StudentPicture: This object contains information about the student’s picture. StudentSchoolEnrollment: This object defines information related to a student’s enrollment. - Some elements’ value spaces have been updated using the new common objects introduced by this PT - Some vocabularies to be further extended

85. Adaptation of the SIF data model to a European context. Data Model Student information WG objects: StudentSectionEnrollment: This object contains information about a student’s enrollment in a section of a course. - Some elements’ value spaces have been updated using the new common objects introduced by this PT TermInfo: This object provides information about a term. - Some elements’ value spaces have been updated using the new common objects introduced by this PT

86. Adaptation of the SIF data model to a European context. Data Model Transportation and Geographic Information WG objects: BusEquipment: This object contains information about a type of equipment that may be on a bus. BusInfo: This object contains all of the information about a bus. BusRouteDetail: This object contains the schedule for the bus route. - Some elements’ value spaces have been updated using the new common objects introduced by this PT

87. Adaptation of the SIF data model to a European context. Data Model Transportation and Geographic Information WG objects: BusRouteInfo: This object contains all of the information about a bus route. - Recommendations from CWA on “Internationalisation of SIF and Harmonisation with other Specs/Standards BusStopInfo: This object contains information about a bus route. StudentTransportInfo: This object contains transportation information about a student.

88. Adaptation of the SIF data model to a European context. Appendixes: Vocabularies XML bindings (to be developed)

89. Agenda Interoperability frameworks for exchange of information between diverse management systems Project objectives Project Schedule and Current State. Decisions from Tessaloniki Final CWA-1/report Final CWA-2 Draft CWA-3 Next Steps

90. Next Steps (i) 1.- Develiver the final versions for 1.a.- Report/CWA on SIF Infrastructure, Architecture, Message Processing and Transpor Layer 1.b.- CWA on Internationalisation of SIF and harmonisation with other specs/standards Interoperability frameworks for exchange of information between diverse management systems

91. Next Steps (ii) 2.- Develop the final versions for the CWA “Adaptation of SIF Data Model for a European context” 2.1. Use output from OASIS WP2 2.2. Further analyse several vocabularies and data elements 2.3. Develop an XML binding Interoperability frameworks for exchange of information between diverse management systems

92. Thanks http://www.gist.uvigo.es/~lanido/interop/ Luis Anido-Rifon lanido@det.uvigo.es Niall Sclater n.sclater@strath.ac.uk www.sclater.com CEN/ISSS Workshop on Learning Technologies, 10-11 December 2002, Copenhagen, Denmark Interoperability frameworks for exchange of information between diverse management systems