- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 17 Jan 2008 13:17:22 +0000
- To: public-sml@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5384 ------- Comment #1 from johnarwe@us.ibm.com 2008-01-17 13:17 ------- I think they are expressing the same concept in different words. fwiw, "equivalent" might be confusing here. I usually see that in the context of how to normalize/compare URIs, e.g. RFC 3986 section 6.1: 6. Normalization and Comparison . . . . . . . . . . . . . . . . . 38 6.1. Equivalence . . . . . . . . . . . . . . . . . . . . . . 38 Given our current rules around URI comparison, I don't think we need to invoke "equivalent" or any variation. We already define what equality (the strongest form of equivalence) means to SMLIF, and don't need anything weaker IIRC. Net, I'd strike all phrases that appear to relate URIs and any form of equivalence other than straight equality.
Received on Thursday, 17 January 2008 13:17:31 UTC