Re: Encoding an incomplete date as xsd:dateTime

Hi all,

Scanning through old messages, I regret to say that I missed your
resolution of this issue prior to the Note being updated in May. If you
meant to follow the RFC, the resulting range is still to strict, since RFC
6350 says:

    The *default* is a single date-and-or-time value. *It can also be reset
to a single text value.*

And goes on to list examples:

             BDAY:19960415
             BDAY:--0415
             BDAY;19531015T231000Z
             BDAY;VALUE=text:circa 1800

The second and last values are not allowed according to the OWL, right?
Perhaps it should be documented somewhere that the vCard ontology is more
restrictive than the RFC.

Cheers,
Niklas



On Tue, Feb 11, 2014 at 4:55 AM, Renato Iannella <ri@semanticidentity.com>
wrote:

>
> On 11 Feb 2014, at 01:53, Niklas Lindström <lindstream@gmail.com> wrote:
>
> I would say that the vcard ontology formally needs to be fixed to allow
> for more variation. It actually seems to have been amended somewhat in 2010
> [4], to at least not require the exact second (or fraction thereof) of the
> birth.
>
>
> The latest working draft of the vCard Ontology [1] is based on RFC6350 [2]
> which defines birthday as: "The default is a single date-and-or-time value"
>
> We can add xsd:gYear to the range for the birthdate data property to
> support "year-only" birth dates.
> (and possibly to the anniversary property too)
>
>  Cheers...
> Renato Iannella
> Semantic Identity
> http://semanticidentity.com
> Mobile: +61 4 1313 2206
>
> [1] http://www.w3.org/TR/vcard-rdf/
> [2] http://tools.ietf.org/html/rfc6350
>
>