A suggested (human/machine-readable) way to specify a list of possible matching properties in the mapping about codemeta HOT 4 OPEN

codeRepository, DOAP: repository/location

actually that one, like other slashes without spaces, is XPath syntax. It means location value in repository value

from codemeta.

For mappings improvement we started a discussion on: #336

An option is going towards a machine actionable format such as SSSOM (A Simple Standard for Sharing Ontology Mappings by Matentzoglu, Nicolas: https://mapping-commons.github.io/sssom/events/wsbo2021/)

I don't have THE answer, but it is a needed discussion.

from codemeta.

codeRepository, DOAP: repository/location

actually that one, like other slashes without spaces, is XPath syntax. It means location value in repository value

Thank you. Maybe that's another reason we probably need some guideline on this. (and a case against the use of / as a separator?)

Also how to deal with such a path.

• DOAP uses / (like in repository/location)
• OntoSoft uses -> (hasDependency->Software)
• R Package Description uses in ([aut] in Author)

from codemeta.

codeRepository, DOAP: repository/location

actually that one, like other slashes without spaces, is XPath syntax. It means location value in repository value

Thank you. Maybe that's another reason we probably need some guideline on this. (and a case against the use of / as a separator?)

Also how to deal with such a path.

* DOAP uses `/` (like in `repository/location`)
* OntoSoft uses `->` (`hasDependency->Software`)
* R Package Description uses `in` (`[aut] in Author`)

I just realized that this case (thanks @progval) and #354 are the same matter, just on a different direction:

• This case is for a mapping from CodeMeta -> Other/property
• #354 is for a mapping from CodeMeta/property -> Other

from codemeta.