Next in thread →
Next in month →
FW: [tab] Including XSLT as a artifact w/i the OASIS Process
From: Chet Ensign [mailto:] Sent: Friday, June 14, 2013 3:26 PM To: Considine, Toby Cc: Martin Chapman; OASIS TAB Subject: Re: [tab] Including XSLT as a artifact w/i the OASIS Process 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 <> 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 Toby Considine Chair, OASIS oBIX TC Editor, OASIS EMIX, Energy Interoperation Campus Services Information Technology University of North Carolina Chapel Hill, NC Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org http://www.NewDaedalus.com From: Martin Chapman [mailto:] Sent: Friday, June 14, 2013 1:58 PM To: Chet Ensign; Considine, Toby Cc: OASIS TAB Subject: RE: [tab] Including XSLT as a artifact w/i the OASIS Process 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:] Sent: 14 June 2013 16:57 To: Considine, Toby Cc: OASIS TAB Subject: Re: [tab] Including XSLT as a artifact w/i the OASIS Process 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 <> 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 Toby Considine Chair, OASIS oBIX TC Editor, OASIS EMIX, Energy Interoperation Campus Services Information Technology University of North Carolina Chapel Hill, NC Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org http://www.NewDaedalus.com From: Considine, Toby Sent: Friday, June 14, 2013 9:59 AM To: 'Chris Bogen'; Subject: RE: [obix] Groups - oBIX 1.1 XML Schema: NIEM Refactoring WD03 uploaded 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 Toby Considine Chair, OASIS oBIX TC Editor, OASIS EMIX, Energy Interoperation Campus Services Information Technology University of North Carolina Chapel Hill, NC Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org http://www.NewDaedalus.com From: [mailto:] On Behalf Of Chris Bogen Sent: Friday, June 14, 2013 9:14 AM To: Subject: [obix] Groups - oBIX 1.1 XML Schema: NIEM Refactoring WD03 uploaded Submitter's message My final revision to the 1.1 schema for now. This .zip includes a revised wsdl that references the NIEM compliant schema and defines a separate schema file for the wsdl types. My recommendation here (as in the core xsd) is to drop the extension of the NIEM ComplexObjectType. For illustrative purposes I wanted to demonstrate full conformance to NIEM extension specs, so the extension is present in the working draft. Honestly I think NIEM is even less important in the context of the wsdl though it's perfectly fine to import a NIEM conformant oBIX core schema. In the deliberations I recommend that we weigh the benefits of NIEM conformance with the impact on existing oBIX XML bindings. The NIEM revisions will break existing xml bindings because of the upper case element names. We can get around that issue by providing a second schema that provides substitution groups with the old lower case element names. Also we can provide xslt to and from 1.0. -- Chris Bogen Document Name: oBIX 1.1 XML Schema: NIEM Refactoring WD03 Description This is a NIEM conformant refactor of Markus J.'s oBIX 1.1 xsd working draft. The oBIX schema files, NIEM dependencies, and log of NIEM conformance errors (relevant to original xsd draft) are included. Working Draft 2 Notes: Alphabetically sorted and grouped declarations. Working Draft 3 Notes: Added revised WSDL and supporting NIEM compliant WSDL type schema (oBIX_SOAP_Types.xsd). Note: Need to add annotations for each type. Download Latest Revision Public Download Link Submitter: Chris Bogen Group: OASIS Open Building Information Exchange (oBIX) TC Folder: Standards Date submitted: 2013-06-14 06:14:05 Revision: 2 -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open
Next in thread →
Next in month →