I guess it should attempt to load one complete set:
RDF data (either mesh.nt or mesh<year>.nt
So, that also means, I think, that mesh-xml2rdf.pl should copy over the vocabulary and void files into $MESHRDF_HOME/out.
That's right. Should the void file be included even if it is an empty file? Should it be an empty file.
ftpupload.sh can pull things from various places to build the right directory structure.
I wasn't aware you'd gotten so specific with the directory structure - I need to know what part of that is requirements, what part is specification, and what part is Chris' idea of how it should be wrt Linked Data Working Group.
If mesh-xml2rdf.pl builds the right directory structure in $MESHRDF_HOME/out, that would also be great.
You mean the FTP site directory structure?
I'm just trying to document what I thought we'd agreed to.
I just tried to follow the convention of what is in the 2014 sub-directory. I have not been keeping up on the minutes.
We could do away with the version numbers in the filenames of vocabulary and void. What do you think?
It would be nice if we could version them consistently, though, using owl:versionInfo inside the documents, and git tags on the repo.
What is the source of the version numbers? How will code know what version numbers to use?
Some sort of checksum file and "LASTUPDATED" file would be more useful. A downstream user who wants to download the latest can just use LASTUPDATED. I downstream user who wants to check if they have the "latest" can use the checksum to check for differences quickly, and the "LASTUPDATED" file he/she has mirrored to figure out when they are changed. Autonomous is better than curated.
Can you document these ideas on the "Versioning" page?
I am starting to work a little on load-rdf.pl. I want to minimize my work to it, but I'm thinking that it should have hard-coded the same conventions as are in mesh-xml2rdf.sh
It could take parameters that match MESHRDF_YEAR (4-digit number) and MESHRDF_URI_YEAR (an on/off switch)
Then, it would look for the data file either as out/mesh.nt or out/YYYY/meshYYYY.nt
And, for the graph names based on the conventions in the Versioning page
Yes, I'll document these ideas on the Versioning page. I'll socialize them with John Butler at our meeting.