trove:propertyPath

https://share.osf.io/vocab/2023/trove/propertyPath
more details...
trove:thesaurusEntry

trove:propertyPath

rdf:Propertyowl:FunctionalPropertyjsonapi:document-resource-object-attributes
https://share.osf.io/vocab/2023/trove/propertyPath
more details...
rdfs:label
label
jsonapi:document-member-names
dcterms:description
mediatype:text/markdown#charset=utf-8language:en

a property-path is a dot-separated path of short-hand IRIs, used in several api parameters

currently the only supported shorthand is defined by OSFMAP

for example, creator.name is parsed as a two-step path that follows creator (aka dcterms:creator, <http://purl.org/dc/terms/creator>) and then name (aka foaf:name, <http://xmlns.com/foaf/0.1/name>)

most places that allow one property-path also accept a comma-separated set of paths, like title,description (which is parsed as two paths: title and description) or affiliation,creator.affiliation,funder (which is parsed as three paths: affiliation, creator.affiliation, and funder)

the special path segment * matches any property

  • *: match values one step away from the focus
  • *.*: match values exactly two steps away
  • *,*.*: match values one OR two steps away
  • *,creator: match values one step away OR at the specific path creator

(currently, if a path contains *, then every step must be * -- mixed paths like *.affiliation are not supported)