Michele Mattioni

link to the issue where we have been discussed this: https://github.com/ga4gh/data-repository-service-schemas/issues/336#issuecomment-1514899431

@bheavner the main idea is that you do not search `drs_uri`. As written by @dglazer DRS alone do not tell you a lot, just how to get the bytes that...

@bheavner yes, I'm 100% aligned with that. The comment on https://github.com/ga4gh/data-repository-service-schemas/issues/336#issuecomment-1514899431 was exactly hinting at that. It would be good if we have in the DRS response the "learn more"...

Thank @MichaelLukowski to get this rolling. Yes I totally agree. Maybe is it worth it also to add another bit about the "name" of the DRS Server? Should we just...

Do we know if others standards have used `service_info` to add specific information? I think that could tell us if we should add "DRS" specific there or not. I'm trying...

quick note form Connect Switzerland, recording the decision: Let's make it an enumeration: --> immediate, delayed as the two terms. Lots of thumbs up in the room.

Hi @ianfore , thanks for raising this. I think it would be important to have it there, given that we already have use-cases where the data are in cold storage,...

I agree, but at the moment the major obstacle I see is how to handle the transfer from the cold to hot, given the inherent variability. AWS for example wants...

@NavidZ I understand where are you coming from, but we do not want to map the cold storage system on DRS. For Phase 1, we just want to answer this...

hi @Avantol13 and @ianfore , thanks for the feedback. I see two main aspects raised: 1) clinical level information on the name: The PR #381, which has already received positive...