Remove x_representation fields
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 23
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
changes be like
```
{
"id": "CHANGE:001",
"type": "NodeRename",
"old_value": "'nuclear envelope'",
"new_value": "'foo bar'",
"about_node": "GO:0005635",
"about_node_representation": "curie",
"@type": "NodeRename"
}
```
there is no need for `about_node_representation` if we have a prefix map for each change set.
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 locating the KGCL data-model definitions and usages of the `x_representation` fields, especially `about_node_representation`. Check how prefix maps are represented for each change set, then verify that the example change no longer needs the redundant field and that existing validation still accepts the revised shape.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100