TimeInRangeFunction has wrong identifier

Description

The org.herasaf.xacml.core.function.impl.nonNumericComparisonFunctions.TimeInRangeFunction is implemented with function-id "urn:oasis:names:tc:xacml:2.0:function:time-in-range".
The specification of this function defines the identifier as "urn:oasis:names:tc:xacml:1.0:function:time-in-range" (mind the 1.0 vs. 2.0).

Environment

None

Activity

Show:
Colm O hEigeartaigh
October 31, 2012, 12:39 PM

This JIRA is invalid IMO. The XACML Core 2.0 spec mentions both a "1.0" and a "2.0" "time-in-range" function. However, the XACML 1.x specification does not define "time-in-range" at all. Therefore, the "2.0" version is correct, and no change is needed to the codebase.

See here for further validation:

https://lists.oasis-open.org/archives/xacml-comment/200808/msg00004.html

> > the document
> xacml-3.0-profile-webservices-spec-v1-wd-10 mentions the
> > urn:oasis:names:tc:xacml:1.0:function:time-in-range
> function, which does
> > not exist. It has only been introduced in XACML 2.0.
>
> Oh well, worse than that. XACML 2.0 defines both of these
> functions:
>
> urn:oasis:names:tc:xacml:1.0:function:time-in-range (page
> 114)
> urn:oasis:names:tc:xacml:2.0:function:time-in-range (page
> 99)
>
> and in XACML 3.0 wd 06, it is still wrong.

Colm.

Peter Doornbosch
November 1, 2012, 8:47 AM
Edited

LOL

Well, if the specification is inconsistent and mentions both (and i now agree it does), i think the best thing the implementation can do is to implement both.

The reasoning that 'the XACML 1.x specification does not define "time-in-range" at all, therefore, the "2.0" version is correct' seems to make a lot of sense, but formally speaking it's "just" an interpretation. I think it's not up to us (i.e. XACML implementors / XACML users) to reason and make assumptions about what the specification committee probably would have meant; we should stick to what the specification says, regardsless of whether we agree with it or not.

So, i (formally) don't agree with the statement that this issue is invalid, but well, i can live with Heras sticking to "urn:oasis:names:tc:xacml:2.0:function:time-in-range".

Assignee

Unassigned

Reporter

Florian Huonder

Labels

None

Components

Fix versions

Affects versions

Priority

Major
Configure