Iriset Notes ((HOT))
Download File >> https://urloso.com/2t7kXH
We formally interpret the above as follows: there is an OWL classcontaining all resources that share all of these properties, and thereis an OWL class of all resources denoted by iriset, and the latteris a subset of the former. In POWDER-S we say:
A POWDER processor is free to choose any traversal policy for treating multiple iriset elements in a DR: first match wins, last match wins, shortest iriset first, and so on, as long as all iriset elements are tried before deciding that DR does not apply to a candidate resource (candidate resource is defined in the Grouping of Resources document [GROUP]). However, DR authors may use the order of the iriset elements to suggest an efficient scope evaluation strategy, by putting the iriset with the widest coverage first, so that a processor that chooses to follow the iriset elements in document order is more likely to terminate the evaluation after fewer checks.
For each IRI set in the DR, two classes are defined: one that represents all resources that are members of the IRI set (as in the earlier examples) and another that defines all the resources that are not members of the IRI set (how this is done is the subject of Section 4). In the example these are given the nodeIDs iriset_n and iriset_n_not.
The following assertion is made: the intersection of the iriset of the current DR and the 'not' irisets from all preceding DRs is subsumedunder the descriptorset (or tagset) of the current DR. (Note that there must be only one IRI set generated for each DR, possibly using owl:unionOf, regardless ofhow the POWDER/XML original is expressed.)
It follows that the first DR in the list yields a simple sub class relationship between its IRI set(s) and descriptor set(s); and that the final DR in the list's 'iriset_not' is not used and may safely be omitted.
It is now possible to express includeregex and excluderegex asowl:hasValue restrictions [OWL] on wdrs:matchesregex and wdrs:notmatchesregex respectivelyand build up an OWL Class to represent the IRI set in the POWDER-S encoding. Furthermore,asserting a rdfs:subClassOf relationship between an iriset and adescriptorset expresses the claim that the resources in the former are describedby the latter.
Similarly, the union of wdrs:notmatchesregexrestrictions is used to define the complements of iriset classes, forthe purpose of expressing ordered lists of DRs(see Section 3.1 above). In this manner,the iriset_1_not and iriset_2_not classesof Example 3-8 are defined as follows:
It should be noted that iriset classesare not implicitly intersected with the aboutregexclass, and it is the responsibility of the POWDER document author toensure that all IRI sets in the document are within the scopedefined by abouthosts/aboutregex.
Such an extension makes it possible to provide semantics to iriset byconstructing an RDF datatype for each iriset and restricting the values ofhasIRI to this datatype's range.In this manner, the POWDER-S translation ofExample 4-4 becomes as shown inExample 4-7, where iriset_1is a class of abstract resources, the concrete IRI string of which iswithin a user-defined datatype (lines 20-29 and 37-46). 2b1af7f3a8