Clarify server handling of related topics

Open
#347 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
50/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
api, documentation

Research direction

Start with the documentation or README referenced in the issue and find the section describing related topics and topic retrieval. Clarify that servers supporting topic relations return every relation in related_topics in both directions, so clients do not need to enumerate other topics. Done means this behavior is stated unambiguously.

Written by the indexing model from the issue text.

Description

This came up from @pasi-paasiala

We should update the documentation / README to ensure that it's clear that servers that support topic relations are always expected to return all the relations when getting topic data, so that a client would never have to enumerate all other topics to check if a relation exists.
Meaning, if we query the server to get a "child" topic, it will include the "parent" topic in it's 'related_topics' list (and vice versa).

Dominant language
No language data
Stars
238
Forks
67
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from buildingSMART/BCF-API

All issues in buildingSMART/BCF-API

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.