Container Data Augmentation
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
From discussion with @timbl , we found that container metadata are intended to be quite sparse, in the sense that it is mostly containment triples, minimal server data, possibly other metadata, such as timestamps of last modification, etc. It is not intended to host extensive metadata about the container or resources in the container that apps may find useful.
Such data is what I refer to as augmented data. Hitherto (I love that word :-) ), the databrowser has used a resource called index.ttl for such data.
This issue is opened as the issue is a orthogonal (or at least 75 degrees :-) ) to the container listing issue in #116.
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 reviewing the discussion in this issue and comparing the existing use of index.ttl with the container listing work in #116. Clarify the intended boundary between sparse container metadata and augmented data, then define the specification changes and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100