https://www.w3.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=HsolbrigW3C Wiki - User contributions [en]2024-03-28T20:13:44ZUser contributionsMediaWiki 1.41.0https://www.w3.org/wiki/index.php?title=Template:Submission&diff=67212Template:Submission2013-07-09T16:47:12Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| '''<center>{{#if:{{{7|}}}|[{{{7}}} {{{1}}}]|[[media:{{{2|}}}|{{{1}}}]]}}</center>''' || {{{3}}} || {{{4|(none)}}} || talk:RdfValidationWorkshop/Papers/{{{5|}}} || {{{6|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67200Template:Submission2013-07-09T14:27:44Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| '''<center>{{#if:{{{7|}}}|[{{{7}}} {{{1}}}]|[[media:{{{2|}}}|{{{1}}}]]}}</center>''' || {{{3}}} || {{{4|(none)}}} || {{{5|}}} || {{{6|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67199Template:Submission2013-07-09T14:27:19Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| '''<center>{{{#if:{{{7|}}}|[{{{7}}} {{{1}}}]|[[media:{{{2|}}}|{{{1}}}]]}}</center>''' || {{{3}}} || {{{4|(none)}}} || {{{5|}}} || {{{6|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Sandbox&diff=67198Template:Sandbox2013-07-09T14:24:54Z<p>Hsolbrig: Created page with "{{#if:{{{2|}}}|{{{2}}}|{{{1}}} }}"</p>
<hr />
<div>{{#if:{{{2|}}}|{{{2}}}|{{{1}}} }}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67197RdfValidationWorkshop/Papers2013-07-09T13:45:36Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin|Requirements<br/>Proposed Solution|||http://www.w3.org/2012/12/rdf-val/submissions/Stardog}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson|Requirements}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth|Requirements<br/>Proposed Solutions}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn|Requirements<br/>Experience w/ XSD}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman|Requirements<br/>Proposed Solution}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya|Requirements}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac|Requirements<br/>Implementation Experience}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday | Application to LDP}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67196Template:Submission2013-07-09T13:44:47Z<p>Hsolbrig: Undo revision 67195 by Hsolbrig (Talk)</p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| '''<center>[[media:{{{2}}}|{{{1}}}]]</center>''' || {{{3}}} || {{{4|(none)}}} || {{{5|}}} || {{{6|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67195Template:Submission2013-07-09T13:43:43Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]|[<web link]]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| '''<center>{{#if:{{{7|}}}|[{{{7}}}|[[media:{{{2|}}}{{{!}}} }}{{{1}}}{{#if:{{{7}}}|]|]]}}</center>''' || {{{3}}} || {{{4|(none)}}} || {{{5|}}} || {{{6|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67194RdfValidationWorkshop/Papers2013-07-09T13:40:42Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks||Clark and Sirin|Requirements<br/>Proposed Solution|http://www.w3.org/2012/12/rdf-val/submissions/Stardog}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson|Requirements}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth|Requirements<br/>Proposed Solutions}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn|Requirements<br/>Experience w/ XSD}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman|Requirements<br/>Proposed Solution}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya|Requirements}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac|Requirements<br/>Implementation Experience}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday | Application to LDP}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67185RdfValidationWorkshop/Papers2013-07-08T19:52:53Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin|Requirements<br/>Proposed Solution}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson|Requirements}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth|Requirements<br/>Proposed Solutions}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn|Requirements<br/>Experience w/ XSD}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman|Requirements<br/>Proposed Solution}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya|Requirements}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac|Requirements<br/>Implementation Experience}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67184RdfValidationWorkshop/Papers2013-07-08T19:45:47Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson|Requirements}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth|Requirements<br/>Proposed Solutions}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn|Requirements<br/>Experience w/ XSD}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman|Requirements<br/>Proposed Solution}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya|Requirements}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac|Requirements<br/>Implementation Experience}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67183RdfValidationWorkshop/Papers2013-07-08T19:43:55Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth|Requirements<br/>Proposed Solutions}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn|Requirements<br/>Experience w/ XSD}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman|Requirements<br/>Proposed Solution}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya|Requirements}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac|Requirements<br/>Implementation Experience}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67182RdfValidationWorkshop/Papers2013-07-08T19:42:52Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn|Requirements<br/>Experience w/ XSD}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman|Requirements<br/>Proposed Solution}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya|Requirements}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac|Requirements<br/>Implementation Experience}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67181RdfValidationWorkshop/Papers2013-07-08T19:23:47Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman|Requirements<br/>Proposed Solution}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya|Requirements}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac|Requirements<br/>Implementation Experience}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67180RdfValidationWorkshop/Papers2013-07-08T19:16:21Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya|Requirements}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac|Requirements<br/>Implementation Experience}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67179RdfValidationWorkshop/Papers2013-07-08T19:09:33Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac|Requirements<br/>Implementation Experience}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67178RdfValidationWorkshop/Papers2013-07-08T19:03:35Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute|Implemenation Experience in Healthcare Domain}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Implementation Experience in Annotation Domain}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67177RdfValidationWorkshop/Papers2013-07-08T18:58:24Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery|Practical Implementation Experience}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67176RdfValidationWorkshop/Papers2013-07-08T18:51:25Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig|Requirements}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67175RdfValidationWorkshop/Papers2013-07-08T18:50:00Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds|Requirements<br/>Structure<br/>Vocabulary<br/>Code Lists}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67174RdfValidationWorkshop/Papers2013-07-08T18:39:28Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|RDFVal_Coyle_Baker.pdf|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|RDFVal_Skjæveland_Stolpe.pdf|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|RDFVal_Harrison.pdf |Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|na|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|RDFVal_Davidson.pdf|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|RDFVal_Booth.pdf|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|RDFVal_Mendelsohn.pdf |Mendelsohn}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|RDFVal_Fokuoe_Ryman.pdf|Fokoue and Ryman}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|RDFVal_Isaac.pdf |Isaac}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use|RDFVal_Jiang_Solbrig_Chute.pdf|Jiang, Solbrig and Chute}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|RDFVal_Menday.pdf |Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|RDFVal_Gerber_Cole_Lowery.pdf|Gerber, Cole and Lowery}}<br />
{{Submission|Definition of and Requirements For RDF Validation|RDFVal_Solbrig.pdf|Solbrig}}<br />
{{Submission|Validation: requirements and approaches|RDFVal_Reynolds.pdf |Reynolds}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Reynolds.pdf&diff=67173File:RDFVal Reynolds.pdf2013-07-08T18:39:19Z<p>Hsolbrig: Validation: requirements and approaches</p>
<hr />
<div>Validation: requirements and approaches</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Solbrig.pdf&diff=67172File:RDFVal Solbrig.pdf2013-07-08T18:38:39Z<p>Hsolbrig: Definition of and Requirements for RDF Validation</p>
<hr />
<div>Definition of and Requirements for RDF Validation</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Gerber_Cole_Lowery.pdf&diff=67171File:RDFVal Gerber Cole Lowery.pdf2013-07-08T18:38:00Z<p>Hsolbrig: Using SPARQL to Validate Open Annotation RDF Graphs</p>
<hr />
<div>Using SPARQL to Validate Open Annotation RDF Graphs</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Menday.pdf&diff=67170File:RDFVal Menday.pdf2013-07-08T18:37:08Z<p>Hsolbrig: Forms to direct Interaction with Linked Data Platform APIs</p>
<hr />
<div>Forms to direct Interaction with Linked Data Platform APIs</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Jiang_Solbrig_Chute.pdf&diff=67169File:RDFVal Jiang Solbrig Chute.pdf2013-07-08T18:36:18Z<p>Hsolbrig: A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use</p>
<hr />
<div>A Semantic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Isaac.pdf&diff=67168File:RDFVal Isaac.pdf2013-07-08T18:35:34Z<p>Hsolbrig: Europeana and RDF data validation</p>
<hr />
<div>Europeana and RDF data validation</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Esteban-Gutierrez_Castro_Mihindukulasooriya.pdf&diff=67167File:RDFVal Esteban-Gutierrez Castro Mihindukulasooriya.pdf2013-07-08T18:34:13Z<p>Hsolbrig: RDF Validation in a Linked Data World</p>
<hr />
<div>RDF Validation in a Linked Data World</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Fokuoe_Ryman.pdf&diff=67166File:RDFVal Fokuoe Ryman.pdf2013-07-08T18:31:54Z<p>Hsolbrig: </p>
<hr />
<div></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Foloue_Ryman.pdf&diff=67165File:RDFVal Foloue Ryman.pdf2013-07-08T18:31:10Z<p>Hsolbrig: OSLC Resource Shape: A Linked Data Constraint Language</p>
<hr />
<div>OSLC Resource Shape: A Linked Data Constraint Language</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Mendelsohn.pdf&diff=67164File:RDFVal Mendelsohn.pdf2013-07-08T18:30:07Z<p>Hsolbrig: Experiences with the Design of the W3C XML Schema Definition Language</p>
<hr />
<div>Experiences with the Design of the W3C XML Schema Definition Language</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Booth.pdf&diff=67163File:RDFVal Booth.pdf2013-07-08T18:28:52Z<p>Hsolbrig: Thoughts on Validating RDF Healthcare Data</p>
<hr />
<div>Thoughts on Validating RDF Healthcare Data</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Davidson.pdf&diff=67162File:RDFVal Davidson.pdf2013-07-08T18:27:53Z<p>Hsolbrig: Linked Data Profiles</p>
<hr />
<div>Linked Data Profiles</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Harrison.pdf&diff=67161File:RDFVal Harrison.pdf2013-07-08T18:26:47Z<p>Hsolbrig: RDF Validation requirements for data about products, services and companies</p>
<hr />
<div>RDF Validation requirements for data about products, services and companies</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Skj%C3%A6veland_Stolpe.pdf&diff=67160File:RDFVal Skjæveland Stolpe.pdf2013-07-08T18:25:18Z<p>Hsolbrig: Bounds: Expressing Reservations about Incoming Data</p>
<hr />
<div>Bounds: Expressing Reservations about Incoming Data</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67159Template:Submission2013-07-08T18:23:00Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| '''<center>[[media:{{{2}}}|{{{1}}}]]</center>''' || {{{3}}} || {{{4|(none)}}} || {{{5|}}} || {{{6|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67158Template:Submission2013-07-08T18:21:58Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| [[media:{{{2}}}{{!}}'''<center>{{{1}}}</center>''']] || {{{3}}} || {{{4|(none)}}} || {{{5|}}} || {{{6|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67157Template:Submission2013-07-08T18:16:28Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| {{#if:{{{2}}}|[[media:{{{2}}}{{!}}'''<center>{{{1}}}</center>''']]|'''<center>{{{1}}}</center>'''}} || {{{3}}} || {{{4|(none)}}} || {{{5|}}} || {{{6|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67156Template:Submission2013-07-08T18:14:10Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| {{#if:{{{2}}}|[[media:{{{2}}}{{!}} }}'''<center>{{{1}}}</center>'''{{#if:{{{2}}}|]]}} || {{{3}}} || {{{4|(none)}}} || {{{5|}}} || {{{6|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:!&diff=67155Template:!2013-07-08T18:12:55Z<p>Hsolbrig: Created page with "<noinclude>Template to create a vertical bar. Usage: <nowiki>{{!}}</nowiki><includeonly>|</includeonly>"</p>
<hr />
<div><noinclude>Template to create a vertical bar. Usage:<br />
<nowiki>{{!}}</nowiki><includeonly>|</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67154Template:Submission2013-07-08T18:10:31Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| {{#if:{{{2|}}}|[[media:{{{2}}}{{!}} }}'''<center>{{{1}}}</center>'''{{#if:{{{2|}}}|]]}} || {{{2}}} || {{{3|(none)}}} || {{{4|}}} || {{{5|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67153Template:Submission2013-07-08T18:05:26Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|[<file name>]|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| {{#if:{{{2|}}}|[[media:{{{2}}} }}'''<center>{{{1}}}</center>'''{{#if:{{{2|}}}|]]}} || {{{2}}} || {{{3|(none)}}} || {{{4|}}} || {{{5|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=File:RDFVal_Coyle_Baker.pdf&diff=67152File:RDFVal Coyle Baker.pdf2013-07-08T18:03:24Z<p>Hsolbrig: Dublin Core Application Profiles</p>
<hr />
<div>Dublin Core Application Profiles</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67151RdfValidationWorkshop/Papers2013-07-08T18:01:59Z<p>Hsolbrig: </p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|Harrison}}<br />
{{Submission|Stardog<br/>On RDF Validation, Stardog ICV and Assorted Remarks|Clark and Sirin}}<br />
{{Submission|Linked Data Profiles|Davidson}}<br />
{{Submission|Thoughts on Validating RDF Healthcare Data|Booth}}<br />
{{Submission|Experiences with the Design of the W3C XML Schema Definition Language|Mendelsohn}}<br />
{{Submission|OSLC Resource Shape: A Linked Data Constraint Language|Fokoue and Ryman}}<br />
{{Submission|RDF Validation in a Linked Data World<br/>A vision beyond structural and value range validation|Esteban-Gutiérrez, García-Castro and Mihindukulasooriya}}<br />
{{Submission|Europeana and RDF data validation<br/>A short expression of interest from a vocabulary owner|Isaac}}<br />
{{Submission|A Semantic Web-Based Framework for Quality Assurance of Electronic Medica Records Data for Secondary Use|Jiang, Solbrig and Chute}}<br />
{{Submission|Forms to direct interaction with Linked Data Platform APIs|Menday}}<br />
{{Submission|Using SPARQL to Validate Open Annotation RDF Graphs|Gerber, Cole and Lowery}}<br />
{{Submission|Definition of and Requirements For RDF Validation|Solbrig}}<br />
{{Validation: requirements and approaches|Reynolds}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RdfValidationWorkshop/Papers&diff=67150RdfValidationWorkshop/Papers2013-07-08T17:50:39Z<p>Hsolbrig: Created page with "{| class="wikitable sortable" border="1" ! Title !! Authors !! Category !! Summary !! Assignment |- {{Submission|Dublin Core Application Profiles<br/>Separating Validation from S…"</p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|Coyle and Baker}}<br />
{{Submission|Bounds: Expressing Reservations about Incoming Data|Skjæveland and Stolpe}}<br />
{{Submission|RDF Validation requirements for data about products, services and companies|Harrison}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=RDF_Validation&diff=67149RDF Validation2013-07-08T17:46:24Z<p>Hsolbrig: Created page with "{| class="wikitable sortable" border="1" ! Title !! Authors !! Category !! Summary !! Assignment |- {{Submission|Dublin Core Application Profiles<br/>Separating Validation from S…"</p>
<hr />
<div>{| class="wikitable sortable" border="1"<br />
! Title !! Authors !! Category !! Summary !! Assignment<br />
|-<br />
{{Submission|Dublin Core Application Profiles<br/>Separating Validation from Semantics|Coyle and Baker|||}}<br />
|}</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67148Template:Submission2013-07-08T17:46:13Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| '''<center>{{{1}}}</center>''' || {{{2}}} || {{{3|(none)}}} || {{{4|}}} || {{{5|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67147Template:Submission2013-07-08T17:41:43Z<p>Hsolbrig: </p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| {{{1}}} || {{{2}}} || {{{3|(none)}}} || {{{4|}}} || {{{5|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=Template:Submission&diff=67146Template:Submission2013-07-08T17:38:38Z<p>Hsolbrig: Created page with "<noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage: <nowiki>{{Submission|<title>|<authors>|[<category>]|[<summary>]|[…"</p>
<hr />
<div><noinclude>Submission template - identify title, authors, category, brief summary and review assignment. Usage:<br />
<nowiki>{{Submission|<title>|<authors>|[<category>]|[<summary>]|[<assignment>]}}</nowiki><br />
</noinclude><includeonly>|-<br />
| {{{1}}} | {{{2}}} | {{{3|(none)}}} | {{{4|}}} | {{{5|}}}</includeonly></div>Hsolbrighttps://www.w3.org/wiki/index.php?title=HCLS/ClinicalObservationsInteroperability/TermInfo&diff=61513HCLS/ClinicalObservationsInteroperability/TermInfo2012-10-15T20:46:22Z<p>Hsolbrig: /* Alternative */</p>
<hr />
<div>Structured clinical data is often viewed as being distributed between two "domains" (also called "views," "perspectives," "layers," "components," etc.) For the purposes of this discussion, we refer to those two "component parts of a fully-formed semantic utterance of clinical data" through by visualizing them as being distributed between two models: an Information Model and a Terminology Model. Note that the term "model" is used rather specifically in the context of this discussion for the purposes of building a concrete example, the terms Information Model and Terminology Model refer to specific, well-defined model, i.e. the HL7 RIM and the SNOMED-CT models. However the concepts of Information Model and Terminology Model in the larger discussion of the full representation of a fully-formed semantic utterance need not be restricted to a single Information Model or single Terminology Model. The critical feature about the separation of the two components is that each contains its own semantics, i.e. its own concepts, relationships, etc. In general, the Information Model expresses a network of generic concepts such roles, actions, observations and their inter-relationships, etc. -- this collection of information (small"i") is also often referred to as "meta-data" or "contextual knowledge." In contrast, the information (small "i") represented by the concepts, relationships, etc. in theTerminology Model provides specific "instance-level" descriptions of higher-order constructs. It is often heavily reliant on "is-a" and "a-part-of" relationships between concepts, and is sometimes referred to as the "data layer" or "definitional knowledge model." This is the conceptual view of the world, a view in which the Information and Terminology Models provide complementary semantics and therefore at least implicitly are clearly, cleanly, and consistently related to each other via some sort of "binding interface.<br />
<br />
Conceptual View of the relationship between Information and Terminology models (hover over graphic for legend).<br />
<br />
[[Image:InformationTerminologyConceptual.png|600px|Figure 1 -- Conceptual view -- The figure shows the layers -- represented in a horizontal rather than vertical view -- as an Information Model and a Terminology Model. As previously mentioned, the Information Model can be thought of as a meta-data model which defines higher-level constructs such as Roles, Observations and their inter-relationships, etc. In contrast, the Terminology Model defines more granular "instance-level data" that, in turn, "bind" to specific constructs in the Information Model to provide those concepts with specific clarifications, context, etc. In the ideal, conceptual world, the boundary between the semantics expressed in each of the two models is well-defined and stable. (NOTE: Examples of Information Models include the HL7 and openEHR Reference Models. The Terminology Model with the greatest level of semantic expressiveness is SNOMED. However, other terminology models such as LOINC also demonstate the binding showing above equally well.)]]<br />
<br />
Operationally, however, the semantic expressiveness of the two models often overlaps, i.e. a given semantic statement can often be partially (or even completely) represented using a number of different combinations of concepts from the Information and Terminology models with each representation selecting some concepts and constructs from an Information Model and others from a Terminology Model. Unfortunately, this overlap in the semantic expressiveness of the two models enables multiple organizations tasked with representing the same semantic utterance to produce representations that, when serialized for transport between systems (for example, to XML) are not interoperable (hover over graphic for legend).<br />
<br />
[[Image:InformationTerminologyOverlap.png|500px|Figure 2 -- Operational view: In certain circumstances (see the following Clinical Example), some (or even all) of the semantics for a given clinical statement can be expressed in both the Information and Terminology Models. As a result, diferent representations of the same clinical semantics can be generated depending on what is represented in the Information Model vs what is represented in the Terminology Model. This figure represents the overlap in the semantic expressiveness of the two models by depicting portions of the Terminology Model being "embedded" in the Information Model. As a result, the Conceptual view that pictured the semantic boundary between the two models as being both well defined and stable is, in fact, not true. As a result, semantically equivalent statements will not be semantically interoperable at a computational level because of differences in representations that are manifest as differences in the serialized wire formats of the various representations. ]]<br />
<br />
== Example: A clinical diagnosis based on multiple observations and relationships ==<br />
<br />
The following clinical diagnosis<br />
<br />
'''Grade 4 anaphylactic reaction to penicillin as evidenced by the combination of wheals (hives), acute respiratory distress (ARD) and systemic hypotension (LBP) following a penicillin injection'''<br />
<br />
can be represented in multiple ways depending on what semantic aspects of the overall statement one chooses to represent using a specific Information Model and its associated concepts and constructs vs the representation of the same semantics using concepts and constructs drawn from a particular Terminology Model. If done correctly, i.e. if the same "amount" of semantic content is <<explicitly>> represented in more than one representational scheme, the various representations would be viewed as clinical identical in terms of the information that they convey. Following the act of representing the semantic statement (the "design-time" form of the statement), each resulting complex construct must be serialiazed into some form of "byte stream" (usually XML, as will be used for the purposes of this discussion) for transmission between systems (the "run-time" form of the statement). Unfortunately, different design-time representations result in different run-time serializations with the high likelihood that two desing-time representations known to be semantically equivalent by human authors or reviewers will be analyzed to be <<computationally>> non-interoperable because the order of elements in XML is critical to automated determination of semantic equivalence.<br />
<br />
The following example uses the HL7 Reference Information Model and the SNOMED-CT Terminology Model to demonstrate both the problem -- i.e. different representations serialized using HL7's standard RIM-to-XML serialization protocol ("HL7 XML Implementation Technology Specification (XML ITS)) are not computationally interoperable from the perspective of semantic equivalence -- as well as to propose a solution using Semantic Web tools and technologies. Specifically, in the Unification section, we show how multiple design-time representations -- when expressed in RDF permit in the presence of pre-existing RDF representations of bot the RIM and SNOMED -- allow one to computationally determine semantic equivalence in spite of differences in run-time serializations that would otherwise be analyzed by machines as being non-interoperable, i.e. would not be recognized as semantically equivalent if standard XML parsing strategies were applied.<br />
<br />
== Semantics primarily represented in Information Model ==<br />
<br />
=== Atomized RIM XML ===<br />
[http://www.w3.org/2012/04/FHIR/terminfo/allV3-rimITS.xml The RIM/XML for the example diagnosis] can distribute individual SNOMED codes across multiple, finely-graunulated RIM Observation class instances. These instances are, in turn, semantically linked using Source ("inbound") and Target ("outbound") ActRelationships typeCode values. (NOTE: the semantics of the various tyepCode relationships are predefined in a vocabulary published by HL7 and controlled through the HL7 RIM Harmonization process to prevent semantic redundancy or "one-off" creation of rogue ActRelationship.typeCode values.)<br />
<nowiki> <content xsi:type="Observation" classCode="OBS" moodCode="EVN"><br />
...<value code="</nowiki>'''241938005'''<nowiki>" displayName="penicillin-induced anaphylaxis (disorder)" .../><br />
<inboundRelationship typeCode="SUBJ"><br />
<source ...><br />
<code code="SEV" displayName="Severity Observation" .../><value code="</nowiki>'''423132009'''<nowiki>" .../><br />
</source><br />
</inboundRelationship><br />
<outboundRelationship typeCode="EVID">...<br />
<code code="ASSERTION" .../><value code="</nowiki>'''247472004'''<nowiki>" displayName="weal (disorder)" .../>...<br />
</outboundRelationship><br />
... <!-- etc. for 373895009 (acute respiratory distress) and 45007003 (low blood pressure) --><br />
</content><br />
</nowiki><br />
<br />
=== Atomized RIM RDF ===<br />
[http://www.w3.org/2012/04/FHIR/terminfo/allV3.ttl Expressed as RDF (turtle)], this diagnosis captures the ActRelationships from the information model, but the semantics of the terminology are still just numeric literals:<br />
@@ captures weal, ARD, LBP, severity but not Substance Administration Act @@<br />
<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
_:dx ...<br />
rim:Observation.value [ dt:CD.code "</nowiki>'''241938005'''<nowiki>" ];<br />
rim:Act.inboundRelationship _:severity ;<br />
rim:Act.outboundRelationship _:weals, _:respDistress, _:lbp .<br />
<br />
# severity = 423132009 | grade 4 out of 5 |<br />
_:severity a rim:ActRelationship ; ...<br />
rim:ActRelationship.source [ rim:Observation.value [ dt:CD.code "</nowiki>'''423132009'''<nowiki>" ] ] .<br />
<br />
# has definitional manifestation = 247472004 | weal (disorder) |<br />
_:weals a rim:ActRelationship ; ...<br />
rim:ActRelationship.target [ rim:Observation.value [ dt:CD.code "</nowiki>'''247472004'''<nowiki>" ] ] .<br />
# etc. for 373895009 (acute respiratory distress) and 45007003 (low blood pressure)<br />
</nowiki><br />
<br />
== Semantics primarily represented in Terminology Model ==<br />
<br />
This same diagnosis can be expressed as a single Observation in the information model with a complex, post-coordinated SNOMED code. This SNOMED code fully specifies the semantics of the entire clinical statement and can thus be bound to a single instance of a RIM Observation class:<br />
<br />
241938005 | penicillin-induced anaphylaxis (disorder) | :<br />
246112005 | severity | = 423132009 | grade 4 out of 5 | ,<br />
363705008 | has definitional manifestation | = 247472004 | weal (disorder) | ,<br />
363705008 | has definitional manifestation | = 373895009 | acute respiratory distress | ,<br />
363705008 | has definitional manifestation | = 45007003 | low blood pressure (disorder) |<br />
<br />
=== Collected RIM RDF ===<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
_:dx ...<br />
rim:Observation.value [ dt:CD.code<br />
"</nowiki>'''241938005:246112005=423132009,363705008=247472004,...'''<nowiki>" ].<br />
</nowiki><br />
<br />
This representation represents a "transfer" of much of semantic expressiveness from the Information Model (RIM) to the Terminology Model (SNOMED-CT). This transfer is evidenced by the marked <<decrease>> in the number of RIM instances required along with the concomitant <<increase>> in the complexity of the SNOMED code. From a clinical perspective, both representations are semantically equivalent.<br />
<br />
It is important to note that two "design-time" representations developed above --the "poles" of different approaches -- are but two of a fairly large number of semantically equivalent but representationally different constructs that could be developed using the RIM and SNOMED-CT. An intermediate representation between the two poles is presented below to emphasize the heterogenous and ultimately somewhat stylized nature of the various representations. The important point is that each design-time representation is semantically equivalent, but that because each representation would result in a different "run-time" XML serialization, automated processing of the various run-time artifacts would often determine them to be non-interoperable, i.e. would not recognize their semantic equivalence.<br />
<br />
== Intermediate representations ==<br />
<br />
The completely Atomized and completely Collected representations of the diagnosis represent two poles of a continuum of possible expressions.<br />
A representation with multiple Observations for weal, ARD, LBP but additional Observations for Grade IV anaphylaxis, single Substance Administration Act is a reasonable example between these poles:<br />
<br />
=== Intermediate RIM RDF ===<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
_:dx ...<br />
rim:Observation.value [ dt:CD.code "</nowiki>'''241938005:246112005=423132009'''<nowiki>" ];<br />
rim:Act.outboundRelationship _:weals, _:respDistress, _:lbp .<br />
<br />
# has definitional manifestation = 247472004 | weal (disorder) |<br />
_:weals a rim:ActRelationship ; ...<br />
rim:ActRelationship.target [ rim:Observation.value [ dt:CD.code "</nowiki>'''247472004'''<nowiki>" ] ] .<br />
# etc. for 373895009 (acute respiratory distress) and 45007003 (low blood pressure)<br />
</nowiki><br />
<br />
<br />
== Unifying these representations ==<br />
<br />
We can Add an extra property to each Observation which captures the semantics of the potentially complex terminology code.<br />
In the case of SNOMED's compositional terms, the semantics can vary from simply recapitulating a soul number to creating complex objects with their own properties and attributes.<br />
Mechanically, this involves micro-parsing the '''dt:CD.code''' attributes and attaching them to the Observations via a new '''terminfo:termcode''' arc.<br />
Applying this to the Collected representation, we see a termcode which may be reasoned about with OWL or SPARQL:<br />
<br />
=== Annotated collected RIM RDF ===<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
_:dx ...<br />
rim:Observation.value [ dt:CD.code<br />
"</nowiki>'''241938005:246112005=423132009,363705008=247472004,...'''<nowiki>" ];<br />
terminfo:termcode [<br />
a <http://www.ihtsdo.org/SCT_241938005> ;<br />
<http://www.ihtsdo.org/SCT_246112005> <http://www.ihtsdo.org/SCT_423132009> ;<br />
<http://www.ihtsdo.org/SCT_363705008> <http://www.ihtsdo.org/SCT_247472004><br />
# etc. for 363705008=373895009 and 363705008=45007003<br />
];<br />
</nowiki><br />
<br />
=== Alternative ===<br />
<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
@prefix sctid: <http://www.ihtsdo.org/SCT_> .<br />
_:dx ...<br />
rim:Observation.value dt:CD.code [<br />
skos:notation "</nowiki>'''241938005:246112005=423132009,363705008=247472004,...'''<nowiki>";<br />
a sctid:241938005 ;<br />
sctid:246112005 sctid:423132009 ;<br />
sctid:363705008 sctid:247472004<br />
# etc. for 363705008=373895009 and 363705008=45007003<br />
] .<br />
</nowiki><br />
<br />
We can now write OWL or SPARQL rules to examine the predicates associated with the 12 axes of SNOMED (e.g. SCT_246112005, SCT_363705008) to map them into their equivalent expressions in the information model.<br />
<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
CONSTRUCT {<br />
?diag rim:Act.outboundRelationship [<br />
a rim:ActRelationship ; ...<br />
rim:ActRelationship.target [ rim:Observation.value [ dt:CD.code "</nowiki>'''?code'''<nowiki>" ] ]<br />
} WHERE {<br />
?diag rim:Act.outboundRelationship [<br />
terminfo:termcode [<br />
<http://www.ihtsdo.org/SCT_363705008> ?codeURL<br />
]<br />
]<br />
BIND (substr(?codeURL, 26) AS ?code)<br />
}<br />
</nowiki><br />
<br />
== Reasoning with the terminology model ==<br />
<br />
SNOMED codes have a '''normalized form'''; the normalized form of the above SNOMED is:<br />
<br />
39579001 | anaphylaxis | :<br />
246075003 | causative agent | = 373270004 | penicillin -class of antibiotic- | ,<br />
246112005 | severity | = 423132009 | grade 4 out of 5 |,<br />
263502005 | clinical course | = 424124008 | sudden onset AND/OR short duration | ,<br />
363705008 | has definitional manifestation | = ( 247472004 | weal |: <br />
{ 116676008 | associated morphology | = 1806006 | eruption | ,<br />
363698007 | finding site | = 39937001 | skin structure | }),<br />
363705008 | has definitional manifestation | = ( 373895009 | acute respiratory distress | :<br />
363698007 | finding site | = 20139000 | structure of respiratory system | ,<br />
363714003 | interprets | = 248546008 | ease of respiration | ,<br />
363714003 | interprets | = 278844005 | general clinical state | ) ,<br />
363705008 | has definitional manifestation | = ( 45007003 | low blood pressure | : <br />
363698007 | finding site | = 281159003 | systemic arterial structure | <br />
)<br />
<br />
Having the SNOMED terms in the same domain of discourse as the HL7 V3 allows us to use OWL for SNOMED gives RDF tooling access to this and even more rich information.<br />
Following are some excerpts from the relevant OWL axioms:<br />
<br />
<nowiki><br />
<owl:Class rdf:about="SCT_298138003"><br />
<rdfs:label xml:lang="en">Micropapular weal (disorder)</rdfs:label><br />
<rdfs:subClassOf><owl:Class><br />
<owl:intersectionOf rdf:parseType="Collection"><br />
<owl:Class rdf:about="SCT_247472004"/><br />
<owl:Restriction><br />
<owl:onProperty rdf:resource="RoleGroup"/><br />
<owl:someValuesFrom><br />
<owl:Class><br />
<owl:intersectionOf rdf:parseType="Collection"><br />
<owl:Restriction><br />
<owl:onProperty rdf:resource="SCT_363698007"/><br />
<owl:someValuesFrom rdf:resource="SCT_39937001"/><br />
</owl:Restriction><br />
<owl:Restriction><br />
<owl:onProperty rdf:resource="SCT_116676008"/><br />
<owl:someValuesFrom rdf:resource="SCT_47725002"/><br />
</owl:Restriction><br />
</owl:intersectionOf><br />
</owl:Class><br />
</owl:someValuesFrom><br />
</owl:Restriction><br />
</owl:intersectionOf><br />
</owl:Class></rdfs:subClassOf><br />
</owl:Class><br />
</nowiki><br />
<br />
These axioms allow us to query richer representations of and/or relationships to the original diagnostic statement, e.g. associations between drug administration and other reparatory or cardiovascular symptoms.<br />
<br />
== Related ==<br />
<br />
* [http://www.hl7.org/Special/Committees/terminfo/index.cfm HL7 terminfo WG].</div>Hsolbrighttps://www.w3.org/wiki/index.php?title=HCLS/ClinicalObservationsInteroperability/TermInfo&diff=61512HCLS/ClinicalObservationsInteroperability/TermInfo2012-10-15T20:45:45Z<p>Hsolbrig: /* Alternative */</p>
<hr />
<div>Structured clinical data is often viewed as being distributed between two "domains" (also called "views," "perspectives," "layers," "components," etc.) For the purposes of this discussion, we refer to those two "component parts of a fully-formed semantic utterance of clinical data" through by visualizing them as being distributed between two models: an Information Model and a Terminology Model. Note that the term "model" is used rather specifically in the context of this discussion for the purposes of building a concrete example, the terms Information Model and Terminology Model refer to specific, well-defined model, i.e. the HL7 RIM and the SNOMED-CT models. However the concepts of Information Model and Terminology Model in the larger discussion of the full representation of a fully-formed semantic utterance need not be restricted to a single Information Model or single Terminology Model. The critical feature about the separation of the two components is that each contains its own semantics, i.e. its own concepts, relationships, etc. In general, the Information Model expresses a network of generic concepts such roles, actions, observations and their inter-relationships, etc. -- this collection of information (small"i") is also often referred to as "meta-data" or "contextual knowledge." In contrast, the information (small "i") represented by the concepts, relationships, etc. in theTerminology Model provides specific "instance-level" descriptions of higher-order constructs. It is often heavily reliant on "is-a" and "a-part-of" relationships between concepts, and is sometimes referred to as the "data layer" or "definitional knowledge model." This is the conceptual view of the world, a view in which the Information and Terminology Models provide complementary semantics and therefore at least implicitly are clearly, cleanly, and consistently related to each other via some sort of "binding interface.<br />
<br />
Conceptual View of the relationship between Information and Terminology models (hover over graphic for legend).<br />
<br />
[[Image:InformationTerminologyConceptual.png|600px|Figure 1 -- Conceptual view -- The figure shows the layers -- represented in a horizontal rather than vertical view -- as an Information Model and a Terminology Model. As previously mentioned, the Information Model can be thought of as a meta-data model which defines higher-level constructs such as Roles, Observations and their inter-relationships, etc. In contrast, the Terminology Model defines more granular "instance-level data" that, in turn, "bind" to specific constructs in the Information Model to provide those concepts with specific clarifications, context, etc. In the ideal, conceptual world, the boundary between the semantics expressed in each of the two models is well-defined and stable. (NOTE: Examples of Information Models include the HL7 and openEHR Reference Models. The Terminology Model with the greatest level of semantic expressiveness is SNOMED. However, other terminology models such as LOINC also demonstate the binding showing above equally well.)]]<br />
<br />
Operationally, however, the semantic expressiveness of the two models often overlaps, i.e. a given semantic statement can often be partially (or even completely) represented using a number of different combinations of concepts from the Information and Terminology models with each representation selecting some concepts and constructs from an Information Model and others from a Terminology Model. Unfortunately, this overlap in the semantic expressiveness of the two models enables multiple organizations tasked with representing the same semantic utterance to produce representations that, when serialized for transport between systems (for example, to XML) are not interoperable (hover over graphic for legend).<br />
<br />
[[Image:InformationTerminologyOverlap.png|500px|Figure 2 -- Operational view: In certain circumstances (see the following Clinical Example), some (or even all) of the semantics for a given clinical statement can be expressed in both the Information and Terminology Models. As a result, diferent representations of the same clinical semantics can be generated depending on what is represented in the Information Model vs what is represented in the Terminology Model. This figure represents the overlap in the semantic expressiveness of the two models by depicting portions of the Terminology Model being "embedded" in the Information Model. As a result, the Conceptual view that pictured the semantic boundary between the two models as being both well defined and stable is, in fact, not true. As a result, semantically equivalent statements will not be semantically interoperable at a computational level because of differences in representations that are manifest as differences in the serialized wire formats of the various representations. ]]<br />
<br />
== Example: A clinical diagnosis based on multiple observations and relationships ==<br />
<br />
The following clinical diagnosis<br />
<br />
'''Grade 4 anaphylactic reaction to penicillin as evidenced by the combination of wheals (hives), acute respiratory distress (ARD) and systemic hypotension (LBP) following a penicillin injection'''<br />
<br />
can be represented in multiple ways depending on what semantic aspects of the overall statement one chooses to represent using a specific Information Model and its associated concepts and constructs vs the representation of the same semantics using concepts and constructs drawn from a particular Terminology Model. If done correctly, i.e. if the same "amount" of semantic content is <<explicitly>> represented in more than one representational scheme, the various representations would be viewed as clinical identical in terms of the information that they convey. Following the act of representing the semantic statement (the "design-time" form of the statement), each resulting complex construct must be serialiazed into some form of "byte stream" (usually XML, as will be used for the purposes of this discussion) for transmission between systems (the "run-time" form of the statement). Unfortunately, different design-time representations result in different run-time serializations with the high likelihood that two desing-time representations known to be semantically equivalent by human authors or reviewers will be analyzed to be <<computationally>> non-interoperable because the order of elements in XML is critical to automated determination of semantic equivalence.<br />
<br />
The following example uses the HL7 Reference Information Model and the SNOMED-CT Terminology Model to demonstrate both the problem -- i.e. different representations serialized using HL7's standard RIM-to-XML serialization protocol ("HL7 XML Implementation Technology Specification (XML ITS)) are not computationally interoperable from the perspective of semantic equivalence -- as well as to propose a solution using Semantic Web tools and technologies. Specifically, in the Unification section, we show how multiple design-time representations -- when expressed in RDF permit in the presence of pre-existing RDF representations of bot the RIM and SNOMED -- allow one to computationally determine semantic equivalence in spite of differences in run-time serializations that would otherwise be analyzed by machines as being non-interoperable, i.e. would not be recognized as semantically equivalent if standard XML parsing strategies were applied.<br />
<br />
== Semantics primarily represented in Information Model ==<br />
<br />
=== Atomized RIM XML ===<br />
[http://www.w3.org/2012/04/FHIR/terminfo/allV3-rimITS.xml The RIM/XML for the example diagnosis] can distribute individual SNOMED codes across multiple, finely-graunulated RIM Observation class instances. These instances are, in turn, semantically linked using Source ("inbound") and Target ("outbound") ActRelationships typeCode values. (NOTE: the semantics of the various tyepCode relationships are predefined in a vocabulary published by HL7 and controlled through the HL7 RIM Harmonization process to prevent semantic redundancy or "one-off" creation of rogue ActRelationship.typeCode values.)<br />
<nowiki> <content xsi:type="Observation" classCode="OBS" moodCode="EVN"><br />
...<value code="</nowiki>'''241938005'''<nowiki>" displayName="penicillin-induced anaphylaxis (disorder)" .../><br />
<inboundRelationship typeCode="SUBJ"><br />
<source ...><br />
<code code="SEV" displayName="Severity Observation" .../><value code="</nowiki>'''423132009'''<nowiki>" .../><br />
</source><br />
</inboundRelationship><br />
<outboundRelationship typeCode="EVID">...<br />
<code code="ASSERTION" .../><value code="</nowiki>'''247472004'''<nowiki>" displayName="weal (disorder)" .../>...<br />
</outboundRelationship><br />
... <!-- etc. for 373895009 (acute respiratory distress) and 45007003 (low blood pressure) --><br />
</content><br />
</nowiki><br />
<br />
=== Atomized RIM RDF ===<br />
[http://www.w3.org/2012/04/FHIR/terminfo/allV3.ttl Expressed as RDF (turtle)], this diagnosis captures the ActRelationships from the information model, but the semantics of the terminology are still just numeric literals:<br />
@@ captures weal, ARD, LBP, severity but not Substance Administration Act @@<br />
<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
_:dx ...<br />
rim:Observation.value [ dt:CD.code "</nowiki>'''241938005'''<nowiki>" ];<br />
rim:Act.inboundRelationship _:severity ;<br />
rim:Act.outboundRelationship _:weals, _:respDistress, _:lbp .<br />
<br />
# severity = 423132009 | grade 4 out of 5 |<br />
_:severity a rim:ActRelationship ; ...<br />
rim:ActRelationship.source [ rim:Observation.value [ dt:CD.code "</nowiki>'''423132009'''<nowiki>" ] ] .<br />
<br />
# has definitional manifestation = 247472004 | weal (disorder) |<br />
_:weals a rim:ActRelationship ; ...<br />
rim:ActRelationship.target [ rim:Observation.value [ dt:CD.code "</nowiki>'''247472004'''<nowiki>" ] ] .<br />
# etc. for 373895009 (acute respiratory distress) and 45007003 (low blood pressure)<br />
</nowiki><br />
<br />
== Semantics primarily represented in Terminology Model ==<br />
<br />
This same diagnosis can be expressed as a single Observation in the information model with a complex, post-coordinated SNOMED code. This SNOMED code fully specifies the semantics of the entire clinical statement and can thus be bound to a single instance of a RIM Observation class:<br />
<br />
241938005 | penicillin-induced anaphylaxis (disorder) | :<br />
246112005 | severity | = 423132009 | grade 4 out of 5 | ,<br />
363705008 | has definitional manifestation | = 247472004 | weal (disorder) | ,<br />
363705008 | has definitional manifestation | = 373895009 | acute respiratory distress | ,<br />
363705008 | has definitional manifestation | = 45007003 | low blood pressure (disorder) |<br />
<br />
=== Collected RIM RDF ===<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
_:dx ...<br />
rim:Observation.value [ dt:CD.code<br />
"</nowiki>'''241938005:246112005=423132009,363705008=247472004,...'''<nowiki>" ].<br />
</nowiki><br />
<br />
This representation represents a "transfer" of much of semantic expressiveness from the Information Model (RIM) to the Terminology Model (SNOMED-CT). This transfer is evidenced by the marked <<decrease>> in the number of RIM instances required along with the concomitant <<increase>> in the complexity of the SNOMED code. From a clinical perspective, both representations are semantically equivalent.<br />
<br />
It is important to note that two "design-time" representations developed above --the "poles" of different approaches -- are but two of a fairly large number of semantically equivalent but representationally different constructs that could be developed using the RIM and SNOMED-CT. An intermediate representation between the two poles is presented below to emphasize the heterogenous and ultimately somewhat stylized nature of the various representations. The important point is that each design-time representation is semantically equivalent, but that because each representation would result in a different "run-time" XML serialization, automated processing of the various run-time artifacts would often determine them to be non-interoperable, i.e. would not recognize their semantic equivalence.<br />
<br />
== Intermediate representations ==<br />
<br />
The completely Atomized and completely Collected representations of the diagnosis represent two poles of a continuum of possible expressions.<br />
A representation with multiple Observations for weal, ARD, LBP but additional Observations for Grade IV anaphylaxis, single Substance Administration Act is a reasonable example between these poles:<br />
<br />
=== Intermediate RIM RDF ===<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
_:dx ...<br />
rim:Observation.value [ dt:CD.code "</nowiki>'''241938005:246112005=423132009'''<nowiki>" ];<br />
rim:Act.outboundRelationship _:weals, _:respDistress, _:lbp .<br />
<br />
# has definitional manifestation = 247472004 | weal (disorder) |<br />
_:weals a rim:ActRelationship ; ...<br />
rim:ActRelationship.target [ rim:Observation.value [ dt:CD.code "</nowiki>'''247472004'''<nowiki>" ] ] .<br />
# etc. for 373895009 (acute respiratory distress) and 45007003 (low blood pressure)<br />
</nowiki><br />
<br />
<br />
== Unifying these representations ==<br />
<br />
We can Add an extra property to each Observation which captures the semantics of the potentially complex terminology code.<br />
In the case of SNOMED's compositional terms, the semantics can vary from simply recapitulating a soul number to creating complex objects with their own properties and attributes.<br />
Mechanically, this involves micro-parsing the '''dt:CD.code''' attributes and attaching them to the Observations via a new '''terminfo:termcode''' arc.<br />
Applying this to the Collected representation, we see a termcode which may be reasoned about with OWL or SPARQL:<br />
<br />
=== Annotated collected RIM RDF ===<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
_:dx ...<br />
rim:Observation.value [ dt:CD.code<br />
"</nowiki>'''241938005:246112005=423132009,363705008=247472004,...'''<nowiki>" ];<br />
terminfo:termcode [<br />
a <http://www.ihtsdo.org/SCT_241938005> ;<br />
<http://www.ihtsdo.org/SCT_246112005> <http://www.ihtsdo.org/SCT_423132009> ;<br />
<http://www.ihtsdo.org/SCT_363705008> <http://www.ihtsdo.org/SCT_247472004><br />
# etc. for 363705008=373895009 and 363705008=45007003<br />
];<br />
</nowiki><br />
<br />
=== Alternative ===<br />
<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
@prefix sctid: <http://www.ihtsdo.org/SCT_> .<br />
_:dx ...<br />
rim:Observation.value dt:CD.code [<br />
skos:notation "</nowiki>'''241938005:246112005=423132009,363705008=247472004,...'''<nowiki>";<br />
a sctid:241938005 ;<br />
sctid:246112005 sctid:423132009 ;<br />
sctid:363705008 sctid:247472004<br />
# etc. for 363705008=373895009 and 363705008=45007003<br />
] .<br />
</nowiki><br />
<br />
We can now write OWL or SPARQL rules to examine the predicates associated with the 12 axes of SNOMED (e.g. SCT_246112005, SCT_363705008) to map them into their equivalent expressions in the information model.<br />
<br />
<nowiki> # penicillin-induced anaphylaxis (disorder) :<br />
CONSTRUCT {<br />
?diag rim:Act.outboundRelationship [<br />
a rim:ActRelationship ; ...<br />
rim:ActRelationship.target [ rim:Observation.value [ dt:CD.code "</nowiki>'''?code'''<nowiki>" ] ]<br />
} WHERE {<br />
?diag rim:Act.outboundRelationship [<br />
terminfo:termcode [<br />
<http://www.ihtsdo.org/SCT_363705008> ?codeURL<br />
]<br />
]<br />
BIND (substr(?codeURL, 26) AS ?code)<br />
}<br />
</nowiki><br />
<br />
== Reasoning with the terminology model ==<br />
<br />
SNOMED codes have a '''normalized form'''; the normalized form of the above SNOMED is:<br />
<br />
39579001 | anaphylaxis | :<br />
246075003 | causative agent | = 373270004 | penicillin -class of antibiotic- | ,<br />
246112005 | severity | = 423132009 | grade 4 out of 5 |,<br />
263502005 | clinical course | = 424124008 | sudden onset AND/OR short duration | ,<br />
363705008 | has definitional manifestation | = ( 247472004 | weal |: <br />
{ 116676008 | associated morphology | = 1806006 | eruption | ,<br />
363698007 | finding site | = 39937001 | skin structure | }),<br />
363705008 | has definitional manifestation | = ( 373895009 | acute respiratory distress | :<br />
363698007 | finding site | = 20139000 | structure of respiratory system | ,<br />
363714003 | interprets | = 248546008 | ease of respiration | ,<br />
363714003 | interprets | = 278844005 | general clinical state | ) ,<br />
363705008 | has definitional manifestation | = ( 45007003 | low blood pressure | : <br />
363698007 | finding site | = 281159003 | systemic arterial structure | <br />
)<br />
<br />
Having the SNOMED terms in the same domain of discourse as the HL7 V3 allows us to use OWL for SNOMED gives RDF tooling access to this and even more rich information.<br />
Following are some excerpts from the relevant OWL axioms:<br />
<br />
<nowiki><br />
<owl:Class rdf:about="SCT_298138003"><br />
<rdfs:label xml:lang="en">Micropapular weal (disorder)</rdfs:label><br />
<rdfs:subClassOf><owl:Class><br />
<owl:intersectionOf rdf:parseType="Collection"><br />
<owl:Class rdf:about="SCT_247472004"/><br />
<owl:Restriction><br />
<owl:onProperty rdf:resource="RoleGroup"/><br />
<owl:someValuesFrom><br />
<owl:Class><br />
<owl:intersectionOf rdf:parseType="Collection"><br />
<owl:Restriction><br />
<owl:onProperty rdf:resource="SCT_363698007"/><br />
<owl:someValuesFrom rdf:resource="SCT_39937001"/><br />
</owl:Restriction><br />
<owl:Restriction><br />
<owl:onProperty rdf:resource="SCT_116676008"/><br />
<owl:someValuesFrom rdf:resource="SCT_47725002"/><br />
</owl:Restriction><br />
</owl:intersectionOf><br />
</owl:Class><br />
</owl:someValuesFrom><br />
</owl:Restriction><br />
</owl:intersectionOf><br />
</owl:Class></rdfs:subClassOf><br />
</owl:Class><br />
</nowiki><br />
<br />
These axioms allow us to query richer representations of and/or relationships to the original diagnostic statement, e.g. associations between drug administration and other reparatory or cardiovascular symptoms.<br />
<br />
== Related ==<br />
<br />
* [http://www.hl7.org/Special/Committees/terminfo/index.cfm HL7 terminfo WG].</div>Hsolbrig