Am 01.03.2017 um 23:29 schrieb Antoine Isaac:
> Hi Kai, Karen, Tom
>
> Yes I agree we can consider it a finished document.
Great, so Thomas and I will prepare the static version and host it on a
new server (or with DCMI, if you prefer it).
> About the snapshot I also have an XML export from a while ago (August
> 2015). Is it good, should we upload it somewhere (I think there was a
> problem attaching files to the DCMI wiki, though).
What kind of XML are you talking about, Antoine? If it should be
published alongside the static version, just send it to me and I will
add it.
> We'd also need to make sure the PURL we've used still redirect to
> something meaningful:
> http://purl.org/net/rdf-application-profiles (used in our report)
> http://purl.org/net/rdf-validation (Thomas and Kai said they had used
> this one in papers)
We try to update the purls (I just created an internet archive account
and wrote them an email to restore my access to the purl domains I had,
let's keep fingers crossed that this works...)
@Thomas: I think you created the domains, anyway, do you still have
access? Otherwise, you should claim your domains, too, just go to
purl.org and follow instructions.
Cheers,
Kai
> Best,
>
> Antoine
>
> On 28/02/17 15:20, Karen Coyle wrote:
> My sense is that the database could be treated as a finished document.
> I don't know the easiest way to do that, but the static HTML snapshot
> sounds good to me.
>
> kc
>
> On 2/28/17 2:31 AM, Kai Eckert wrote:
>>>> Dear all,
>>>>
>>>> I had to take the webserver offline that also hosts the
>>>> requirements database, due to security issues. A migration of the
>>>> database to a new server would be needed, but unfortunately I have
>>>> no time available at the moment.
>>>>
>>>> There is a GitHub issue for this problem, too:
>>>> https://github.com/boschthomas/rdf-validator/issues/56
>>>>
>>>> The question is how to proceed with the database anyway. Do you
>>>> consider it "done" and stable? Then, I would propose to create a
>>>> static HTML snapshot and make it available for preservation. A dump
>>>> of the original MySQL database where your passwords are eliminated
>>>> could be provided as well, as we did already sometime in the past,
>>>> IIRC.
>>>>
>>>> Otherwise, we would have to keep the Drupal system available
>>>> somewhere, which is doable, but requires efforts for the migration
>>>> and the continuous backups and security updates.
>>>>
>>>> What do you think?
>>>>
>>>> Cheers,
>>>>
>>>> Kai
>>>>
>>>>
>
>>
>>
--
Prof. Dr. Kai Eckert, Stuttgart Media University
http://www.wisslab.org/
PGP Public Key: http://www.kaiec.org/2012/pgp/pubkey.asc
A987 3760 12A6 35A4 E6D2 577E 513A 6B84 C755 5A67
|