Assign Topic to ...

[buildingsmart]

Assign Topic to ...

[linhard]

With BCF 2.0 we will go more in the direction of webservices than sending bcfzips over email. For that we expect a BIM-hub and see project- and user related things more on that side.

[ErikPijnenburg]

Yep, I agree. We will need bim-hub's for managing issues. But we will still need the communication via BCF files for some time (for example for applications which are slower in supporting direct links to a BIM hub offering upload/download of BCF files). Solibri currently offers for issues a "responsibility" choice. More app's have something similar, so why not support 'assign to' also in BCF files.

[pasi-paasiala]

Should we then add assignedTo to the topic? I think this is very general need, not only in communicating with the hub.

[linhard]

Topic or comment, what is the right place ?
and is it an email-address or simply first-name and last-name ?

[ErikPijnenburg]

I vote yes, on topic level
In my view somebody is responsible for a topic = issue. Comments are just historical discussion / remarks with an author. The most simple identification of a user (and also an author) is his e-mail address combined with a one string name. Apps but mostly hubs can then define for themselves if they add more info like initials, first-name, second name, company, etc. If you want to be complete in BCF you could add user-definitions with these extra properties, but not sure if that is needed.

[linhard]

Ok i will add that to the markup.xsd und load it up to GitHub

[linhard]

Ok this is now on GitHub. Please check if it is ok like that ?
When its ok i will bring it into the documentation.

[ErikPijnenburg]

OK, but better is to have max 1 assigned to.
Only one person can bear responsibility.

[linhard]

OK, its on GitHub

[linhard]

I updated also the documentation.

[theoryshaw]

IMHO, it would be nice to be able to apply multiple people to a topic. In our typical workflow, this happens quite a bit.

A good precedent even, would be the ability to assign multiple people to github issues.

[linhard]

so i think we need a discussion here.

[ErikPijnenburg]

The request of theoryshaw is understandable but keeping pleople informed should not be mixed with appointing a person who is responsible for the topic/issue. Github is not fully comparable since that is more a discussionplatform. In a ticketsystem like BCF is meant to be, only one person can be responsible otherwise we compromise on basic team-cooperation rules. The request of theoryshaw should therefor be solved in another way. I even think that it is more functionality of a hub or app to send changes in a ticket to team members then it Is a recquirement for the BCF format.

[berlotti]

Agree with Erik. It is about responsibility and in the end only one person is responsible for an issue (could be someone else than the creator/owner by the way)

[pasi-paasiala]

We'll stick with one comment at the moment.