The formats/mediaTypes a DataService may support in BregDCAT-AP is one of the  main considerations when deciding whether a DataService is (re)usable or not.  In the current version of BRegDCAT-AP, dcat:DataService doesn’t have properties dct:format and dcat:mediaType the way dcat:Distribution has. Therefore, alternative paths should be followed to identify the dct:format and dcat:mediaType  that is supported by a DataService.

There is a related discussion point  (#10) under ABR collection in Joinup (here).

We can enrich the content of this issue, by adding that during the last WG meeting, this issue remained unresolved and it is therefore left open, to be dealt with in the next release in 2022.

Context: During the last WG meeting, many participants identified the need of adding such properties at DataService to enrich its metadata (this is also addressed to  dxwg  at #1381 , #1055, and  related discussions and info can be found  #1126 and #1242). However,  there was also a concern that by doing so, the scope of DataService may be restricted. Therefore, no conclusion was reached at that point. Nonetheless, it was agreed that if new properties are to be added to dcat:DatsService, they should be optional.

Possible solutions:

• Add dct:format and dcat:mediaType  to dcat:DataService  as optional properties
• Add an (optional)  property  with different (more precise) semantics to address this need, such as  dct:conformTo, dcatap:availableFormat.
• Other proposals

Opinions and proposals are welcome. Please express your opinion for you preferred option.