Änderungen von Dokument 02 Standardkompatibilität

Zusammenfassung

• Seiteneigenschaften (1 geändert, 0 hinzugefügt, 0 gelöscht)
• Objekte (1 geändert, 0 hinzugefügt, 0 gelöscht)
  • Confluence.Code.ConfluencePageClass[0]

Details

Seiteneigenschaften

Inhalt

...	...	@@ -4,64 +4,10 @@
4	4	{{layout-cell}}
5	5
6	6
7		-{{conditionalcontent 0="Zielgruppe: (BPS)" sv-attr:866DE48701525447C13BC59401CD793F="866DE48701525447C13C469E1E314A59" atlassian-macro-output-type="INLINE"}}
8		-{{details}}
9		-|=(((
10		-Verantwortlicher
11		-)))|(((
12		-
13		-)))
14		-|=(% colspan="1" %)(% colspan="1" %)
15		-(((
16		-Status
17		-)))|(% class="highlight-yellow" colspan="1" data-highlight-colour="yellow" %)(% class="highlight-yellow" colspan="1" data-highlight-colour="yellow" %)
18		-(((
19		-{{sv-metadata type="workflow-status"/}}
	7	+(% class="removedPlaceholderWrapper" %)
20	20
21		-{{status colour="Red" title="Offen"/}}
22		-)))
23		-|=(% colspan="1" %)(% colspan="1" %)
24		-(((
25		-Varianten
26		-)))|(% colspan="1" %)(% colspan="1" %)
27		-(((
28		-{{sv-metadata type="variants"/}}
29		-)))
30		-|=(% colspan="1" %)(% colspan="1" %)
31		-(((
32		-Attribute
33		-)))|(% colspan="1" %)(% colspan="1" %)
34		-(((
35		-{{sv-metadata type="attributes"/}}
36		-)))
37		-|=(% colspan="1" %)(% colspan="1" %)
38		-(((
39		-Pagekey
40		-)))|(% colspan="1" %)(% colspan="1" %)
41		-(((
42		-{{sv-metadata type="pagekey"/}}
43		-)))
44		-|=(% colspan="1" %)(% colspan="1" %)
45		-(((
46		-Übersetzung
47		-)))|(% colspan="1" %)(% colspan="1" %)
48		-(((
49		-(% class="task-list" %)
50		-(((
51		-{{task reference="/Tasks/Task_1" status="Done"}}
52		-{{status colour="Green" title="fertig"/}} {{mention reference="XWiki.0a49950f5c0f19a8015c101b60e10001" style="FULL_NAME" anchor="XWiki-0a49950f5c0f19a8015c101b60e10001-acpot"/}}
53		-{{/task}}
54		-)))
55		-)))
56		-|=(% colspan="1" %)(% colspan="1" %)
57		-(((
58		-TODOs
59		-)))|(% colspan="1" %)(% colspan="1" %)
60		-(((
61		-
62		-)))
63		-{{/details}}
64		-{{/conditionalcontent}}
	9	+
	10	+
65	65	{{/layout-cell}}
66	66
67	67	{{layout-cell}}
...	...	@@ -178,11 +178,11 @@
178	178	{{layout}}
179	179	{{layout-section ac:type="two_right_sidebar"}}
180	180	{{layout-cell}}
181		-The ONYX Testsuite uses established standards in all areas to ensure a sustainable e-assessment solution. The ONYX Testsuite’s data model is based on the IMS QTI v2.1 specifications, meaning all content is available in standardised format. The results data is also shown in standardised form as an IMS QTI v2.1 report. The metadata is described using the open LOM standard.
	127	+The ONYX Testsuite uses established standards in all areas to be able to ensure a sustainable e-assessment solution. The data model of the ONYX Testsuite is based on the IMS QTI v2.1 specification, meaning all contents are available in standardised format. This also includes the result data, which are shown in standardised form as a IMS QTI v2.1 report. The description of the metadata is done via the open standard LOM.
182	182
183		-The current publication (November 2012) of IMS LTI 2.0 is designed to keep making the ONYX interfaces available as LTI interfaces, even in future.
	129	+As a member of the IMS QTI working group, we are actively involved in the development of the specification documents. The ONYX Testsuite serves as the reference implementation for IMS QTI v2.1. Due to its sustainable approach including the use of open standards and the provision of flexible, includable assessment modules, the ONYX Testsuite was already honoured with the Learning Impact Award in 2011 and a second time in 2014.
184	184
185		-As a member of the IMS QTI working group, we are actively involved with further developing the specification documents. The ONYX Testsuite serves as the reference implementation for IMS QTI v2.1, and, in 2011 and 2014, received the Learning Impact Award for its sustainable approach using open standards and providing flexible, integrable assessment modules.
	131	+
