- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 24 Jun 2008 08:40:31 +0000
- To: public-sml@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5788 Summary: target complete identifiers - distinguish between before-normalization input and after-normalization output Product: SML Version: LC Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Core AssignedTo: cmsmcq@w3.org ReportedBy: johnarwe@us.ibm.com QAContact: public-sml@w3.org from f2f discussion, MSM base URI #1: 1. Apparent inconsistency in definition and use of the term 'target-complete' SML says (2.2): A target-complete identifier is a URI or IRI that contains all the information required to locate a target of an SML reference. It is a consequence of this definition that a target-complete identifier cannot be a relative URI/IRI. This seems to say explicitly that "relative URI/IRI" and "target-complete identifier" are disjoint classes. But SML 4.3 says of references defined by some arbitrary reference scheme: An SML reference scheme definition MUST specify all of the following: ... 3. An assertion that states whether or not the reference scheme uses target-complete identifiers. Using target-complete identifiers requires all the following: 2. If these references are allowed to be relative references, i.e. they are not already target-complete, then some implementation-dependent base URI or IRI is used to resolve them to URIs or IRIs. (See section 5 of [IETF RFC 3986] and section 6.5 of [IETF RFC 3987].) If "relative URI/IRI" and "target-complete identifier" are disjoint classes, this makes no sense. If 3b makes sense, then the claim in 2.2 about the consequence of the definition of "target-complete" is false. I don't think I care how this is resolved, only that the terms be used consistently. ---------------------- The discussion led to us agreeing that in 4.3, the target complete identifiers the SML URI ref scheme "uses" refers to the after-normalization form not the input markup an ordinary user would observe in an instance document. Neither "uses" nor "requires" was found to make this distinction adequately. MSM to update this bug with other suggestions. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 24 June 2008 08:41:06 UTC