Re: Candidate 1.0f release: bugfixes, Offer generalized for non-profit use.

On Wed, Jan 22, 2014 at 12:26 PM, Dan Brickley <> wrote:

> I've made a test build of a 1.0f release, at
> draft release notes:
> """1.) Several Minor fixes reported by Dan Scott
> <>
>  *
>   - typo in "availablity": "A list of possible product availablity
> options." should be "A list of possible product availability options."
> * - invalid note in docs. The description
> says "NOTE: Candidate for promotion to ScholarlyArticle." when in fact
> the property was promoted from ScholarlyArticle to CreativeWork.
>  * still has no
> encoding declaration in the <head> element or HTTP header. This can
> cause difficulties for parsers: Add <meta charset="UTF-8" /> to head.
> 2.) Textual changes to Offer that support not-for-profit offers.
> * via
> * Thanks to Dan Scott again for the proposed RDFS diff
> <>.
> This broadens the definition of Offer and makes associated changes to
> ItemAvailability and OfferItemCondition, typically rewording "the item
> for sale" to simply say "the item". The itemOffered property is now
> defined more appropriated as "The item being offered." rather than
> "...sold.". The "seller" property is now defined as "The organization
> or person making the offer.", a compromise to support its use for more
> kinds of offer."""
> See and nearby for most of this.
> Thanks Dan x2, and the bibextend team. Unless someone catches a
> mistake, we'll proceed to publish this shortly. "Many eyes", and all
> that..

Looks great! I've diffed the current vs. the sdopending version,
and all of the changes are good (and thorough). Nice to see a few of the
properties getting arranged in proper alphabetical order, as well (yes, I
looked that closely--heh!)

Thanks Dan!

Received on Thursday, 23 January 2014 03:18:19 UTC