OASIS DocBook TC2

  • 1.  5.1 next steps

    Posted 03-16-2016 14:27
    Hi folks, I asked Chet about SoUs. They don’t have to be organizational members, but if they are, we need to get the Primary Rep to confirm. So I think we can probably craft three amongst us. It’d be nice to get an organizational member, though. For the independent implementation question, there’s no defined meaning. If we think we have demonstrated interoperability, then we can say so, otherwise we can’t. Roughly. My guess is we can demonstrate interoperability. Be seeing you, norm -- Norman Walsh <ndw@nwalsh.com> To create a little flower is the http://www.oasis-open.org/docbook/ labour of ages.--Blake Chair, DocBook Technical Committee Attachment: signature.asc Description: PGP signature


  • 2.  RE: [docbook-tc] 5.1 next steps

    Posted 03-16-2016 14:37
    Hi, I can probably get such SoU from LexisNexis representative. Although DocBook is not company standard, some people use it for documentation on some projects. Do we have some draft of such SoU? Many thanks in advance, Jirka
    Original Message


  • 3.  RE: [docbook-tc] 5.1 next steps

    Posted 03-16-2016 14:52
    https://www.oasis-open.org/policies-guidelines/tc-process#dStatementUse Here is a typical SoU template: ORGANIZATION has successfully used the STANDARD vX Committee Specification 01, approved DATE, in accordance with section X. The implementation includes all STANDARD features; they interoperate with multiple independent implementations. Documents that are created by ORGANIZATION make particular use of the following structures that were added to STANDARD vX: * X * Y * Z Regarding Interoperability, here's something from the DITA list: ----------- From: Chet Ensign <chet.ensign@oasis-open.org> To: Kristen James Eberlein <kris@eberleinconsulting.com> Date: Thu, 20 Aug 2015 13:40:40 -0400 No, so far as I know, OASIS does not have a definition of interoperation. I think all the definitions you provided qualify. Product A being able to produce a document that Product B can consume and use as expected certainly qualifies. Also, Eliot's point is well taken - there is interoperable content and interoperable systems. So I have no objection at all to the notion that *if* you can produce conforming DITA content. My point for the statement of use is that the qualification in the definition is that the statement is to a fact "... included multiple independent implementations" not to a concept "... can support interoperation." So, e.g., if you tested your implementation using DITA content produced by someone else, as far as I'm concerned, you can say 'included multiple independent..." That is the nuance I'm pointing out. --Chet ------------- Best regards, --Scott
    Original Message


  • 4.  RE: [docbook-tc] 5.1 next steps

    Posted 03-16-2016 14:38
    As much as I would like to, Boeing does not provide SoUs. We couldn't provide for DITA 1.3 either. Company policy, I'm afraid. Thanks, --Scott
    Original Message


Related Content