The most general classification of a person This class will display all the instances in the subclasses below it, as well as any organizations that were added as part of this generic class because there wasn't a specific class available. Only use if no specific subclasses of foaf:organization desribe the organization. A generic class encompassing several types of organizations. Ued to describe an organization related to bibliographic items such as a publishing company, etc. Agents are things that do stuff see: http://xmlns.com/foaf/spec/#term_Agent Used to describe any "agent" related to bibliographic items. Such agents can be persons, organizations or groups of any kind. A group can also be an organization but need not be; typically used for looser associations of people or organizations acting together in some fashion, not necessarily through formal agreement or on a long-term basis. Added to the VIVO ontology to be able to support informal and perhaps even private groups of people around an idea, funding opportunity, or event. see: http://xmlns.com/foaf/spec/#term_Group A collection of individual agents (and may itself play the role of a Agent, ie. something that can perform actions). Definition take from: http://xmlns.com/foaf/spec/#term_based_near . foaf indicates that the status of this term is "unstable". "The based_near relationship relates two "spatial things" (anything that can be somewhere), the latter typically described using the geo:lat / geo:long geo-positioning vocabulary (http://www.w3.org/2003/01/geo/wgs84_pos#). This allows us to say describe the typical latitute and longitude of, say, a Person (people are spatial things - they can be places) without implying that a precise location has been given." Used to link an agent, related to bibliographic things, to a place where it is based near: can be a city, a monument, a building, etc. http://xmlns.com/foaf/spec/#term_lastName. Note from foaf: "The lastName property is provided (alongside firstName) as a mechanism to support legacy data that cannot be easily interpreted in terms of the (otherwise preferred) familyName and givenName properties. The concepts of 'first' and 'last' names do not work well across cultural and linguistic boundaries; however they are widely used in addressbooks and databases." http://xmlns.com/foaf/spec/#term_firstName. Note from foaf: "The lastName property is provided (alongside firstName) as a mechanism to support legacy data that cannot be easily interpreted in terms of the (otherwise preferred) familyName and givenName properties. The concepts of 'first' and 'last' names do not work well across cultural and linguistic boundaries; however they are widely used in addressbooks and databases."