W3C home > Mailing lists > Public > public-vocabs@w3.org > October 2013

Re: Attaching a time interval to schema:PostalAddress

From: Thad Guidry <thadguidry@gmail.com>
Date: Thu, 24 Oct 2013 10:00:55 -0500
Message-ID: <CAChbWaPb8SLN+gg=cqd-NN+o7hTzsKusEpuSoVB7gxB-yd8HPA@mail.gmail.com>
To: Marc Twagirumukiza <marc.twagirumukiza@agfa.com>
Cc: SchemaDot Org <public-vocabs@w3.org>
I think the ContactPoint is the appropriate place.

A person or business has a ContactPoint (an email, phone, fax, postal
address) that is valid and current for a given date range.
So the date range should be available for ContactPoint....not only the
specific PostalAddress, which is just one element of a ContactPoint.

my opinion,



On Thu, Oct 24, 2013 at 9:15 AM, Marc Twagirumukiza <
marc.twagirumukiza@agfa.com> wrote:

> Dear Schema.org community,
> We are trying to attach a time interval to schema:PostalAddress structure,
> and we hesitate with two suggestions. Can you advise?
> Here are suggestions (sorry to send them in turtle):
>
> ##1. RESIDENCY
> <http://example.org/resource/Natperson/person1#this>
>         schema:hasResidentialStatus <
> http://example.org/resource/Residency/100#this>.
>
> <http://example.org/resource/Residency/100#this>
>         a schema:ResidentialStatus;
>         schema:address <
> http://example.org/PostalAddress/PostalAddress1#this>;
>         schema:startDate "2009-11-01T09:00:00Z"^^xsd:dateTime;
>         schema:endDate  "2009-11-01T09:00:00Z"^^xsd:dateTime.
>
> ##2. ADDRESSES
> <http://example.org/PostalAddress/PostalAddress1#this>
>         a schema:PostalAddress;
>         schema:streetAddress "Via Pietro Panzeri";
>         schema:postalCode "20139";
>         schema:addressLocality "Milan";
>         schema:addressRegion  "MI";
>         schema:addressCountry [a schema:Country; schema:name "Italy"].
>
> This suggest to extend Schema.org with one predicate
> ("schema:hasResidentialStatus") and one class ("schema:ResidentialStatus")
>
> The second suggestion is to combine all in one structure model  and use
> schema:contacType
> ##3. ADDRESSES
> <http://example.org/PostalAddress/PostalAddress1#this>
>         a schema:PostalAddress;
>             Schema:contacType [ schema:startDate
> "2009-11-01T09:00:00Z"^^xsd:dateTime; schema:endDate
>  "2009-11-01T09:00:00Z"^^xsd:dateTime];
>         schema:streetAddress "Via Pietro Panzeri";
>         schema:postalCode "20139";
>         schema:addressLocality "Milan";
>         schema:addressRegion  "MI";
>         schema:addressCountry [a schema:Country; schema:name "Italy"].
>
> What do you think on two models?
>
> Kind Regards,
> *
> Marc Twagirumukiza | **Agfa HealthCare*
> Senior Clinical Researcher | HE/Advanced Clinical Applications Research
> T  +32 3444 8188 | M  +32 499 713 300
>
> http://www.agfahealthcare.com
> http://blog.agfahealthcare.com
>  ------------------------------
> Click on link to read important disclaimer:
> http://www.agfahealthcare.com/maildisclaimer
>
>
>
> From:        Robert Kost <rkost@thematix.com>
> To:        SchemaDot Org <public-vocabs@w3.org>
> Date:        24/10/2013 15:51
> Subject:        Cascading Types in a Meta Tag
> ------------------------------
>
>
>
> Hi
>
> Dumb question #347:
>
> *How does one nest RDFa type declarations in a <meta> tag?*
>
> For example, the copyrightHolder of a CreativeWork is an Organization.
>  Since the copyright holder isn’t explicitly stated on the page, it has to
> be declared in a <meta> tag.   But this doesn’t look right:
>
> <div id="namespaces" prefix="schema: *http://schema.org/*<http://schema.org/>“>
>
> <div typeof="schema:VideoObject”>
> <meta property="copyrightHolder" typeof="schema:Organization"
> property="name" content=“Some Company"/>
> ...
> </div>
> </div>
>
> I know this is elementary stuff, but a fair amount of googling around
> failed to provide an answer, so I look to someone here.
>
> regards,
>
> Rob
>



-- 
-Thad
Thad on Freebase.com <http://www.freebase.com/view/en/thad_guidry>
Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>
Received on Thursday, 24 October 2013 15:01:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:32 UTC