ISO/TC 68/SC 9
Projekta Nr. | ISO/TR 22126-2:2025 |
---|---|
Nosaukums | <p class="MsoBodyText"><span lang="EN-GB">This document is concerned with the representation of the ISO 20022 e-Repository contents in RDF and OWL by developing a case study around the ISO 20022 auth.016 sample message (hereafter simply referred to as “auth.016”). This includes:<span style="mso-spacerun: yes;"> </span></span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">a)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">transformation of the sample message into an RDF instance graph;<span style="mso-spacerun: yes;"> </span></span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">b)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">demonstrating a set of SPARQL rules that transform the auth.016 message into a FIX TradeCaptureReport(35=AE) message (hereafter simply referred to as “FIX AE”); </span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">c)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">expressing the metamodel, business components and message components exactly with a custom RDF vocabulary; </span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">d)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">representing those schemas as OWL schemas using OWL vocabulary when possible and annotation properties otherwise;</span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">e)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">creating instance graphs for the auth.016 sample messaging using the vocabulary of the business components and message components. </span></p> <p class="MsoBodyText"><span lang="EN-GB">This document also discusses the choices that arise in structuring RDF documents equivalent to documents in XML, and FIX Tag-Value format balancing considerations such as preserving the order of parts of the message versus creating graphs that are suitable for RDFS and OWL inference.</span></p> |
Reģistrācijas numurs (WIID) | 76310 |
Darbības sfēra | <p class="MsoBodyText"><span lang="EN-GB">This document is concerned with the representation of the ISO 20022 e-Repository contents in RDF and OWL by developing a case study around the ISO 20022 auth.016 sample message (hereafter simply referred to as “auth.016”). This includes:<span style="mso-spacerun: yes;"> </span></span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">a)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">transformation of the sample message into an RDF instance graph;<span style="mso-spacerun: yes;"> </span></span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">b)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">demonstrating a set of SPARQL rules that transform the auth.016 message into a FIX TradeCaptureReport(35=AE) message (hereafter simply referred to as “FIX AE”); </span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">c)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">expressing the metamodel, business components and message components exactly with a custom RDF vocabulary; </span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">d)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">representing those schemas as OWL schemas using OWL vocabulary when possible and annotation properties otherwise;</span></p> <p class="ListNumber1" style="mso-list: l0 level1 lfo1;"><!-- [if !supportLists]--><span lang="EN-GB" style="mso-fareast-font-family: Cambria; mso-bidi-font-family: Cambria;"><span style="mso-list: Ignore;">e)<span style="font: 7.0pt 'Times New Roman';"> </span></span></span><!--[endif]--><span lang="EN-GB">creating instance graphs for the auth.016 sample messaging using the vocabulary of the business components and message components. </span></p> <p class="MsoBodyText"><span lang="EN-GB">This document also discusses the choices that arise in structuring RDF documents equivalent to documents in XML, and FIX Tag-Value format balancing considerations such as preserving the order of parts of the message versus creating graphs that are suitable for RDFS and OWL inference.</span></p> |
Statuss | Standarts spēkā |
ICS grupa | 03.060 35.240.40 |