Thanks Richard
That is enormously helpful.. i had worked out some of that by diving and
playing.. but great to see it laid out.
The list of properties that get inherited is really helpful, and the
rationale behind viewClass.
Rob
On Thu, 12 Jul 2018, 20:17 Richard Cyganiak wrote:
> Hi Rob,
>
Hi Rob,
> On 12 Jul 2018, at 01:22, rob.atkin...@surroundaustralia.com wrote:
>
> BTW - still trying to get my head around why sometimes a viewClass is used
> and sometimes an instance of such a class - both seem to co-exist in EDG -
> but whats the reason for using instances - and do they just
On 12/07/2018 10:22, rob.atkin...@surroundaustralia.com wrote:
Thanks Holger
very helpful...
On 11/07/2018 22:56, rob.at...@surroundaustralia.com
wrote:
I want to set up some common metadata that a suite of services
implemented in SWP can access.
I have a superclass
Thanks Holger
very helpful...
> On 11/07/2018 22:56, rob.at...@surroundaustralia.com wrote:
>
> I want to set up some common metadata that a suite of services implemented
> in SWP can access.
>
> I have a superclass of services, and in the header I can use a named graph
> to persist infor
On 11/07/2018 22:56, rob.atkin...@surroundaustralia.com wrote:
I want to set up some common metadata that a suite of services
implemented in SWP can access.
I have a superclass of services, and in the header I can use a named
graph to persist information - because AFAICT it appears that name
I want to set up some common metadata that a suite of services implemented
in SWP can access.
I have a superclass of services, and in the header I can use a named graph
to persist information - because AFAICT it appears that named graphs are
the only mechanism for sharing context outside nested
