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

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, @simon or @andrea 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-811857000 using your GitHub account


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

Received on Thursday, 1 April 2021 11:57:53 UTC