186	186	{{/layout-cell}}
187	187
188	188	{{layout-cell}}
...	...	@@ -200,23 +200,23 @@
200	200	{{layout-cell}}
201	201	== IMS QTI ==
202	202
203		-The globally recognised IMS Question and Test Interoperability (QTI) specification 2.1 forms the conceptual basis of the ONYX Testsuite. Almost all valuable functions of the Onyx Testsuite rely on this standard. Apart from content replaceability, further advantages are also generated by using QTI. The strict separation of content and layout and the XML-based mapping of all test and task content lay the foundations for an independent end format, and for editing existing content later on. The IMS QTI specifications stipulate replacing the test content as an IMS Content Package. This file archive contains a summary of all test data, the LOM metadata, and media therein. Formulae are described in MathML-Notation within the test data.
	149	+The globally recognised IMS Question and Test Interoperability (QTI) specification 2.1 forms the conceptual basis of the ONYX Testsuite. Almost all valuable functionalities of the Onyx Testsuite rely on this standard. In addition to the interchangeability of contents, the use of QTI offers several further advantages. The strict separation of content and layout as well as the XML-based mapping of all test and task contents lay the foundations for both an independent final format and the possibility to edit existing contents. The IMS QTI specification provides that the test contents are replaced in the form of an IMS content package. This file archive contains a summary of all test data, the LOM metadata, and all included media. Formulas are described in MathML-notation within the test data.
204	204
205		-Apart from the standard storage of test data, ONYX also stores the result data in accordance with IMS QTI. The IMS QTI Report file contains all test analysis data, including the learner responses, time stamps and points scored. The result file is expanded for manual assessments, enabling the assessment process to be traced. The results can also undergo a CSV export.
	151	+In addition to the standard-compliant storage of the test data, ONYX also stores the result data in accordance with IMS QTI. The IMS QTI report file contains all test evaluation data, including the learner responses, time stamp, and points gained. In the case of a manual evaluation, the result file will be expanded, which also enables a transparent and understandable evaluation process. A CSV export of the results is further possible.
206	206
207		-The ONYX Editor allows test data to be imported and exported to other formats, such as IMS QTI v1.2. The system manufacturers gave IMS QTI v1.2 a very heterogeneous design, meaning imports and exports are system-specific. The IMS QTI v1.2 Import was tested for Blackboard, WebCT and OLAT. A PDF Export is available in the ONYX Editor to allow the compiled test data to also be used in paper-based test scenarios. Various conversions have additionally been made for proprietary formats.
	153	+The ONYX editor offers the possibility to import and export test data to other formats such as IMS QTI v1.2. The system manufacturers gave IMS QTI v1.2 a very heterogeneous design, which is why the import and export is system-specific. The IMS QTI v1.2 import has been tested for Blackboard, WebCT, and OLAT. To be able to use the created test data also in paper-based test scenarios, the ONYX editor additionally contains a PDF export. Beyond that, various conversions for proprietary formats have been realised so far.
208	208
209	209	[[image:attach:ONYX-IMS-Award_EN.png]]
210	210
211	211	== IEEE LOM ==
212	212
213		-ONYX supports the open IEEE Learning Object Metadata (LOM) Standard which is recommended by the IMS QTI specification. The metadata is thus described in XML-Notation in the test data’s IMS Manifest. For each ONYX editor instance a metadata configuration can determine which metadata fields and values are displayed to the author in the ONYX Editor and how they should mapped to IEEE LOM.
	159	+ONYX supports large parts of the open IEEE Learning Object Metadata (LOM) standard. The metadata are thus described in XML notation in the test data’s IMS manifest. Which metadata are actually displayed to the author in the ONYX editor can be determined via a metadata configuration.
214	214
215	215	=== Standard metadata profile ===
216	216
217	217	[[image:attach:Standard metadata profile.png]]
218	218
219		-=== Customized metadata profile ===
	165	+=== Specific metadata profile ===
220	220
221	221	[[image:attach:Customized metadata profile.png]]
222	222	{{/layout-cell}}

Confluence.Code.ConfluencePageClass[0]

id

...	...	@@ -1,1 +1,1 @@
1		-178880903
	1	+182518164

url

...	...	@@ -1,1 +1,1 @@
1		-https://www.bps-system.de/help/display/SOV/wiki/spaces/ONYX/pages/178880903/Standardkompatibilitaet
	1	+https://www.bps-system.de/help/display/SOV/wiki/spaces/ONYX/pages/182518164/Standardkompatibilitaet