Omar Benjelloun

I would lean towards representing them as separate FileObjects. If we want to preserve the connection between them, we could specify sc:encoding pointing from the original file to each of...

@ccl-core Can you please take a look at this issue?

Drive-by comment: I dislike the fact that versions can be numbers... As numbers, there is no difference between 1 and 1.0, even though we may consider them to be different...

We can constrain sc:version by changing its documentation in our spec, and validate the field for datasets that specify that they comply with Croissant 1.0. Indeed, for SemVer we would...

Wow, the discussion in https://github.com/schemaorg/schemaorg/issues/1781 is quite amazing and instructive. You make very valid points on the merits of xsd types vs. schema.org basic data types. Personally, I would lean...

Thanks for the catch! Indeed it should be schema.org/Enumeration. Do you want to send me a PR for the fix, or should I go ahead and fix it?

Hi Vladimir, We considered CSVW, but it wasn't appropriate to describe the structure of data in Croissant, as it focuses on CSV tables. We needed a construct that could also...

Hi Phil, It would be great to also embed the Croissant metadata inside the dataset Web pages (as an extension of the schema.org metadata you already have) so that it's...

On Mon, Feb 26, 2024 at 12:39 PM Philip Durbin ***@***.***> wrote: > @qqmyers hmm, good point. Signposting does > provide a machine-readable way (HTTP headers) to retrieve URLs with...

Hi Phil, Please see replies inline. On Fri, Feb 23, 2024 at 5:50 PM Philip Durbin ***@***.***> wrote: > @benjelloun thanks. Right, the schema.org > metadata inside the of Dataverse...