relax-ng message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [relax-ng] Future of RELAX NG
- From: "David RR Webber \(XML\)" <david@drrw.info>
- To: "MURATA Makoto \(FAMILY Given\)" <eb2m-mrt@asahi-net.or.jp>
- Date: Wed, 28 Mar 2007 07:38:21 -0700
Makoto,
Yes - it is work to submit the RNG spec' to OASIS member ballot - and
given that ISO have already approved it - the value would not come solely from SDO adoption.
Notice that the OASIS staff ONLY promote specifications that
have full member approval. Therefore I strongly suggest we look at submitting RNG to member ballot - so that OASIS staff can then formally promote RNG - if that is our goal here.
The reason they did not reply to you is in part because of this factor -
they cannot give any special treatment to specifications that are not OASIS approved standards.
Most other TC's are gaining OASIS member approval ballots on their way
to ISO submission. There is always one bird that fly's north it seems somewhere! ; -)
This would also garner RNG visibility on the website - and get us a
docs.oasis-open.org/relax-ng area and wiki - all essential to better promotion.
I believe we already have grandfathered in committee spec' approval
right now. Not sure we ever did OASIS member review (I recall we may have) - if we did - then we are one very short step away from member adoption.
So the steps to OASIS approval would be - (this could start with 1)
- but skip to 5) if grandfathered:
1) Re-format existing RNG spec' to latest OASIS doc template - (cut and
paste job) - IPR statement - and RNG schemas - insert copyright statement.
2) TC level ballot to approve doc as committee spec' for OASIS member
review.
3) Submit to 60 day OASIS member review.
4) After review - address comments (if any)
5) 3 verification / use statements from member companies
6) Submit to member ballot.
Actually an alternate plan - would be to have Apache.org adopt RELAX NG
- which I believe would be a much more direct route to the user community? I've not had any success reaching the inner sanctum at Apache in the past - but maybe some of our members here have personal contacts they can leverage?
DW
"The way to be is to do" - Confucius (551-472 B.C.)
-------- Original Message --------
Subject: [relax-ng] Future of RELAX NG
From: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp>
Date: Tue, March 27, 2007 11:22 pm
To: relax-ng@lists.oasis-open.org
Folks,
The OASIS RNG TC has two procedural problems: RELAX NG is NOT an
OASIS
standard, and the OASIS RELAX NG TC does not obey to the OASIS Liaison
Policy,
which imposes constraints on submitting OASIS specs to other
standardization organizations.
http://www.oasis-open.org/committees/liaison_policy.php
I have contacted OASIS people about procedural and IPR issues but
they
do not respond.
SC34 has had some discussions on the maintenance of RELAX NG in Oslo on
3/22.
OASIS is a category-A liaison of SC34. This means that members of
the RELAX NG TC
can participate in SC34 meetings. Voting is different, since only
P-members
of SC34 are allowed to vote.
To avoid the two procedural problems mentioned above, I think that
the
best way to go forward is:
(1) SC34 the authoritative committee for the RNG specification,
(2) members of the OASIS RNG TC paricipate in discussions
by e-mail or F2F,
(3) the OASIS RNG TC continues to make the OASIS committee specification
identical to 19757-2,
(4) the OASIS RNG TC maintains what has not been standardized by SC34.
That is, RELAX NG Tutorial, Guidelines for using W3C XML
Schema Datatypes with RELAX NG, and RELAX NG Compact
Syntax
(which is only partially standardized by SC34.)
(5) the OASIS RNG TC can do promotion and education.
How do people feel? Some people feel that ISO/IEC is not important
in
the US, but I would argue that the ODF .vs. OOXML issue reminds me of
ISO/IEC.
Cheers,
--
MURATA Makoto (FAMILY Given) <EB2M-MRT@asahi-net.or.jp>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]