# The Specifications link is dead

**URL:** https://discourse.openehr.org/t/the-specifications-link-is-dead/755
**Category:** Site Feedback
**Created:** [7 June 2020 22:36 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755 "2020-06-07T22:36:00Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![Nathan](https://discourse.openehr.org/user_avatar/discourse.openehr.org/nathan/32/702_2.png) [@Nathan](https://discourse.openehr.org/u/Nathan)
#### Post date: [7 June 2020 22:36 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755/1 "2020-06-07T22:36:00Z")

</div>

![image](https://discourse.openehr.org/uploads/default/original/1X/a1a725865a3c39201b01ac491265b59d2312d706.png)  
points to [https://discourse.openehr.org/c/site-feedback/vdo](https://discourse.openehr.org/c/site-feedback/vdo) - which doesn’t allow access to me. Is that intentional?

It may be better suited to being a published page - see:

> **[Page Publishing](https://meta.discourse.org/t/page-publishing/151971)**
>
> Page Publishing Page Publishing allows Staff/Admin users the ability to convert a topic into a static standalone page with support for custom styling. This is similar to the pattern in use for Terms of Service or the Privacy Policy pages. Note that...

---

<div class="post-metadata">

### Author: ![pablo](https://discourse.openehr.org/user_avatar/discourse.openehr.org/pablo/32/3505_2.png) [@pablo](https://discourse.openehr.org/u/pablo)
#### Post date: [8 June 2020 03:08 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755/2 "2020-06-08T03:08:50Z")

</div>

The link should be [https://specifications.openehr.org/](https://specifications.openehr.org/)

There are many dead links in the website, it needs some love.

---

<div class="post-metadata">

### Author: ![Nathan](https://discourse.openehr.org/user_avatar/discourse.openehr.org/nathan/32/702_2.png) [@Nathan](https://discourse.openehr.org/u/Nathan)
#### Post date: [8 June 2020 04:34 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755/3 "2020-06-08T04:34:41Z")

</div>

Doesn’t look too flash on mobile either! C’mon @marcusbaw you’d better make me an admin to harness my OCD ways…

---

<div class="post-metadata">

### Author: ![marcusbaw](https://discourse.openehr.org/user_avatar/discourse.openehr.org/marcusbaw/32/4792_2.png) [@marcusbaw](https://discourse.openehr.org/u/marcusbaw)
#### Post date: [8 June 2020 12:11 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755/4 "2020-06-08T12:11:44Z")

</div>

> [@pablo](#):
>
> link should be [https://specifications.openehr.org/](https://specifications.openehr.org/)

I’ve fixed the header link on the forum now

---

<div class="post-metadata">

### Author: ![marcusbaw](https://discourse.openehr.org/user_avatar/discourse.openehr.org/marcusbaw/32/4792_2.png) [@marcusbaw](https://discourse.openehr.org/u/marcusbaw)
#### Post date: [8 June 2020 12:14 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755/5 "2020-06-08T12:14:57Z")

</div>

> [@pablo](#):
>
> dead links in the website

I don’t control the website, but I can imagine managing a site that size there will be inevitably some dead links

> [@Nathan](#):
>
> Doesn’t look too flash on mobile either! C’mon @marcusbaw you’d better make me an admin to harness my OCD ways…

I don’t ‘own’ this server somaking you admin is not my decision. However, @thomas.beale I can highly recommend @Nathan’s expertise with Discourse servers and tweaking the look/feel/user experience - he’s done good work on [healthforum.nz](http://healthforum.nz) and [discourse.digitalhealth.net](http://discourse.digitalhealth.net)

---

<div class="post-metadata">

### Author: ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)
#### Post date: [8 June 2020 12:26 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755/6 "2020-06-08T12:26:27Z")

</div>

Are we talking about dead links in this site (Discourse) or in the main site?

The board is working currently on requirements for updating the main site. If there are any dead links, they can be reported to [webmaster@openehr.org](mailto:webmaster@openehr.org) or posted on [this jira project](https://openehr.atlassian.net/projects/WEB/issues).

---

<div class="post-metadata">

### Author: ![pablo](https://discourse.openehr.org/user_avatar/discourse.openehr.org/pablo/32/3505_2.png) [@pablo](https://discourse.openehr.org/u/pablo)
#### Post date: [8 June 2020 17:00 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755/7 "2020-06-08T17:00:32Z")

</div>

Yesterday I was clicking around on this spec and the links in the tables are most of them 404 [https://specifications.openehr.org/releases/CNF/latest/openehr\_platform\_conformance.html](https://specifications.openehr.org/releases/CNF/latest/openehr_platform_conformance.html)

---

<div class="post-metadata">

### Author: ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)
#### Post date: [8 June 2020 17:41 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755/8 "2020-06-08T17:41:25Z")

</div>

I discovered a link generation problem. It’s fixed now, but of course these ‘scripts’ will get replaced by something more modern from your / HighMed’s work 😉

---

<div class="post-metadata">

### Author: ![pablo](https://discourse.openehr.org/user_avatar/discourse.openehr.org/pablo/32/3505_2.png) [@pablo](https://discourse.openehr.org/u/pablo)
#### Post date: [8 June 2020 18:26 UTC](https://discourse.openehr.org/t/the-specifications-link-is-dead/755/9 "2020-06-08T18:26:03Z")

</div>

I guess those could be linked to the robot implementation [https://github.com/ehrbase/ehrbase/tree/develop/tests/robot](https://github.com/ehrbase/ehrbase/tree/develop/tests/robot) but I guess some README documentation is missing for anyone wanting to execute the tests.

Also I’m working on a load test tool for HiGHmed, that is not related with conformance, but could be used to test part of it [https://github.com/ppazos/testehr](https://github.com/ppazos/testehr)
