LD4P / arm

BIBFRAME extension ontologies for modeling bibliographic metadata in the art and rare materials domains.
https://ld4p.github.io/arm/
16 stars 10 forks source link

Namespace for raremat_monograph_form #62

Closed rjyounes closed 6 years ago

rjyounes commented 6 years ago

@sfolsom If our namespaces are going to reflect the directory structure, shouldn't the raremat_monograph_form namespace be: https://w3id.org/arm/application_profiles/raremat_monograph/shacl/raremat_monograph_form/ ?

Ditto for raremat_monograph_property_groups.

This is how I've namespaced my files, and that's how my prefixes for your files read. We need to get these in sync, obviously.

P.S. Despite my earlier suggestion of the singular "application profile", I've changed the folder name to the plural because it does indeed contain multiple profiles (raremat and art). If it were just multiple files for a single application, it would be more appropriate to use the singular.

rjyounes commented 6 years ago

Or maybe you weren't expecting the namespaces to reflect the directory structure. In any case, I'm confused.

sfolsom commented 6 years ago

I misinterpreted a comment you made previously about redundancy in the URI. If keeping the directory matching the URI is important... Maybe the URI should be https://w3id.org/arm/application_profiles/raremat_monograph/shacl/form/ .

rjyounes commented 6 years ago

The directory structure doesn't have a form/ directory. Also, the SHACL in the application profiles is not strictly for forms, but also for display, isn't it? So I would suggest just matching the current directory structure; but feel free to disagree.

zimeon commented 6 years ago

There is no requirement for directory structure to match the URIs. The directory structure should be whatever is easiest to understand and manage (which maybe happen to match URIs, or may not)

rjyounes commented 6 years ago

I realize there's no such requirement, but other things being equal it seems simpler if they do. AFAIK other things are equal.