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 5678 - locid is missing from schema in editors draft
Summary: locid is missing from schema in editors draft
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-07 02:18 UTC by Julia McCarthy
Modified: 2008-05-22 18:15 UTC (History)
0 users

See Also:


Attachments

Description Julia McCarthy 2008-05-07 02:18:27 UTC
The editors draft available on 5/6/2008 no longer has a definition for sml:locid in the schema (Appendix A).
Comment 1 Kumar Pandit 2008-05-07 17:01:17 UTC
I do see the following present in the latest draft. Can you provide a link to the draft that does not have this?

   <!-- CONTEXT: To be used in <sch:assert>, <sch:report>
         and elements with textual content.
         This attribute is used to support string localization.
         It is used to define the translation location for 
         the text content of the containing element.-->
     
    <xs:attribute name="locid" type="xs:QName"/>
Comment 2 John Arwe 2008-05-08 14:15:58 UTC
current editor's draft: http://dev.w3.org/cvsweb/~checkout~/2007/xml/sml/build/sml.html?content-type=text/html;%20charset=utf-8
I don't see locid defined in App A (normative schema)
I find locid in 7, 9.7.1, and App F (non-normative) only.
Comment 3 Julia McCarthy 2008-05-20 17:04:10 UTC
It was the draft linked as the "Editor's Copy" to the SML workgroup page (http://www.w3.org/XML/SML/) on the date I opened this bug. (I checked 4 times.) The draft linked there today does indeed have locid in the schema. I don't have a link to the older version, but as long as the current one is OK, we can close this bug.
Comment 4 Pratul Dublish 2008-05-22 18:15:11 UTC
As per the resolution in 5/22 call