OASIS Darwin Information Typing Architecture (DITA) TC

 View Only
  • 1.  Groups - Draft of the DITA 1.2 XSDs (xsd1.2-20090723.zip) uploaded

    Posted 07-23-2009 18:50
    Hello,
    
    Some cleanup and updates:
    
    * Added @keys to topichead
    * Removed new note types caution1 and caution2
    * Included a couple of fixes to learning modules (class attribute fixes in
    learningDomain.mod, set a default of no-topic-nesting for *-info-types in
    topic modules) 
    
    I also added the following information (the following is just an example)
    to all Domain and Mod files.
    
    
    
    Each file has a copy of the value that should appear in the domains
    attribute in the schema shells.  In the DTDs, these values are found in the
    .ent files.  The intention is that applications that assemble modules to
    generate a new shell would be able to look at the annotation to generate
    the domains attribute value.  
    
    I think we still need to add an id to the 


  • 2.  Re: [dita] Groups - Draft of the DITA 1.2 XSDs (xsd1.2-20090723.zip)uploaded

    Posted 07-23-2009 19:24
    On 7/23/09 1:49 PM, "esirois@ca.ibm.com" 


  • 3.  Re: [dita] Groups - Draft of the DITA 1.2 XSDs (xsd1.2-20090723.zip) uploaded

    Posted 07-28-2009 14:45

    Hi Eliot,

    I had thought about the idea, but wanted add the info in such a way that it would detract from getting things out the door for 1.2.  Thus the simpler model.  I can easily pull things out in an update if there's an issue. I'm definitely open to ideas.  I hope that we can get things in 1.2 without having too much affect on where we are in the current pipeline.

    If we were going to make use of a namespace, I think that the DITA Architecture namespace would suffice (http://dita.oasis-open.org/architecture/2005/).  It's an existing namespace and one that would not require too much additional work.  It would also seem fitting since the domains attribute is one of the architecture attribute.

    Eric

    NOTE to members:  This change does not have any affect on the XSDs or DTDs with respect to the validation on DITA documents.  This is metadata that applications may make use of to help generate XSD shells or to determine the hierarchy of a particular module.  There would be an update to the architectural spec if we wanted to externalize the information.


    Eric A. Sirois
    Staff Software Developer
    DB2 Universal Database - Information Development
    DITA XML Schema Architect and DITA Open Toolkit Developer
    IBM Canada Ltd. - Toronto Software Lab
    Email:
    esirois@ca.ibm.com
    Phone:(905) 413-2841

    Blue Pages (Internal)

    "Transparency and accessibility requirements dictate that public information and government
    transactions avoid depending on technologies that imply or impose a specific product or
    platform on businesses or citizens" - EU on XML-based office document formats.



    From: Eliot Kimber <ekimber@reallysi.com>
    To: Eric Sirois/Toronto/IBM@IBMCA, dita <dita@lists.oasis-open.org>
    Date: 07/23/2009 03:27 PM
    Subject: Re: [dita] Groups - Draft of the DITA 1.2 XSDs (xsd1.2-20090723.zip) uploaded





    On 7/23/09 1:49 PM, "esirois@ca.ibm.com" <esirois@ca.ibm.com> wrote:

    > I also added the following information (the following is just an example)
    to
    > all Domain and Mod files.
    >
    > <xs:annotation>
    >     <xs:appinfo>(map classify-d)</xs:appinfo>
    >     <xs:documentation>
    >    
    >     </xs:documentation>
    > </xs:annotation>
    >
    > Each file has a copy of the value that should appear in the domains
    attribute
    > in the schema shells.  In the DTDs, these values are found in the
    .ent files.
    > The intention is that applications that assemble modules to
    generate a new
    > shell would be able to look at the annotation to generate
    the domains
    > attribute value.
    >
    > I think we still need to add an id to the <xs:annotation> so that we
    > can
    differentiate/highlight that this particular one is used for @domains.

    Why not define a new element type in a DITA-specific namespace for use
    within appinfo, e.g.:

    <xs:appinfo>
     <domainsUsed
    xmlns="
    http://www.dita.org/namespaces/appinfo"
    >(map classify-d)</domainsUsed>
    <xs:appifo>

    Cheers,

    E.

    ----
    Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
    email:  ekimber@reallysi.com <
    mailto:ekimber@reallysi.com>
    office: 610.631.6770 | cell: 512.554.9368
    2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
    www.reallysi.com <http://www.reallysi.com>  | http://blog.reallysi.com
    <
    http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>


    ---------------------------------------------------------------------
    To unsubscribe from this mail list, you must leave the OASIS TC that
    generates this mail.  Follow this link to all your TCs in OASIS at:
    https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php





  • 4.  Re: [dita] Groups - Draft of the DITA 1.2 XSDs (xsd1.2-20090723.zip)uploaded

    Posted 07-28-2009 15:34
    On 7/28/09 9:44 AM, "Eric Sirois"