Re: [dxwg] dcat:byteSize - check constraints (#125)

@dr-shorthair are you suggesting changing the range of `dcat:byteSize` instead of mentioning `xsd:nonNegativeInteger` only as an indication in the REC (as in https://w3c.github.io/dxwg/dcat/#Property:distribution_size)? 
In this case, could you comment on the impact this can have on existing implementations? See my comment below. 


> In terms of principle, I agree on specializing the range of dcat:byteSize. It makes `dcat:byteSize` semantics more consistent, and consequently, it improves the overall metadata quality.
> 
> However, this change might have some practical burden on existing implementations. If we restrict the range of `dcat:byteSize`, we force people to correct the metadata in which real numbers or abbreviations are used.
> 
> I wonder how impacting this change is for people managing tons of metadata.
> Probably, @dr-shorthair or @andrea-perego have already considered this aspect.
> Do we think the advantages in terms of gained quality balance the extra work required to metadata managers?



-- 
GitHub Notification of comment by riccardoAlbertoni
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/125#issuecomment-821048347 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 16 April 2021 09:29:28 UTC