- From: makxdekkers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Mar 2018 08:17:11 +0000
- To: public-dxwg-wg@w3.org
@dr-shorthair Although I admit that I am the one who suggested the range "to be tightened to a new class `dcat:IANAMediaType`", on second thought, I think this would not be a good idea as it could break existing implementations. If someone had implemented DCAT using `dcat:mediaType` and used something that is not an IANA media type as its object but still a valid `dct:MediaTypeOrExtent`, that implementation would violate the spirit but not the letter of the specification. It could only be accused of not respecting the SHOULD in the [Usage Note](https://www.w3.org/TR/vocab-dcat/#Property:distribution_media_type), which is a very weak axiom, if you could call it an axiom at all. However, after the suggested change, that implementation would violate the letter of the rule. I don't think we want that. I have always used the rule that you may 'widen' the scope of a property, e.g. by making the domain or range broader, but that you should not narrow domain or scope, as this is not backward compatible. In this case, then, I would be in favour of adding more guidance information to the specification rather than fiddling with the range. -- GitHub Notification of comment by makxdekkers Please view or discuss this issue at https://github.com/w3c/dxwg/issues/127#issuecomment-373295494 using your GitHub account
Received on Thursday, 15 March 2018 08:17:58 UTC