Closed smnmyr closed 2 years ago
There is a PR based on https://github.com/HyperAgents/ns.hyperagents.org/issues/38 that changes this definition.
Can we rename ":exposesSignifier", by ":hasSignifier"?
We agree it's sloppy to have in the definition of :Artifact
: : exposes affordances, and:
:exposesSignifier
with domain :ResourceProfile
that uses the same word.@smnmyr @maximelefrancois86 to echo @DrLeturc's last comment: it seems this issue is addressed in PR #54 by the updated :Artifact
definition.
I think :exposesSignifier
is not affected by @smnmyr's remark on affordances as relational notions: a signifier is a design abstraction and a concrete resource, such as an information resource. Not sure :hasSignifer
would be more clear because it seems to me "has" implies some ownership or composition relation. E.g., could the same :Signifier
be part of multiple :ResourceProfile
s?
@danaivach please weigh in
@DrLeturc should we open a new issue for :exposesSignifier
to keep the discussions tidy?
Closed because PRs #54 and #38 are closed.
@DrLeturc Please open an issue for :exposesSignifier
if still an issue.
https://github.com/HyperAgents/ns.hyperagents.org/blob/8a13e3ec4bdfdcc419d3a17b3b8c7c2091d89ddc/src/core.ttl#L95
I propose to change the "exposes" to a word that does not undermine the relational notion of affordances so much. "Exposes" can easily be misunderstood as close to "shows" or "presents" which is what we are trying not to do by introducing Signifiers.