W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2004

Fwd: Access to date and time information

From: Tom Adams <tom@tucanatech.com>
Date: Wed, 14 Jul 2004 16:18:05 -0400
Message-Id: <EA3EC158-D5D2-11D8-8D0C-000A95C9112A@tucanatech.com>
To: public-rdf-dawg@w3.org

FYI:


Begin forwarded message:

Resent-From: public-rdf-dawg-comments@w3.org
From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: 12 July 2004 10:22:47 PM
To: public-rdf-dawg-comments@w3.org
Subject: Access to date and time information


Dear RDF Data Access Working Group,

   http://www.w3.org/TR/2004/WD-rdf-dawg-uc-20040602/#u2.4 seems to
motivate a requirement that is not listed in the draft. At some point
in the process, the software needs to know the current date and time
for example to avoid to schedule the recording of outdated items, or
it needs to know how to group dates to weeks in order to present the
index page for each week's recorded items.

Another use case here would be a software program to remind working
groups of the "Heartbeat" Requirement using TR Automation [2]; a query
language could enable a query for all the technical reports not in an
end state that are older than 2 1/2 month, or all groups that published
a technical report that is not in an end state, that have not published
an update of one of those drafts for 2 1/2 months.

Hmm, this also motivates Requirement 3.7, "Limited Datatype Support";
since there is so far only one use case that motiviates datatype
support, it might be good to add this motivation to the Monitoring News
Events use case.

[1] http://www.w3.org/Consortium/Process/process.html#three-month-rule
[2] http://www.w3.org/2002/01/tr-automation/


-- 
Tom Adams                  | Tucana Technologies, Inc.
Support Engineer           |   Office: +1 703 871 5312
tom@tucanatech.com         |     Cell: +1 571 594 0847
http://www.tucanatech.com  |      Fax: +1 877 290 6687
------------------------------------------------------
Received on Wednesday, 14 July 2004 16:18:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:20 GMT