Distinguish server and client implementations on the standards implementation list

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start by reviewing the software implementation list at technical.buildingsmart.org/resources/software-implementations/ and the issue's requested server/client distinction. Done means the list lets vendors identify server and client implementations so users can match them for a data flow.

Written by the indexing model from the issue text.

Description

This is not directly an issue with the BCF-API, but more a feature request to bSI related to the BCF-API: In the software implementation list at technical.buildingsmart.org, it would be useful to distinguish server and client implementations. Currently, vendors can only specify whether they implement the API at all. But if I search for software to combine in a complex project setup, I want to match different client and server software to realize a specific data flow. Admittedly, this corresponds to read/write capability for the IFC schemas, where there is no such distinction either same as for the bsDD API.

Dominant language
No language data
Stars
238
Forks
67
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 Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.