Is HL7 FHIR Specification suitable to be added as a new project?
Fragment of a discussion from Support/LiquidThreads
Hello, we generally don't translate websites here, so it would be quite hard. As they have a MediaWiki wiki, the easiest would be that they install Translate to translate the specification there, and then find a way to "transclude" the translated HTML into their website.
Hi Nemo,
Thanks first!
The FHIR website is just an exact representation of the FHIR specification and it/its content is the same as the whole specification.
- A zipped official copy of the FHIR specification (i.e., the full site not including the downloads) can be downloaded from here.
Broadly, the FHIR specification is broken up into 3 parts (See here):
- General documentation that describes how resources are defined, and gives background material including definitions of data types, codes, and the XML and JSON formats
- Implementation - how to use resources using REST, Messaging, as clinical documents, or in a service based architecture
- The resource list - a list of all the resources defined by FHIR. You can also get lists for clinical, administrative and infrastructural resources
The FHIR Wiki is a place where development processes, methodology and design decisions are documented.
- Implementers and others can also contribute to the wiki to provide additional guidance and supplemental information not found in the specification.
- Note that wiki content is not authoritative and is not relevant for determining conformance to the FHIR specification.
- As well, some wiki content may not be up to date with the most recent version of the FHIR specification.
Thanks agian.
Cheers,
This doesn't really change much.
- We don't generally translate websites as we don't generally translate books, manuals or specifications.
- The way the wiki is currently being used is not a divine order and is compatible with translation. Unless the specification "master" is already some structured [l10n] format, any translation system will require that the document is moved to the translation system/format and back. If the specs can be converted to YAML or JSON, they can as well be regularly sync'ed to wiki pages and translated there.