2015-09-24 12:25 GMT+02:00 Makx Dekkers <mail@makxdekkers.com>:
> All,
>
> >
> > > I think this is what you should do. Unless the two sites correspond to
> > > the same site.
> >
> > I don't follow. I do mean that they are one and the same site.
> > Say I have an organization O with site S1. And S1 has a registration
> address
> > Ar1 and a postal address Ap1. Would I then have to model an additional
> > instance S1'
> > representing the same site just to express the different addresses?
> >
>
> I don't understand how one site (=physical location) can have two
> different addresses, one the registration address and one the postal
> address.
> Or is the issue that an *organisation* can have a postal address that is
> different from the registration address? If that is the issue, I'd argue
> that two different addresses are associated with different physical
> locations. E.g. the physical location of a post office box is at the post
> office, not at the location where the organisation has its office.
>
> Makx.
>
>
Yes, if an organisation is registred at a PO box somewhere that would be a
different site. The organization vocabulary has taken this into account,
see the description of org:hasSite <http://www.w3.org/ns/org#hasSite>:
*"Indicates
a site at which the Organization has some presence even if only indirect
(e.g. virtual office or a professional service which is acting as the
registered address for a company)"*. Both org:hasPrimarySite and
org:hasRegistredSite are subproperties of org:hasSite, so this remark goes
for those properties too.
Regards,
Frans