Re: Buyer / Seller / Provider Re-Design

+1 Proposal Beta


> consumer <> buyer <> broker <> seller <> provider

looks to me like very nice way to draw distinctions between various roles!


> Proposal Alpha
> Deprecate all other uses of provider under a new property
"serviceProvider".

why Product can't have provider, does schema:manufacturer acts as
equivalent property for products?


> The domain would be: BusTrip, Flight, Reservation, Service, TrainTrip

adding TaxiTrip, FerryTrip, Rideshare etc. would require adjusting
domain every time, maybe worth introducing Trip and moving all specific
transport modes to subtypes? similar to http://schema.org/Reservation


> In both proposals, it was overly difficult to find a term that
satisfied the needs of
> expressing entities involved in offering nonmonetary / noncommercial
goods and services.
>The end result was a recommendation to overload usage of ‘seller’ for
these scenarios w/ a description clarifying this additional,
nontraditional usage.

THANK YOU for keeping in mind nonmonetary / noncommercial cases! :)





On 08/01/2014 06:00 PM, Jason Johnson (BING) wrote:
> Hi All,
> 
>  
> 
> Following up on a thread which went stale back in June, Vicki and Dan @
> Google + myself formalized the prior public discussions into a pair of
> alternative vocabulary re-designs.  We then generated a (hopefully)
> canonical set of use cases to help validate and map those alternatives. 
> We would like to re-start the stale discussion using this more formal
> proposal in the hopes that we can drive consensus ASAP.
> 
>  
> 
> https://www.w3.org/wiki/File:ProviderSellerVocabularyRe-DesignProposal.pdf
> 
>  
> 
> Please read through the PDF and …
> 
> - provide feedback on the proposed model of exchanges
> 
> - provide feedback on the two alternative proposals, ideally favoring
> one more than the other (we can’t decide ourselves)
> 
> - review the canonical examples we have generated and share any that we
> are missing – especially if neither alternative vocab addresses them
> 
>  
> 
> We hope to move forward with one of these solutions ASAP and look
> forward to your input!
> 
>  
> 
> Thank you,
> 
>  
> 
> *Jason Johnson*
> 
> Microsoft//
> 
>  
>

Received on Sunday, 3 August 2014 20:44:18 UTC