This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5399 - SML typos
Summary: SML typos
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Kumar Pandit
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-22 13:27 UTC by John Arwe
Modified: 2008-01-22 20:21 UTC (History)
0 users

See Also:


Attachments

Description John Arwe 2008-01-22 13:27:15 UTC
1. Introduction, 1. SML references 
"does support references within elements in the same document through xs:ID,"
replace "within" with "between" to "to"

4.2.2 Consistent References
from: scheme resolves to a target that's different from the target resolved to
to:   scheme resolves to a target        different from the target resolved to

4.2.4 Multiple References
context: An element in a document MAY be targeted by multiple reference elements. These reference elements 
from: These reference elements 
to  : The referencing elements
(this one is optional.  it is not especially hard to read the existing text correctly, the revision simply reads more clearly to me)

4.2.5 Null References
from: 4.2.5 Null References
to  : 4.2.5 SML Null References
for consistency with 4.1.2

4.2.5 Null References
from: A      null reference is 
to  : An SML null reference is 

4.2.6 deref() XPath Extension Function, item 1
from: recognizes no scheme used in the reference,   then deref() returns no target for R.
to  : recognizes no scheme used in the reference R, then deref() returns no target for R.
(both before and after this spot we refer to the reference element as R already)

4.2.6 deref() XPath Extension Function, item 2.c
from: resolves to a target that's different from
to  : resolves to a target        different from

4.3 Reference Schemes, final paragraph
from: A schema definition MAY impose
to  : A scheme definition MAY impose
             -
4.3.1 SML URI Scheme, item 2
from:                                The SML URI scheme is resolved using
to  : An SML reference element using the SML URI scheme is resolved using
(this makes it consistent with item 1 same list)

4.3.1 SML URI Scheme, item 2.a
from: sans
to  : ignoring any

4.3.1 SML URI Scheme, item 2.a
from: appropriate operation defined for the     scheme used in that URI reference
to  : appropriate operation defined for the URI scheme used in that URI reference
(this is a particularly important place to fix an unqualified use of "scheme", since this "scheme" refers to the URI scheme within a particular instance of the SML reference scheme... I realize we have a separate bug to weed out all unqualified "scheme" uses, but it would be too easy to get this one wrong)

4.3.1 SML URI Scheme, item 4
Need to be sure we define the BNF syntax elements, like ::=, used here.  Did not see that we already did so.  Probably a matter of pointing to where that syntax is defined.  RFC3986 probably contains such a pointer in its references.  Goes in section 2.1

4.3.1.1 The smlxpath1() scheme, item 1
from: Scheme name: smlxpath1.
to  : Scheme name: smlxpath1
(i.e. remove the trailing period, lest someone believe that is part of the literal)

4.4 Constraints on References
The {property-name} notation was borrowed from XML Schema.  Should be attributed in section 2.1

4.4 Constraints on References, target*
from: And 3             new properties
to  : SML defines three new properties
(consistency with the acyclic text above this)

4.4.1 sml:acyclic
from: sml:acyclic is used to specify that           a cycle is not allowed 
to  : sml:acyclic is used to specify whether or not a cycle is not allowed

4.4.1 sml:acyclic
from: allowed for an SML reference      type
to  : allowed on instances of a complex type 

4.4.2.1 Mapping from schema, item 2.b
from: then{target element}  of ED is the same as that of EB.
to:   then {target element} of ED is the same as that of EB.
          -
4.4.2.2 Schema Validity Rules, item 2
from: If 2   element
to  : If two element
Comment 1 Kumar Pandit 2008-01-22 20:21:48 UTC
All of the changes made as suggested.