dc:description) will normally be a summary of the whole DR but this doesn't prevent a
dc:descriptionbeing provided of, say, just the Descriptors. The discussion then turned to how to express package scope. The resolution was that as a minimum, you SHOULD defined a white space separated list of hosts covered by a package (using
wdr:aboutHosts) and you MAY further define an RS but be warned that not all processors will honour it. Package scope is a processing hint - the DRs in the package are not guaranteed to cover all the resources given in the package scope. Work is being done on showing how to use DR data in a rules-based environment. It is anticipated that this will show how the data can be expressed precisely and efficiently and may lead to further improvements in the spec. The group discussed how to include multiple blocks of Descriptors in a single DR. The idea of a separate
wdr:includepredicate for this purpose was dropped in favour of simply using a parseType="Collection" attribute on the hasDescriptors predicate. The section on efficient data representation (using XML entity declarations etc.) will be moved the the POWDER Primer but will be referred to in the specification document. Finally, a proposal to make
includeHostsmandatory in Resource Set definitions was not approved. Individual DR creators (a.k.a. labelling authorities) may operate Web Services where includeHosts is guaranteed to be present but this need not apply universally.