W3C home > Mailing lists > Public > public-swd-wg@w3.org > August 2009

Re: Transition Request: SKOS to Proposed Recommendation

From: Alistair Miles <alimanfoo@gmail.com>
Date: Tue, 4 Aug 2009 09:32:05 +0100
To: Felix Sasaki <felix.sasaki@fh-potsdam.de>
Cc: "Phillips, Addison" <addison@amazon.com>, Guus Schreiber <schreiber@cs.vu.nl>, SWD WG <public-swd-wg@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, pda@tbaker.de
Message-ID: <20090804083205.GA4132@skiathos>
Dear Felix,

On Fri, Jul 31, 2009 at 02:12:29PM +0200, Felix Sasaki wrote:
> Dear Alistair (personal response and response as AC of University of Applied
> Sciences Potsdam),
> 
> I do not agree with your resolution. You need to take out all examples and
> suggestions for using language subtags for notations, syntactic modification
> of the examples is not enough. As Martin and me pointed out before, using
> language tags for non-language items like notations is a very bad
> suggestion, hindering the application of SKOS for multilingual data in the
> future.

Personally, I am happy to do as you suggest. I will put it to the
SWDWG asap.

Thanks for your response,

Alistair

> 
> Regards, Felix.
> 
> 2009/7/31 Alistair Miles <alimanfoo@gmail.com>
> 
> > Dear Addison,
> >
> > Thank you for raising this issue, apologies for the delayed response.
> >
> > The SWDWG discussed this issue [1] at its teleconference on 7 July [2]
> > and made the following resolution:
> >
> > RESOLUTION: We (a) modify the example(s) in [SKOS Reference section]
> > 6.5.4 to be syntactically conformant to BCP 47 and (b) offer to add a
> > phrase such as "note that such use of private subtags to transmit data
> > unrelated to language or language choice may violate BCP 47"
> > contingent on Alistair and Sean's agreeing
> >
> > Both Sean [3] and myself find this resolution acceptable.
> >
> > Could you please indicate whether this resolution is sufficient to
> > meet your concerns. We realise this is short notice, but we would be
> > extremely grateful if you could respond with approval by 10 August, or
> > with any further concerns as soon as possible.
> >
> > Many thanks,
> >
> > Alistair
> >
> > [1] http://www.w3.org/2006/07/SWD/track/issues/224
> > [2] http://www.w3.org/2009/07/07-swd-minutes.html#item04
> > [3] http://lists.w3.org/Archives/Public/public-swd-wg/2009Jul/0014.html
> >
> > On Mon, Jun 29, 2009 at 02:23:14PM -0700, Phillips, Addison wrote:
> > > The Internationalization Core WG has a problem with this document that
> > should be corrected before a transition is approved. This was discussed
> > during our most recent teleconference [1] in response to comments by Felix
> > Sasaki [2] (and others, in that thread).
> > >
> > > During Last Call, I18N did review this document and made comments about
> > the use of BCP 47 language tags for language identification in the prefLabel
> > construct. I18N was satisfied by these changes. However, for whatever
> > reason, we did not notice that there were several problematic uses of the
> > prefLabel language tags elsewhere in the reference document. Specifically,
> > section 6.5.4 proposes to use language tags for additional uses. We have the
> > following concerns:
> > >
> > > 1. The language tag examples do not meet IETF BCP 47 "well-formed"
> > criteria. BCP 47 language tags limit subtag length to eight characters. The
> > examples in 6.5.4 are syntactically wrong as they are longer than eight
> > characters per subtag.
> > >
> > > 2. BCP 47 specifically recommends against using private-use subtags when
> > other mechanisms exist for data interchange. Use of private use subtags to
> > transmit data unrelated to language or language choice is frowned upon. The
> > examples given seem to confuse this or be in violation of this. We think
> > they need to be clarified and clarified in a way that removes the private
> > use subtags.
> > >
> > > Note that, although the IESG recently approved an update to RFC 4646
> > (part of BCP 47), this change has no impact on this specification or our
> > comments. We apologize for having missed this and think that the reference
> > and the related primer should (and can easily) be updated to address this
> > issue.
> > >
> > > Regards,
> > >
> > > Addison (for I18N Core WG)
> > >
> > >
> > > [1] http://www.w3.org/2009/06/24-core-minutes.html
> > > [2]
> > http://lists.w3.org/Archives/Public/public-i18n-core/2009AprJun/0068.html
> > >
> > > Addison Phillips
> > > Globalization Architect -- Lab126
> > > Chair -- W3C Internationalization WG
> > >
> > > Internationalization is not a feature.
> > > It is an architecture.
> > >
> > > > -----Original Message-----
> > > > From: chairs-request@w3.org [mailto:chairs-request@w3.org] On
> > > > Behalf Of Guus Schreiber
> > > > Sent: Monday, June 01, 2009 2:44 PM
> > > > To: Tim Berners-Lee; Steve Bratt; plh@w3.org
> > > > Cc: w3t-comm@w3.org; chairs@w3.org; SWCG; SWD WG
> > > > Subject: Transition Request: SKOS to Proposed Recommendation
> > > >
> > > > Director,
> > > >
> > > > The Semantic Web Deployment Working Group requests transition to
> > > > Proposed
> > > > Recommendation for
> > > >
> > > >    SKOS Simple Knowledge Organization System Reference
> > > >    [1] http://www.w3.org/TR/2009/CR-skos-reference-20090317/
> > > >
> > > > The updated editor's draft can be found at:
> > > >
> > > >    [2] http://www.w3.org/2006/07/SWD/SKOS/reference/20090315/
> > > > (Revision 1.13)
> > > >
> > > > The proposed STOD section reads as follows:
> > > >
> > > > [[
> > > >     This document is a W3C Proposed Recommendation published by the
> > > >     Semantic Web Deployment Working Group, part of the W3C Semantic
> > > > Web
> > > >     Activity.  This document reflects editorial changes arising
> > > > during
> > > >     the Candidate Recommendation review, summarized in the Changes
> > > >     section.  An implementation report documents known uses of SKOS
> > > >     during the Candidate Recommendation review period.  An updated
> > > >     SKOS Primer Working Draft is being published concurrently with
> > > > this
> > > >     Proposed Recommendation.
> > > >
> > > >     Comments on this document may be addressed to
> > > >     public-swd-wg@w3.org. Please include the text "SKOS
> > > >     comment" in the subject line. All comments sent to that address
> > > >     are available in a public archive.
> > > > ]]
> > > >
> > > > The record of the WG decision to request this transition is at:
> > > >
> > > >    [3] http://www.w3.org/2009/05/19-swd-minutes.html#item03
> > > >
> > > > No substantive issues were raised during CR, though a few comments
> > > > resulted in
> > > > editorial clarifications to the specification. Three CR comments
> > > > were received
> > > > and resolved, namely:
> > > >
> > > >      ISSUE-191: missing bracket in example 44
> > > >      http://www.w3.org/2006/07/SWD/track/issues/192
> > > >
> > > >      ISSUE-218: editorial errors and problems (Ch. 1)
> > > >      http://www.w3.org/2006/07/SWD/track/issues/218
> > > >
> > > >      ISSUE-219: name
> > > >      http://www.w3.org/2006/07/SWD/track/issues/219
> > > >
> > > > Changes from the Candidate Recommendation version are given in the
> > > > "Changes"
> > > > section of editors draft:
> > > >
> > > >    [4]
> > > > http://www.w3.org/2006/07/SWD/SKOS/reference/20090315/#changes
> > > >
> > > > There were no features at risk.
> > > >
> > > > The requirements have not changed since Candidate Recommendation.
> > > >
> > > > This specification has no normative references to W3C
> > > > specifications that are
> > > > not yet Proposed Recommendations.
> > > >
> > > > The Groups' implementation report [5] lists 27 implementations with
> > > > a broad
> > > > coverage of SKOS features.  All comments have received formal
> > > > responses; these
> > > > are recorded in the issue tracker [6].
> > > >
> > > >    [5]
> > > > http://www.w3.org/2006/07/SWD/SKOS/reference/20090315/implementatio
> > > > n.html
> > > >    [6] http://www.w3.org/2006/07/SWD/track/issues
> > > >
> > > >   The specification has therefore met the CR exit criteria:
> > > >
> > > > [[
> > > >     1. At least two implementations have been demonstrated that use
> > > >        features of the SKOS vocabulary.  Other vocabularies that
> > > > use
> > > >        SKOS are candidates for inclusion in the implementation
> > > > report.
> > > >     2. All issues raised during the CR period against this document
> > > >        have received formal responses.
> > > > ]]
> > > >
> > > > There have been no formal objections.
> > > >
> > > > There have been no changes to the patent disclosure pages since the
> > > > transition
> > > > to Candidate Recommendation. There are no open exclusion
> > > > opportunities.
> > > >
> > > > The Working Group intends to publish an updated version of the SKOS
> > > > Primer
> > > > Working Draft [7] at the same time as this Proposed Recommendation.
> > > >
> > > >    [7] http://www.w3.org/TR/skos-primer/
> > > >
> > > >
> > > >
> > > > Thomas Baker
> > > > Guus Schreiber
> > > > co-chairs Semantic Web Deployment WG
> > > >
> > >
> >
> > --
> > Alistair Miles
> > The Wellcome Trust Centre for Human Genetics
> > Roosevelt Drive
> > Oxford
> > OX3 7BN
> > United Kingdom
> > Web: http://purl.org/net/aliman
> > Email: alimanfoo@gmail.com **note change of email address**
> >
> >

-- 
Alistair Miles
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Web: http://purl.org/net/aliman
Email: alimanfoo@gmail.com **note change of email address**
Received on Tuesday, 4 August 2009 08:32:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:31:57 UTC