Opened 10 years ago

Closed 8 years ago

#15 closed defect (fixed)

move "comparison" into separate document?

Reported by: lmm@… Owned by:
Priority: minor Milestone:
Component: 3987bis Version:
Severity: - Keywords:
Cc:

Description

The section on the comparison ladder contains a number of heuristics and best practices about practical IRI comparison which is likely to evolve over time. I think it would be better to move this into a separate "best practices" document.

Change History (2)

comment:1 Changed 10 years ago by lmm@…

  • Priority changed from major to minor

917a982,984

<t>((NOTE: It has been suggested that this section move to a separate
document as Best Practice.))</t>

1195,1197c1262,1265
< is no way for an implementation to compare two resources to determine
< if they are "the same" unless it has full knowledge or control of
< them. For this reason, determination of equivalence or difference of
---

is no way, in general, for an implementation to compare two resources to determine
if they are "the same".

For this reason, determination of equivalence or difference of

1214c1282
< their respective target IRIs before comparison. When IRIs are compared
---

their respective absolute IRIs before comparison. When IRIs are compared

1216c1284
< representation, fragment components (if any) should be excluded from
---

representation, fragment components (if any) SHOULD be excluded from

1224,1225d1291
< </section> <!-- equivalence -->
<

comment:2 Changed 8 years ago by masinter@…

  • Resolution set to fixed
  • Status changed from new to closed

draft-masinter-iri-comparison splits out this section and provides a new introduction. That document probably could use substantial work, but at least the split is made.

Note: See TracTickets for help on using tickets.