Okay, that was what I thought. I guess for the W3C note it makes sense to have a strong rule set. Alasdair, will the validator highlight properties that should be removed in order to fit a certain profile? Not sure how easy/hard it would be to implement though. Joachim On 28 November 2013 13:53, Michel Dumontier <michel.dumontier@gmail.com>wrote: > The reason for this is that we want to distinguish each of these forms, > and allowing users to add any of these special attributes would undermine > and confuse the process. > > m. > > > On Tue, Nov 26, 2013 at 1:42 PM, Joachim Baran <joachim.baran@gmail.com>wrote: > >> Hello, >> >> On 26 November 2013 09:33, Gray, Alasdair J G <A.J.G.Gray@hw.ac.uk>wrote: >> >>> [...] I have also used NEVER to indicate when a property should not be >>> associated with a description profile. >>> >> NEVER seems quite a strong indication. For example, if I have a catalog >> description and additionally include dct:creator besides the MUST and >> SHOULD properties, does the description become invalid then? Would "MAY" >> not be appropriate here? >> >> Joachim >> >> > > > -- > Michel Dumontier > Associate Professor of Medicine (Biomedical Informatics), Stanford > University > Chair, W3C Semantic Web for Health Care and the Life Sciences Interest > Group > http://dumontierlab.com >
Received on Thursday, 28 November 2013 19:33:33 UTC