Looking good, Jean-Pierre. However on PublicationEvent... > - The addition of the PublicationEvent, inheriting from the existing > Event class. Two sorts of publication events are covered: broadcast events (to > allow EPG events to be describe in a way understandable to search engines to > fin content and services providing such content within a given area) and on > demand events (NOTE: from an EBU and BBC perspective, such events are freely > accessible. I may make sense to add the property Œfreeš as a Boolean to Event > in order to differentiate free event from access controlled events and go form > more complete on demand descriptions associated to transactional services..) However such an Event specialisation could be also be used in a book/journal publishing context. So the descriptive text, to prevent confusion for other event based extensions, could read something like: a PublicationEvent corresponds indifferently to the event of publication for a CreativeWork of any type e.g. a broadcast event, an on-demand event, a book/journal publication, via a variety of delivery media In which case I would suggest the Œfreeš boolean may well reside better at the inheriting class level. ~Richard. -- Richard Wallis Technology Evangelist OCLC
Received on Monday, 18 June 2012 19:47:54 UTC