Add further restriction on PolicyShape to target AustGovt licenses

[nicholascar]

Ensure that the EUDM licenses not only have at least one permission but that individuals come from a particular register - the list of Aust Govt licenses this project will set up. Assume a license register of http://test.linked.data.gov.au/license/ for testing.

Just let me know if this restriction is not advisable or too hard to make.

[dr-shorthair]

Do you mean

(a) the odrl:hasPolicy property of a EUDM Distribution should point to an AU License, which is an instance of an odrl:Policy

or

(b) the odrl:permission property of a EUDM Policy should point to an AU Permission, which is an instance of an odrl:Permission?

Either is easy to do.

[nicholascar]

The Distribution will need to have a hasPolicy pointing to an AU License (that it a license in that register, not a thing of class AU License). That AU License will need to have a permission pointing to a Permission subClassOf Rule. This is to guard against the (probably unlikely) event of an AU License that grants no permissions being selected for use. We can fabricate one to prove the point.

So the interesting bit is in the AU License being in the particular register, as we discussed. Why don't you constrain this on AU_License_X reg:register <http://test/linked.data.gov.au/license/> .? This will be the formal way to indicate membership in that register and I use reg:register for all memberships like this.

A stretch goal would be a constraint that allows an AU License to be in a subregister of the .../licese/ register too, since this may occur.

We may think of a better constraint on the AU License instances around permissions later but can use this trivial constraint now for testing. I think the register restriction though is real.