- Any RDF schema can be included in a contentLabel
- Generalised rules can be written based on a few contentLabels that can affect unlimited and, as yet, non-existent resources
- Useful directly if the service profile defines acceptable content types
So it’s easy to add DC data or any other schema’s data to a content Label
Direct usefulness for content adaptation example: an ISP/publisher might offer a filtered access service. They would define what that meant using the ICRA vocabulary. The CMS can then match content descriptions against that profile. The profile might be under direct parental control if desired.