- From: Goldberg, Matt (Matthew G) <GoldberMG3@corning.com>
- Date: Fri, 18 Jul 2025 16:46:18 +0000
- To: Eliana Papoutsoglou <Eliana@y.digital>, "public-shacl@w3.org" <public-shacl@w3.org>
I am partial to option 1, also with the restriction that only the primitive node kinds should be allowed in the list as others have mentioned. Matt Goldberg -----Original Message----- From: Eliana Papoutsoglou <Eliana@y.digital> Sent: Friday, July 11, 2025 10:55 AM To: public-shacl@w3.org Subject: [⚠️] [EXTERNAL]--Straw-poll: Issue 410 / Allowing list syntax Caution: This email originated from outside of Corning. Do not click links or open attachments unless you recognize the sender and know the content is safe. Report phishing by using the “Report Phishing” button or forward the email to Phishyemails@corning.com. Hi all, As discussed in our last meeting, this is a straw poll to help us assess the group's position on PR #410: "feat: #407 add support for sh:TripleTerm to sh:nodeKind and allow lists." https://github.com/w3c/data-shapes/pull/410 The main point of contention is whether lists should be allowed. On one hand, lists offer a more user-friendly syntax that can better accommodate new use cases compared to the current sh:or. On the other hand, allowing lists may introduce performance issues. If the group does decide in favour of allowing lists, there will be additional options to explore (such as simplifying use through node expression functions). However, for this vote, I would like to keep the focus on whether they should be allowed in the spec at all. This is a straw poll to gauge preferences. Please indicate your preferred option: 1) Lists should be allowed. 2) Lists should not be allowed. The poll will remain open for 10 days, until the WG meeting on July 21st at 14:00 CET. Please submit your response before then. Kind regards, Eliana
Received on Friday, 18 July 2025 16:47:11 UTC