Published Subjects Definitions Requirements and Examples

maybe you just need publishers to say "this is a published subject indicator"

Recommendation 1 :

A Published Subject Indicator should provide human-readable metadata.

Recommendation 2 :

A Published Subject Indicator should provide machine-processable metadata.

Machine-processable metadata is recommended so that applications can use more information on the subject than solely URI identification.

Human-readable as well as machine-processable metadata can be included in the Subject Indicator itself (e.g. RDF metadata), or in a separate resource referenced from the Subject Indicator (e.g. XTM metadata). Deliverable 2 will provide complementary recommendations on the nature of those metadata.

Recommendation 3 :

Metadata defined in 1 and 2 should be consistent, but not necessary equivalent.

Consistency between human-readable and machine-processable metadata is the warrant of consistent "interpretation" by applications and humans. This can be achieved, for example, by human-readable metadata being an expression of machine-processable metadata. This issue will be addressed by Deliverable 2.

Recommendation 4 :

Published Subject Indicator should indicate that it is intended to be a PSI.

This statement of purpose has to be clearly endorsed by the publisher (see below).

Recommendation 5 :

Published Subject Indicator should identify its publisher.

Publisher is to be understood here in its Dublin Core definition: "An entity responsible for making the resource available."

Statement of purpose and Publisher identification are the warrants of trust, fundamental to efficient PSI mechanism.

Event Broker