Re: Proposal to extend rangeIncludes of DataTypes predicates in schema.org

XSD dateTime element requires a format of "YYYY-MM-DDThh:mm:ss" where all
components are required.

The HTML <time> element represents either a time on a 24-hour clock OR a
precise date in the Gregorian calendar (with optional time and timezone
information).

There is not a 1:1 match to dateTime in XSD.

However, one could use <xs:complexType mixed="true"> in XSD to probably
emulate the mostly complex HTML <time> element.  No ?


On Thu, Nov 13, 2014 at 8:30 AM, martin.hepp@ebusiness-unibw.org <
martin.hepp@ebusiness-unibw.org> wrote:

> On 10 Nov 2014, at 16:54, Gregg Kellogg <gregg@greggkellogg.com> wrote:
>
> >> 2. It may also be that you want to encourage Web sites to add XSD
> datatype information to schema.org properties. This will not work, IMO,
> because
> >> a) this is impossible in Microdata syntax (no datatype at instance
> level)
> >
> > Not entirely true, a conforming Microdata to RDF processor will output a
> matching @datetime or element content value for a <time> element as a typed
> literal using the matching xsd datatype. What Google does, however, may be
> different.
> >
> > Gregg
> >
>
> Yes, <time> is a special case. But also note the complexity of that
> special case: https://wiki.whatwg.org/wiki/Time_element. Not sure whether
> there is a 1:1 match to xsd datatypes.
>
> Martin
>
>
>


-- 
-Thad
+ThadGuidry <https://www.google.com/+ThadGuidry>
Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>