Documentation of ttl and exp on Catalog
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Search the protocol specification for the Catalog object and its ttl and exp fields, then read their current definitions and usage in on_search. Clarify the semantic difference in the relevant documentation, or record the decision to remove one field; done means the specification unambiguously explains both fields or resolves the duplication.
Written by the indexing model from the issue text.
Description
Describe the bug
On Catalog object returned as part of on_search, there are 2 fields ttl and exp. Not sure what is the difference between time to live and expiry in the same object. need clarification.
To Reproduce
Steps to reproduce the behavior:
-NA-
Expected behavior
Both ttl and exp need to be documented better or one of them removed.
Screenshots
-NA-
Desktop (please complete the following information):
-NA-
Smartphone (please complete the following information):
-NA-
Additional context
-NA-
@ravi-prakash-v @rajaneeshk90
- Dominant language
- No language data
- Stars
- 453
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from beckn/protocol-specifications
-
Migrate default branch from `master` to `main`May be free again @ravi-prakash-v claimed this 369 days ago, and no pull request is open. Openworking group meeting
beckn/protocol-specifications#491 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
beckn/protocol-specifications#472 · 3 comments ·
-
Restructure spec repos to allow more interactive learning of the specMay be free again @rajaneeshk90 claimed this 713 days ago, and no pull request is open. Openprotocol-specifications
beckn/protocol-specifications#455 · 1 assignee ·
-
Design specifications for Open Data platformMay be free again @rajaneeshk90 claimed this 713 days ago, and no pull request is open. Openprotocol-specifications
beckn/protocol-specifications#454 · 1 assignee ·
-
Protocol-Specification Version 1.2 releaseMay be free again @rajaneeshk90 claimed this 713 days ago, and no pull request is open. Openprotocol-specifications
beckn/protocol-specifications#451 · 2 comments · 1 assignee ·
All issues in beckn/protocol-specifications
Similar issues
-
area:breg criticality:p3 documentation triage:needs-implementation
Difficulty 1/5 Under an hour Newbie friendliness 86/100
registrystack/registry-stack#1713 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
posit-dev/ggsql#565 · 1 reaction ·
Maintainers usually reply within 1 day
-
documentation easy good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lacs-project/sysknife#518 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
qgis/QGIS-Plugins-Website#459 ·
-
bot-found documentation priority: P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
madenvel/KalinkaPlayer#178 ·