[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: [tab] Including XSLT as a artifact w/i the OASIS Process
|
From: Chet Ensign [mailto:chet.ensign@oasis-open.org]
Well you could certainly publish it in a CN. It could be part of the spec as well, even if you needed to identify it as non-normative. Toby, I was also reminded that there was once an XSLT Conformance TC. You could have a look and see how they handled that. https://www.oasis-open.org/committees/xslt /chet On Fri, Jun 14, 2013 at 2:32 PM, Considine, Toby <Toby.Considine@unc.edu> wrote: We have a blanket statement “The Artifacts are Normative”, which is of course more nuanced than that. What I *think* you are saying, martin, is that the XSLT, if published, is actually a “Committee
Note” tc "When one door closes, another opens; but we often look so long and so regretfully upon the closed
door that we do not see the one which has opened for us."
-- Alexander Graham Bell
From: Martin Chapman [mailto:martin.chapman@oracle.com]
This is a slightly tricky one. Ignoring the licensing issue, I am not sure what it means for s/w or a
script to be normative. I can see the formats of the source and targets being normative plus a description of how to map from one the other also being normative, but as for the xslt itself I am not so sure that it is more than just a supporting tool. Doesn’t
mean to say its shouldn’t be done (and eventually licensed), I am just not sure how normative it is. Just my two €0.2c Martin. From: Chet Ensign [mailto:chet.ensign@oasis-open.org]
Hi Toby, You can certainly incorporate XSLT into your spec. The Board IPR committee is talking now about what may need to be done differently re copyright and license.
I'll get back to you with that. But feel free to move forward with the XSLT itself. /chet On Fri, Jun 14, 2013 at 10:06 AM, Considine, Toby <Toby.Considine@unc.edu> wrote: When we defined oBIX 1.0 some years ago, we did not produce any normative artifacts such as XML Schemas
(XSD, et al.) with the package. We intend to in the future. In some ideal world, these new schemas would be fully conformant with some more recent best practices. In particular, as oBIX has potential use w/I a variety integrations environments that involve
the US government it would be nice to be NIEM conformant. This offers the possibility of breaking backward compatibility, which we do not wish to do. On the
other hand, we are tightening conformance. If conformance is useful, it inherently breaks compatibility with all those applications that do not conform. In other words, we know that backward compatibility cannot be an absolute. If you read the thread below, you see a statement that [we] could publish an XSLT that does the translations.
I am not aware of a normative XSLT in the OASIS world, but that may well be only my ignorance… Can you provide some guidance / thoughts on publishing XSLT within the TC process? tc "When one door closes, another opens; but we often look so long and so regretfully upon the closed
door that we do not see the one which has opened for us."
-- Alexander Graham Bell
From: Considine, Toby
Very interesting, Chris. If we can deliver a standard XSLT with the package for conversion old-oBix to new-oBIX, that can
give us a bit more freedom. I do not know about including XSLT as part of a standard w/I the OASIS process. I will look into
it and report back. tc "When one door closes, another opens; but we often look so long and so regretfully upon the closed
door that we do not see the one which has opened for us."
-- Alexander Graham Bell
From:
obix@lists.oasis-open.org [mailto:obix@lists.oasis-open.org]
On Behalf Of Chris Bogen Submitter's message
--
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
-- Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]