Re: [dxwg] prof:inheritedFrom needs more convincing case and/or example (#642)

Thanks for the example. I believe that it helps the discussion... But first some friendly editorial advice. It would be good if profiles ids had numbers or letters that can be reused by the resource descriptors id, making sure it's easy for the reader to connect profiles with descriptors, just from reading the ids. X,Y,1,2,3 could be P1, P2, P1RS1, P2RS1, P2RS2. It's not beautiful but will make our discussion/understanding a tad easier.
And echoing a comment from @kcoyle, in such an example there's no need for representing class instantiation in the diagram. It's already visually quite complex, cf the arrow between RS1 and ResourceDescriptor. Instead, pick ids for the instances, which will reflect the main class they belong to. Like resourceDescriptor1ForProfile2. Not beautiful, but clearer.

Finally, don't include materialized trivial rdf:type statements unless they mean something. If ex1:Standard_X shall be defined as instance of prof:Profile then it's enough, in an example that is not about the relation between dct:Standard and prof:Profile.

On the content itself, like @kcoyle I sense that we've talked a lot about 'profile inheritance' and that prof:isInheritedFrom is about something slightly different (maybe a consequence of profile inheritance, but for the resources that embody these profiles).

But I would prefer that the example is editorially a bit simpler before discussing this really complex matter.

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

Received on Tuesday, 5 February 2019 10:16:57 UTC