- From: Karen Coyle <kcoyle@kcoyle.net>
- Date: Wed, 28 Aug 2013 09:36:54 -0700
- To: public-vocabs@w3.org
One possible solution is to have a property for "parent organization" - this avoids any specificity as to the relationship but does establish the basics. There are numerous types of parent/child relationships in organizations, including very complex ones in government and corporations. It will not be possible to name them all, and in many cases the exact relationship is not commonly known. kc On 8/28/13 6:54 AM, Thad Guidry wrote: > I agree with Martin and Tom Morris' example in the proposal. We are > also trying to squeeze too much into a single type, at times. > > We still need this idea of a "department" that holds 3 things primarily, > and what webmasters are looking for. > > 1. A relationship to a parent LocalBusiness. ( Just need a property of a > "department" under LocalBusiness). > +1 I am fine with Martin's suggestion of a property called > "departmentOf", just like we have "branchOf" that expects a new type > called "LocalBusinessDeparment" (This avoids the squeezing so much into > a single type problem) > > 2. Borrow the property for openingHours from LocalBusiness. (I am 50/50 > on the promotion of openingHoursSpecification to a Place. The dreaded > squeezed type problem again) > > 3. Borrow the property for contactPoint from Organization. > > Reduce, Reuse, Recycle... we should be heavy on the Reuse / Recycle of > properties, and less so on the Reduce (promotion), since Reduce causes > more confusion than worth, typically. > . > -- > -Thad > Thad on Freebase.com <http://www.freebase.com/view/en/thad_guidry> > Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/> -- Karen Coyle kcoyle@kcoyle.net http://kcoyle.net ph: 1-510-540-7596 m: 1-510-435-8234 skype: kcoylenet
Received on Wednesday, 28 August 2013 16:37:23 UTC