Re: [dxwg] Copied lists of inherited properties into class descriptions

I actually disagree with @agbeltran. It looks more natural to me to go from subclass to superclass to super-superclass. It is done the same way in schema.org, e.g. https://schema.org/Dataset lists properties for Dataset first, then properties inherited from superclass CreativeWork, then the ones from Thing. Also, it seems better to me to keep the text in line with the diagram.
In addition, the lists of properties in the diagram are ordered strictly alphabetically on the namespace prefix/property label, while the properties in the text do not seem to follow any ordering. I would suggest to align the order in the diagram with the list under the class heading and with the sequence of the subsections.

-- 
GitHub Notification of comment by makxdekkers
Please view or discuss this issue at https://github.com/w3c/dxwg/pull/459#issuecomment-431106844 using your GitHub account

Received on Thursday, 18 October 2018 18:05:18 UTC