- From: SWD Issue Tracker <dean+cgi@w3.org>
- Date: Thu, 3 Apr 2008 02:02:30 +0000 (GMT)
- To: public-swd-wg@w3.org,public-rdf-in-xhtml-tf@w3.org
ISSUE-112: Last Call Comment: describe algorithm in functional terms, too http://www.w3.org/2006/07/SWD/track/issues/112 Raised by: Ben Adida On product: RDFa raised by Micah Dubinko in [1]: """ In addition to the procedural "Sequence" description in section 5.5, include a functional description of the algorithm. Often times, a functional description is better suited for describing an algorithm to implementers, even if the eventual code will closely follow the sequence of steps given in section 5.5. The process of translating the sequence description into functional terms will help improve the quality of the specification, make any algorithm errors or areas that are unclear or difficult to implement stand out better, resulting in a smoother call-for-implementations period. Obviously, people actually implementing in a functional language (including XSLT/GRDDL) will find the beneficial as well. What is a functional description? Any number of possible descriptions would qualify, but the essential constraints of a functional description are: * no side-effects or state * no mutable variables <http://en.wikipedia.org/wiki/Functional_programming> For example, a functional description be structured as a series of statements like this: * For each <condition on node> produce a triple with <rule for subject> <rule for predicate> <rule for object> I am personally interested in contributing on the list or wiki to flesh out the details of a functional description. I prefer a final result with normative weight, though. """ Requires discussion. [1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0379.html
Received on Thursday, 3 April 2008 02:03:02 UTC