Date: Fri, 29 Mar 2024 13:27:43 +0000 (UTC) Message-ID: <1162830934.1.1711718863755@81eae2d3a063> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_853905472.1711718863742" ------=_Part_0_853905472.1711718863742 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
(By Koray Atalag)
To determine a consistent and predictable URL scheme for openEHR specifi= cations and other related artefacts (e.g. ITS, conformance, XML Schemas etc= .)
We would then like to apply for openehr-specs namespace= from http://identifiers.org for persistent identification of these op= enEHR artefacts.
Firstly for internal consistency. Also identifiers.org is an impo= rtant registry for enabling persistent identifiers for the Semantic Web in = computational modeling and bioinformatics communities. We can use these ide= ntifiers for semantic annotation of archetypes and associated data resource= s (e.g. for example linking archetypes or instance data to the version of s= pecs they conform to in a triple-store). They also facilitate discovery etc= . on the Net.
We are also looking at getting openehr-models namespace= for models (e.g. openEHR models) which will then allow us to give unique i= dentifiers to each clinical model anywhere on the Net. That's a separate pr= oposal.
We need consistent and predictable URL for specs - so that automated map= pings can be provided from identifier.org (instead of manual mapping of= an URI to a spec at an arbitrary URL at openehr.org)
Suggested openehr.org specs URL designation (which is very close to cur= rent scheme:
http://openehr.org/releases=
/COMPONENT[BASE, RM, AM, =
QUERY, TERM, SM, CDS, ITS, CONF]/ |
---|
For example: http://ww= w.openehr.org/releases/RM/1.0.3/ehr.html (This is a= valid URL currently)
We currently have other inconsistent URL schemes (for older releases) su= ch as:
http://www.openehr.org/releas=
es/1.0.1/architecture/rm/ehr_im.pdf
http://openehr.org/releases/1.0.2/architecture/rm/ehr_im.pdf
http://www.openehr.org/programs=
/specification/releases/1.0.2
NOTE: The only proposed changes to current scheme is I = have now included [ITS]=3DImplementation Technology Specification and = [CONF]=3DConformance as a COMPONENT of spec although it is a separate he= ading on our current s= pecs page. I think the namespace "openehr-specs" is broader than what w= e assume on this page.
If we go with the suggested URL designation, people at identifiers.org<= /a> can write automatic mappings that redirect to openehr.org. They need m= appings because they can't use identifiers that have "/" in them so it need= s to be substituted with "." or "-" etc.
So taking the given example the corresponding identifiers.org URI w= ill be:
http://identif= iers.org/openehr-specs/RM-1.0.3-ehr | >>>automatic mapping>>><= /span> | http://www.openehr.org/releases/RM/1.0.3/eh= r.html |
---|
NOTE: Another suggestion to consider is whether we want= to provide alternate formats for our specs (e.g. html, pdf, open doc etc.)= . In that case we may want to redirect each spec to an auto-generated place= holder page that would provide links to html, pdf etc. specs. This is commo= nly used for other specs on identifiers.org; see: http://co.mbine.org/standards/specification-infrastructure=
Example: