- From: Nicholas Car <nick@kurrawong.ai>
- Date: Tue, 28 Oct 2025 07:58:08 +0000
- To: Andy Seaborne <andy@apache.org>
- Cc: public-shacl@w3.org
- Message-ID: <lNFAgQOMjxkFOQ9kjDZRXh0iutc47s_c464of8b2i8TrI0V-DMRKCOJO9AsSW_tvcoHFJ6GReFr6HWA>
The problem with having the particular things suggested in this section outside of the Profiling doc is that some of the further sections in that doc will depend on the particular practices being followed. So while I can think of other Best Practices that should go into such a Note, the 3 recommended here are tied to the Profiling work. Nick On Monday, 27 October 2025 at 23:02, Andy Seaborne <andy@apache.org> wrote: > "best practices" might be better as a Note or on a wiki. Something easier to update - including removing advice, of changing it in non-compatible ways. > > "Profiling" is on the track to be a standard (REC) - it gets frozen at the point of publication. > > Andy > > On 27/10/2025 08:02, Nicholas Car wrote: > >> Re-request to review Packaging recommendations > > - @nicholascar: updated request to review Packaging recommendations > > - https://raw.githack.com/w3c/data-shapes/shacl-packaging/shacl12-profiling/index.html#packaging > - I have removed the tricky Named Graph / quads references > - I am interested in what other recommendations we would all make to SHACL users for how else they might package SHACL, not just for Profiling tasks but for any other purposes. I do think it sensible to convey what we think is Best Practice
Received on Tuesday, 28 October 2025 07:58:19 UTC