On 14/11/13 20:28, Martynas Jusevičius wrote:
OK. One more question - most of the examples I was looking at (like
the one from StackOverflow) use simple integer values like
"11"^^xsd:gMonth, and not the "--11"^^xsd:gMonth syntax. But strictly
speaking, these are illegal values?
Yes - strictly i
OK. One more question - most of the examples I was looking at (like
the one from StackOverflow) use simple integer values like
"11"^^xsd:gMonth, and not the "--11"^^xsd:gMonth syntax. But strictly
speaking, these are illegal values?
On Thu, Nov 14, 2013 at 9:11 PM, Andy Seaborne wrote:
> On 14/11
On 14/11/13 18:29, Martynas Jusevičius wrote:
BTW, there seems to be a related question on StackOverflow:
http://answers.semanticweb.com/questions/610/ordering-by-time-in-sparql-query
I might just give up building an xsd:dateTime and use separate
year/month/day components.
On Thu, Nov 14, 2013
BTW, there seems to be a related question on StackOverflow:
http://answers.semanticweb.com/questions/610/ordering-by-time-in-sparql-query
I might just give up building an xsd:dateTime and use separate
year/month/day components.
On Thu, Nov 14, 2013 at 7:26 PM, Martynas Jusevičius
wrote:
> Andy,
Andy, now I'm confused. Where are you looking? I checked the RDF/XML
version of Time ontology and it says:
On Thu, Nov 14, 2013 at 7:10 PM, Andy Seaborne wrote:
> On 14/11/13 16:42, Martynas Jusevičius wrote:
>>
>> OK I was probably too quick - n
On 14/11/13 16:42, Martynas Jusevičius wrote:
OK I was probably too quick - now I realized the syntax of xsd:gMonth
and xsd:gDay is not so simple...
:-)
http://www.w3.org/TR/xmlschema11-2/#dateTime for details.
The range of time:month is a non-negative integer so may be single
digit. That'l
OK I was probably too quick - now I realized the syntax of xsd:gMonth
and xsd:gDay is not so simple...
On Thu, Nov 14, 2013 at 4:05 PM, Martynas Jusevičius
wrote:
> I came up with an approach that concatenates lexical values and
> doesn't need Calendar or DateTimeStruct.
>
> Not sure however how
I came up with an approach that concatenates lexical values and
doesn't need Calendar or DateTimeStruct.
Not sure however how this aligns with the range of time:inXSDDateTime
which is xsd:dateTime - can xsd:gYear/xsd:gMonthDay/xsd:date be
treated as xsd:dateTime values? I guess I'll have to typeca
I'll try DateTimeStruct again, but that basically means I need my own
copy of the class, since I currently cannot extend it to override the
private constructor?
On Thu, Nov 14, 2013 at 2:15 PM, Andy Seaborne wrote:
> Hi there,
>
> DateTimeStruct is, well, a struct. The fields are public. You cou
Hi there,
DateTimeStruct is, well, a struct. The fields are public. You could
write a builder to target that. The default constructor could be made
public. The statics are specific patterns for the XSD date/time
datatypes with validation.
DateTimeStruct represents the Date/time Seven-prop
Hey,
I have datetime components as 3 separate literals, with xsd:gYear,
xsd:gMonth, xsd:gDay respective datatypes. Not all mandatory - the
format can be , -MM, -MM-DD.
Now how do I combine those into a single xsd:dateTime Literal? A
concrete use case would be converting time:inDateTim
11 matches
Mail list logo
