Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dataspace-protocol-base-dev] Distribution entity : Possible data model issues

Yes, you are right, but in that case is referring to the distribution of the Catalogue itself as a dataset itself, not to the distributions that are registered in the Catalogue i.e the ones it contains as Resources ... so that should be clearly clarified in the spec, IMHO. In my opinion a Distribution always come hand in hand with a Dataset ... i.e. there is no point in an orphaned distribution ... 

Part III:
BTW another issue with Distribution in the current data model is the absence of an @id ... it is necessary in case one to refer explicitly to it as the target in a negotation  

On Tue, Nov 11, 2025 at 9:30 AM Jim Marino <jim.marino@xxxxxxxxx> wrote:
Please review the DCAT 3 Specification. Catalog is a Dataset subtype, which has a “distribution” property.

On Nov 11, 2025 at 9:20:24 AM, José Cantera via dataspace-protocol-base-dev <dataspace-protocol-base-dev@xxxxxxxxxxx> wrote:
Dear all,


Part I: 
Catalog object type is said to have a member named `distribution` with a list of `Distribution`. However the W3C DCATv3 doesn't, although it has a dcat:resource that only mentions `catalog`, `service` and `dataset` as possible sub-properties.  

On the other hand a Distribution might not have a life without a dataset ... so ... 

Part II:

Dataset object type mentions `distribution` as one of its members but then nothing is said about the type. It should say required array[Distribution]. 

Please let me know your feedback

All the best

--
José Manuel Cantera Fonseca

IOTA
Senior Architect & Project Lead
_______________________________________________
dataspace-protocol-base-dev mailing list
dataspace-protocol-base-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

Back to the top