This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR RDF Mapping - Potential Strategies"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
== Option 2: JSON-LD with @lists == | == Option 2: JSON-LD with @lists == | ||
| − | + | Description: | |
| + | * Slides 8-10 of http://dbooth.org/2015/fhir/json-ld/fhir-in-json-ld.pdf | ||
== Option 3: JSON-LD brief/verbose use of @context == | == Option 3: JSON-LD brief/verbose use of @context == | ||
Description: https://lists.w3.org/Archives/Public/public-semweb-lifesci/2015Mar/0064.html | Description: https://lists.w3.org/Archives/Public/public-semweb-lifesci/2015Mar/0064.html | ||
Revision as of 14:53, 24 March 2015
- Return to ITS Main Page | ITS RDF Minutes 2014 | All ITS RDF Pages | ITS Email Archives | W3C HCLS Email Archives | Issues List
Option 1: Custom Mapping with ShEx
In practice, this would likely be mostly generated from the FHIR specification (as EricP and Josh Mandel did), with some customizations to produce the desired RDF result.
Description:
Option 2: JSON-LD with @lists
Description:
- Slides 8-10 of http://dbooth.org/2015/fhir/json-ld/fhir-in-json-ld.pdf
Option 3: JSON-LD brief/verbose use of @context
Description: https://lists.w3.org/Archives/Public/public-semweb-lifesci/2015Mar/0064.html
