The representations at the links in the readme.md file suck #1

Open
jonphipps opened this Issue Jan 9, 2012 · 5 comments

Comments

Projects
None yet
2 participants

There needs to be a better way of displaying the triples. This seems to be related to the gap between the expectations of the linked-to ontology parsers and the mapping file.

There's an example of a better mapping representation at:
http://maps.jesandco.org/maps/934
...although the map would have to be hosted there for it to work.

aisaac commented Mar 22, 2012

Yes, that's weird, it seems that they have changed the code so as not to display classes/properties, when these come from a different namespace. And since our mapping file only has such classes/properties...

aisaac commented Apr 6, 2012

Here's a thread with a suggestion on making the situation slightly better: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1204&L=dc-architecture&F=&S=&P=2541

I guess I'm not seeing how that would address the issue of line-related discussions (which is addressed by version-specific line reference links). But I'd love to see a brief example of an html/rdfa doc like you're suggesting. And of course we could always reify the mapping statements so we could refer to them by URI.

aisaac commented Apr 6, 2012

Hi Jon,

I plan to post an example file / play around with it on github in the very near future.
Do you know if I have push rights, by the way?

Cheers,

Antoine

I guess I'm not seeing how that would address the issue of line-related discussions (which is addressed by version-specific line reference links). But I'd love to see a brief example of an html/rdfa doc like you're suggesting. And of course we could always reify the mapping statements so we could refer to them by URI.


Reply to this email directly or view it on GitHub:
#1 (comment)

Hey Antoine,

Best thing to do is fork the repo into your account, make your changes, add your files, and then send a pull request.

That's actually the best way to suggest changes to the current mappings as well since they can be edited right in your own version on github and your version, whether it lives only your github fork on github or is cloned to your local machine, can be synced to the dcmi version with a pull -- complete with commit comments.

Jon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment