[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [xacml] functions specifications
In general - we can reuse there list of references as well, shortened 1 Normative Clinger, WD (1990) William D Clinger. How to Read Floating Point Numbers Accurately. In Proceedings of Conference on Programming Language Design and Implementation, pages 92-101. Available at: ftp://ftp.ccs.neu.edu/pub/people/will/howtoread.ps IEEE 754-1985 IEEE. IEEE Standard for Binary Floating-Point Arithmetic. See http://standards.ieee.org/reading/ieee/std_public/description/busarch/754-19 85_desc.html Namespaces in XML World Wide Web Consortium. Namespaces in XML. Available at: http://www.w3.org/TR/1999/REC-xml-names-19990114/ RFC 2396 Tim Berners-Lee, et. al. RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax.. 1998. Available at: http://www.ietf.org/rfc/rfc2396.txt The Unicode Consortium. The Unicode Character Database. Available at: http://www.unicode.org/Public/3.1-Update/UnicodeCharacterDatabase-3.1.0.html XML 1.0 (Second Edition) World Wide Web Consortium. Extensible Markup Language (XML) 1.0, Second Edition. Available at: http://www.w3.org/TR/2000/WD-xml-2e-20000814 XML Schema Requirements World Wide Web Consortium. XML Schema Requirements. Available at: http://www.w3.org/TR/1999/NOTE-xml-schema-req-19990215 2 Non-normative Character Model Martin J. Durst and Francois Yergeau, eds. Character Model for the World Wide Web. World Wide Web Consortium Working Draft. 2001. Available at: http://www.w3.org/TR/2001/WD-charmod-20010126/ Gay, DM (1990) David M. Gay. Correctly Rounded Binary-Decimal and Decimal-Binary Conversions. AT&T Bell Laboratories Numerical Analysis Manuscript 90-10, November 1990. Available at: http://cm.bell-labs.com/cm/cs/doc/90/4-10.ps.gz HTML 4.01 IETF INTERNET-DRAFT: IRIs L. Masinter and M. Durst. Internationalized Resource Identifiers 2001. Available at: http://www.ietf.org/internet-drafts/draft-masinter-url-i18n-07.txt ISO 11404 ISO (International Organization for Standardization). Language-independent Datatypes. See http://www.iso.ch/cate/d19346.html ISO 8601 ISO (International Organization for Standardization). Representations of dates and times, 1988-06-15. Available at: http://www.iso.ch/markete/8601.pdf ISO 8601 Draft Revision ISO (International Organization for Standardization). Representations of dates and times, draft revision, 2000. U.S. Naval Observatory Time Service Department Information about Leap Seconds Available at: http://tycho.usno.navy.mil/leapsec.990505.html Unicode Regular Expression Guidelines Mark Davis. Unicode Regular Expression Guidelines, 1988. Available at: http://www.unicode.org/unicode/reports/tr18/ XML Schema Language: Part 2 Primer World Wide Web Consortium. XML Schema Language: Part 2 Primer. Available at: http://www.w3.org/TR/2001/REC-xmlschema-0-20010502/ -----Original Message----- From: Polar Humenn [mailto:polar@syr.edu] Sent: Friday, September 06, 2002 11:32 AM To: Daniel Engovatov Cc: XACML Subject: RE: [xacml] functions specifications On Fri, 6 Sep 2002, Daniel Engovatov wrote: > Some of this is recommended, with appropriate standards cited in this > document: http://www.w3.org/TR/xmlschema-2/ Can you point out which ones? Thanks, -Polar > > > > -----Original Message----- > From: Polar Humenn [mailto:polar@syr.edu] > Sent: Friday, September 06, 2002 8:45 AM > To: XACML > Subject: [xacml] functions specifications > > > > We need explicit specifications or pointers to specifications for the > certain functions. A specification should include the exact type (i.e. > xs:string, xs:dateTime, etc) of its arguments and the exact type of its > return value. Also, we need explicit, if not formal semantics for the > function's behavior. > > Note, their type signature is not sufficient. If we cannot find > specifications for the following, I'd just assume we leave them out. > However, that might not be good for some of the functions that we think > are necessary. > > I'm reluctant to issue defintions for these things, because, I'm not up on > internationalization of strings, and I'm definiately not familiar with the > nuances of XML processing. For instance, "string-equal" works two > arguments of xs:string. In XML, what do you do with leading and trailing > whitespace or mulitiple lines? Does leading and trailing white space get > ignored, or reduced, etc.? I'll bet *everybody* had a different approach. > > The following functions need specification: (They are also listed in the > Functions Document I put on the list with [NEED SPECIFICATION]. Here's a > compiled list. > > return 1st Arg 2nd Arg > type > string-equal xs:boolean xs:string xs:string > Q: leading and trailing spaces, multiple lines, etc. > > date-equal xs:boolean xs:date xs:date > time-equal xs:boolean xs:time xs:time > dateTime-equal xs:boolean xs:dateTime xs:dateTime > anyURI-equal xs:boolean xs:anyURI xs:anyURI > > x500Name-equal xs:boolean xs:x500Name xs:x500Name > Q: Do we have an adequate specification on this from pkix? > > rfc822Name-equal xs:boolean xs:rfc822Name xs:rfc822Name > hex-equal xs:boolean xs:hex xs:hex > Q: Is the type xs:hex or xs:hexBinary? > Q: leading and trailing spaces, multiple lines, etc. > > base64-equal xs:boolean xs:base64 xs:base64 > Q: Is the type xs:base64 or xs:base64Binary? > Q: leading and trailing spaces, multiple lines, etc. > > string-greater-than xs:boolean xs:string xs:string > string-greater-than-or-equal xs:boolean xs:string xs:string > Q: leading and trailing spaces, multiple lines, etc. > Q: What if two different international strings? > > > time-greater-than xs:boolean xs:time xs:time > time-greater-than-or-equal xs:boolean xs:time xs:time > Q: Are these relative to only one day? with Timezones? > > date-greater-than xs:boolean xs:date xs:date > date-greater-than-or-equal xs:boolean xs:date xs:date > datetime-greater-than xs:boolean xs:date xs:date > datetime-greater-than-or-equal xs:boolean xs:date xs:date > > string-match xs:boolean xs:string xs:string > rfc822Name-match xs:boolean xs:rfc822Name xs:rfc822Name > x500Name-match xs:boolean xs:x500Name xs:x500Name > > Ann has a whole lot of other functions in the compliance tests such > as: > > add-dayTimeDurations > subtract-dayTimeDuration-from-time > > of which I still do not know how they are to proceed. I don't even know if > we have a type for a datTimeDuration or what it looks like. Does anybody? > > I suggest that we leave all of these out, especially if we cannot come up > with specifications for them. We can add them later when people do figure > out how they want them to operate. > > Cheers, > -Polar > > > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC