Re: Commonly supported properties

 >I need to encode postal addresses and phone numbers for businesses (not
 >people) in some RDF I'm working on. Is there any particular existing
 >vocabulary that I should prefer over another for this application?

For representing a business, I would also recommend importing the 
GoodRelations ontology from

http://purl.org/goodrelations/v1

and represent the legal entity as an instance of

http://purl.org/goodrelations/v1#BusinessEntity

You can then attach the address and phone number etc. to that instance.

If you have branches or shop locations of the same legal entity, those 
should be instances of

http://purl.org/goodrelations/v1#LocationOfSalesOrServiceProvisioning
 
Also here, you can attach vCard attributes easily.

If you need an example, just drop a note. For more info, see 
http://purl.org/goodrelations/

Best
Martin
-------------------
martin hepp
Richard Cyganiak wrote:
> On 14 Feb 2009, at 20:01, Bob Wyman wrote:
>> I need to encode postal addresses and phone numbers for businesses (not
>> people) in some RDF I'm working on. Is there any particular existing
>> vocabulary that I should prefer over another for this application?
>
> vCard in RDF is the canonical one:
> http://www.w3.org/2006/vcard/ns#
>
> Best,
> Richard
>
>
>>
>>
>> bob wyman
>>
>> On Sat, Feb 14, 2009 at 11:20 AM, Jay Luker <lbjay@reallywow.com> wrote:
>>
>>> Hi all,
>>>
>>> I'm interested in getting people's thoughts on a particular line 
>>> from the
>>> "How to publish Linked Data on the Web" tutorial. Specifically the
>>> following...
>>>
>>> "It is common practice to mix terms from different vocabularies. We
>>> especially recommend the use of 
>>> rdfs:label<http://www.w3.org/TR/rdf-schema/#ch_label>and
>>> foaf:depiction <http://xmlns.com/foaf/0.1/#term_depiction> properties
>>> whenever possible as these terms are well-supported by client 
>>> applications."
>>>
>>> I'm curious about a couple of things in regards to this: a) does anyone
>>> know what "client applications" the authors might be referring to, 
>>> and b)
>>> are there examples of other properties that enjoy similar support?
>>>
>>> Thanks,
>>> --jay
>>>
>
>
>