RDF terms should be available in a public vocabulary - Githubissues

samvera-deprecated / curation_concerns

A Hydra-based Rails Engine that extends an application, adding the ability to Create, Read, Update and Destroy (CRUD) objects (based on Hydra::Works) and providing a generator for defining object types with custom workflows, views, access controls, etc.

Other

15 stars 27 forks source link

RDF terms should be available in a public vocabulary #561

Closed mjgiarlo closed 2 years ago

mjgiarlo commented 8 years ago

From @spr7b on October 7, 2015 19:35

Did these terms ever get posted somewhere to make them part of a public vocabulary?

ss:relativePath: A relative path within a directory structure.
ss:importUrl: The URL from which content hosted in a cloud storage service is imported.

Copied from original issue: projecthydra/sufia#1327

mjgiarlo commented 8 years ago

From @escowles on October 8, 2015 12:20

I wrote up a rough draft of an RDFS description of those predicates:

https://gist.github.com/escowles/93eea55a4341da25cdf5

Outstanding issues:

Is http://scholarsphere.psu.edu/ns# the right namespace to use?
Related: who can host these?
Do the domains and ranges match how these are used in the new PCDM-ified Sufia?

mjgiarlo commented 8 years ago

From @awead on October 9, 2015 10:39

The Scholarsphere namespace seems a bit out of place now. Are they're any alternatives to use? @mjgiarlo, any issues for existing apps if we change these?

mjgiarlo commented 8 years ago

@awead Existing apps will have to migrate data to the new predicate URI, yep.

mjgiarlo commented 8 years ago

From @awead on October 9, 2015 15:59

@mjgiarlo maybe something to pull the plug on for Sufia 7.0 with PCDM, since we'll be redefining a lot predicates anyway.

mjgiarlo commented 8 years ago

ooooh, I like that idea. I'll ticket that.

mjgiarlo commented 8 years ago

From @jcoyne on October 9, 2015 16:29

These are currently in curation_concerns, so if we're going to change them we should do it ASAP.

mjgiarlo commented 8 years ago

Good point re: relativePath and importUrl being in CC. I'll look at @escowles's gist today and come back with a proposal.

mjgiarlo commented 8 years ago

No, that's not the right namespace.
How about opaquenamespace.org? Or is there a more appropriate/stable place? (Hey, how stable would you consider opaquenamespace.org, @terrellt @kestlund @no-reply? A penny for your thoughts about where to host a wee Hydra-related vocab, preferably somewhere that isn't going to go away in the next few years?)
About domains and ranges, are pcdm:Files a valid domain given the wonky way that we express metadata about files in F4? If so, OK. The range of relativePath should be a string given the current impl.

Thanks for getting this started, @escowles!

mjgiarlo commented 8 years ago

From @ruebot on October 26, 2015 23:36

Greetings!

@jlhardes contacted @acoburn and I, and wanted us to check out this issue in our roles as co-facilitators for the Technical Metadata Working Group. @acoburn and I had a call today and talked about it, and are more than happy to share our feedback now, or if you'd like, we can pull the original group together and consult them as well.

cheers! :smile:

mjgiarlo commented 8 years ago

From @awead on October 28, 2015 10:31

@jlhardes @acoburn @ruebot It just so happens there's an agenda item for this on today's Hydra tech call. https://wiki.duraspace.org/display/hydra/Hydra+Tech+Call+2015-10-28 Care to join in?

mjgiarlo commented 8 years ago

From @ruebot on October 28, 2015 11:26

I'd love too, but I have a schedule conflict at noon :cry:

mjgiarlo commented 8 years ago

From @jlhardes on October 28, 2015 12:27

I can be on the call today. @ruebot @acoburn can you go ahead and share your feedback? I think that will help move this forward.

mjgiarlo commented 8 years ago

From @acoburn on October 28, 2015 12:29

I will also be on the call

mjgiarlo commented 8 years ago

From @ruebot on October 28, 2015 12:34

Thanks @acoburn!

mjgiarlo commented 8 years ago

From @jlhardes on November 11, 2015 20:46

Hi! @acoburn and @ruebot should verify this, but from what I have in my notes from the Hydra Tech Call on 2015-10-28, the following were predicate options to use instead of creating new terms:

premis: http://www.loc.gov/premis/rdf/v1 marcrelator: http://id.loc.gov/vocabulary/relators ebucore: http://www.ebu.ch/metadata/ontologies/ebucore/ebucore

ss:arkivoChecksum = premis:hasMessageDigest or a checksum property from LC (not sure which) ss:relativePath = premis:hasContentLocationValue or a property from ebucore (ebucore:locator?) ss:importURL = premis:historyInfo but this might not work ss:proxyDespoitor = marcrelator:dpt (depositor) ss:onBehalfOf = marcrelator:cre (creator)

mjgiarlo commented 8 years ago

From @hackmastera on November 12, 2015 14:27

Some of these did not seem like great fits as I recall, especially the marcrelators for proxyDepositor and onBehalfOf. My sense from the conversation was that more investigation / discussion would be needed. @cam156 seemed to have the best sense of how these terms were actually being used.

mjgiarlo commented 8 years ago

From @ruebot on November 16, 2015 2:16

@jlhardes that sounds about right.

mjgiarlo commented 8 years ago

Given no clear path to resolution at the moment, I am moving this to the backlog so that it's not a blocker to 7.0.0.