- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Nov 2021 01:55:32 +0000
- To: public-dxwg-wg@w3.org
@danbri - you make a good point that there may be different underlying architectural assumptions about implementation constraints. I think the appropriate non-absolutist approach however is to address this directly and provide examples for both implementation patterns - not assume any given pattern is a personal whim. Admittedly this is tricky in that there is no universally accepted reference architecture - I will argue that objectively the practices I suggested are well established for some relevant architectural styles. I would also note that they do not preclude the usage you consider - systems determine what their behaviour should be re following links - and if you dont or cant then you simple pre-load resources you need (varying from harcoding to caching when networks are available). Named, modular contexts actually support that by making it obvious how to go safely offline and dark with minimal pre-loading. Ad-hoc cut and paste style means you need to load a lot more if you have multiple schemas - but may be more efficient if your system only needs to know about one message - which is probably common enough we should call out examples. Just not sure its a key use case for DCAT however? -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1428#issuecomment-982206258 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 30 November 2021 01:55:34 UTC