- From: Nicholas Car via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Nov 2019 01:53:35 +0000
- To: public-dxwg-wg@w3.org
The reason for taking this qualified relations approach (`hasResource/hasRole`) is that there are potentially many `ResourceRole` roles and thus there could be many properties. [Already the vocabulary contains 8 Roles](https://w3c.github.io/dxwg/prof/#resource-roles-vocab) and we hop for and expect more to be created. So it's true that perhaps nothing would be *lost* in using direct properties but, over time, the direct properties, if declared in PROF and thus unchangeable, would bias against the use of future roles for which direct properties were not created, since they were unknown at the time of PROF creation. If your community feels strongly about direct properties, could an Issue be created for the 4PWD to add them to PROF? -- GitHub Notification of comment by nicholascar Please view or discuss this issue at https://github.com/w3c/dxwg/issues/794#issuecomment-557957046 using your GitHub account
Received on Monday, 25 November 2019 01:53:36 UTC