- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Nov 2021 08:15:03 +0000
- To: public-dxwg-wg@w3.org
Thanks for the link Dan - I think it is addressing a more complex problem around the interaction of syntax with multiple alternatives - whereas I was just talking about the basic pattern of referencing a context by URL:
{ "@context = [ "http://my.org/context" , "http://your.org/context" ] }
If these context files map default prefixes for vocabularys and support either "prefix:item" or "item" forms then AFAIK application profiles can simply use "item" where there is no class of term names between namespaces and "prefix:item"when disambiguation is needed.
The weird thing is I have really seen this written up anywhere yet it seems so obvious - and even if there was a good reason it coudlnt work I would have expected to have seen some angst about it. Maybe we've all missed it but it would be good to surface any reason this won't work... or just do it.
--
GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1428#issuecomment-973852727 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 November 2021 08:15:05 UTC