W3C home > Mailing lists > Public > public-i18n-its@w3.org > October to December 2005

[Bug 2620] Necessity of dislocated scope / selectors *and* insitu scope / selectors

From: <bugzilla@wiggum.w3.org>
Date: Mon, 26 Dec 2005 08:45:54 +0000
To: public-i18n-its@w3.org
Message-Id: <E1EqnzO-0000xm-Qv@wiggum.w3.org>


           Summary: Necessity of dislocated scope / selectors *and* insitu
                    scope / selectors
           Product: ITS
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ITS tagset
        AssignedTo: fsasaki@w3.org
        ReportedBy: fsasaki@w3.org
         QAContact: public-i18n-its@w3.org

Comment from Francois Richard, only entered into bugzilla by Felix:

Currently, an ITS implementation has to decide whether it wants to use in situ
or dislocated scope / selectors. Would it be possible to use only dislocated
scope / selectors, and in situ only without selectors (but with a default scope
for each data category)? That would make the conflict resolution between in situ
and dislocated easier, and the overall design of ITS, without loosing expressive
power of selectors (since every in situ selector can be expressed dislocated as
Received on Monday, 26 December 2005 08:45:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:06 UTC