Hi,
sorry, the last call I could nit make it as I had a serious paper deadline for my PhD thesis.
One question raised the last call was to change the URL of the database.
When I set up the database with Kai, we created a PURL:
http://purl.org/net/rdf-validation
I could change this URL if wished.
Any suggestions?
Another question was, if I understood correctly, if the title for the database 'rdf-validation' could be changed.
Yes, I changed it to 'DCMI Application Profiles' to show that this is possible.
Any suggestions?
So far, I do not have any experience in providing an export functionality.
If this is wished I could do some research on that.
I will continue using the database as I use it for my research on RDF validation.
You suggest not to continue using it? If yes, this would be a pity...
Cheers,
Thomas
Hi Thomas,
In the call today, we had a long discussion about how we should manage our information on use cases and requirements, which is currently in the databse you've set up:
http://lelystad.informatik.uni-mannheim.de/rdf-validation/
We would like very much to hear your opinion on it.
I've copied the minutes of our discussion on it below.
The minutes of the full call are at
https://etherpad.wikimedia.org/p/dcmi-ap-16-07-2015
I think I don't need to explain a lot more the questions we had, but feel free to ask if a point is not clear.
All the best,
Antoine
----
Karen: in terms of documentation: many things are in the database. Should we continue?
Antoine: I'd like to base our reqs on cases
Karen: we could copy them outside
Corey: the DB has 'RDF validation' in the URI.
Evelyn: I could copy in the UC document
Karen: the requirement wiki also points to the DB.
antoine: if we copy the DB in one document, it could be huge
Karen: it has all our ideas
Evelyn: we could export it
Karen: we could do at the end of the task force
Antoine: in the meantime, where should we do our updates (use cases or requirements)?
Corey: if we draw new people to our group the 'RDF validation' title may be confusing.
Antoine: it has played a trick on us once already :-)
Antoine: we could ask Thomas to change the URL?
Corey: probably a non-starter. He uses it for his PhD, which is on validation
Corey: the LLD XG report had links to separate wiki pages with the original use case details
... which corresponds to an HTML version of what we could do.
... we could do an Markdown export
Antoine: thomas was using the DB to keep track of updates
... he could prefer us to keep using it rather than do updates on a separate wiki page
Karen: how many times would people need to access the origianl description?
... maybe not so much, so we could have the info exported in a more basic way
[discussion on creating one page on the wiki for every UC]
Corey: a page could be ok, as long as it has all the info
Corey: Here's something interesting: Drupal-Jekyll-Markdown module: https://github.com/lukaswhite/Drupal-Jekyll-Export
This would potentially allow us to export a markdown page per drupal node, and then generate media-wiki pages from those.
|