-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dead links on hear guidance document #7
Comments
Suggest use: http://www.hear.ac.uk/sites/default/files/HEAR%20Reference%20Pack%20Feb%202014_0.pdf |
Good in principle to use an up-to-date source maintained by others. Problem
is that it won't take account of any of our revised thinking.
Do you, Alan (or anyone) have access either (a) to whoever maintains the
documentation on the hear.ac.uk site (so we could feed them updates) or (b)
to the source materials for the document, so we could regenerate an updated
version? Or, of course, (c) the people who are responsible for hear.ac.uk?
Thanks
Simon
…On 12 January 2017 at 11:42, alanepaull ***@***.***> wrote:
Suggest use: http://www.hear.ac.uk/sites/default/files/HEAR%
20Reference%20Pack%20Feb%202014_0.pdf
This one is the most up-to-date (I think) version of the guidance
document. It's been renamed the Reference Pack.
Alternatively, consider using the more general:
http://www.hear.ac.uk/guidance.
This one leads to all the currently "official" HEAR materials.
Alan
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACkRh_3pRtXrge0j_yGJ-Sbs2_Qi3lbFks5rRhGqgaJpZM4Kps2T>
.
--
from Simon Grant +44 7710031657 (I'm "asimong" with many services)
|
As far as I am aware, it's the HEA that is formally responsible for the HEAR. I don't think we're in a position to update the Reference Pack - that's much more about non-technical implementation issues, management and organisation, than the HEAR XML data standard. The latter has always been seen as peripheral by the wider HEAR community. I have no knowledge of who in HEA is responsible - I did try to find out a while back, but rapidly hit a dead end. What's the precise nature of the Cetis remit? I doubt that it covers all the HEAR documentation, because I'm sure that Jisc doesn't have a remit for that. I've taken the liberty of changing the 1.1 spec draft to point to the HEAR website PDF, rather than my own website, because the alanpaull.co.uk bit is definitely wrong. Alan |
Thanks, Alan, your liberty is well taken :)
The issue to me is e.g. that the guidance document refers to the spec v
1.0c. At very least we would want it to refer to the new version. If there
is no one able and willing to maintain the document, I would suggest that a
much more helpful approach would be to (do the small amount of work to)
edit the document lightly and republish on our site. But if we can't find
the source, that might be difficult.
Simon
…On 12 January 2017 at 12:02, alanepaull ***@***.***> wrote:
As far as I am aware, it's the HEA that is formally responsible for the
HEAR. I don't think we're in a position to update the Reference Pack -
that's much more about non-technical implementation issues, management and
organisation, than the HEAR XML data standard. The latter has always been
seen as peripheral by the wider HEAR community. I have no knowledge of who
in HEA is responsible - I did try to find out a while back, but rapidly hit
a dead end.
What's the precise nature of the Cetis remit? I doubt that it covers *all*
the HEAR documentation, because I'm sure that Jisc doesn't have a remit for
that.
I've taken the liberty of changing the 1.1 spec draft to point to the HEAR
website PDF, rather than my own website, because the alanpaull.co.uk bit
is definitely wrong.
Alan
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACkRh6GpoyGmtHCySJfUKx9syBDhVg-fks5rRhZhgaJpZM4Kps2T>
.
--
from Simon Grant +44 7710031657 (I'm "asimong" with many services)
|
From @asimong on xcri repo
Currently links from the HEAR 1.0c Specification to the "HEAR Guidance Document" give 404, as they point to withdrawn page on server belonging to APS.
Please find an active copy and link to that.
The text was updated successfully, but these errors were encountered: