check compatibility with inara
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 35
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
see https://github.com/openjournals/inara/blob/main/docs/names.md
It seems the only strict issue is `literal` by inara is `string-name` by us.
Not sure what to do with particles. jats4r does not talk about this I think. @tarleb
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked inara docs/names.md and comparing its names with this project's schema, especially inara's literal versus this project's string-name. Investigate how particles are represented in both specifications, then define and document the compatibility result and any required schema changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100