EM CAP SC

 View Only
  • 1.  From RIM SC: Inclusive CAP Documentation Hierarchy

    Posted 08-22-2024 16:36

    Hi Everyone,

    I was tasked by the RIM SC to send a my take on a possible (Spitball) self-referencing Documentation Hierarchy related to CAP Event Terms List work. (Jeez, it takes more words to describe than it does to just show it):

    Hierarchy for CAP Documentation (with agreed cross referencing):

    Top: CAP v1.2 or Current Standard document

    Second Level: Profiles (FEMA IPAWS, Environment Canada, Australian)

    Third Level: Event Terms List Committee Note v1…(?)

    Fourth Level:   Event Terms List Users Guide Committee Note or ?

                              Event Terms List Users Guide Definitions Note or ?

    My primary concern is that we appear to have embarked upon the mission, yea verily, of boiling the ocean (It snuck up on us.)

    My suggested goal: usability.

    Cheers,
    Rex



    ------------------------------
    [Rex] [Brooks] [Secretary, OASIS Open Emergency Management Technical Committee (EMTC);
    Chair, EMTC Reference Information Model Subcommittee (RIM SC)]
    [Principal]
    [Starbourne Communications Design, Knowledge Management]
    [Berkeley,] [California][USA]
    [(510) 898-0670]
    [rexb@starbourne.com][http://www.starbourne.com]
    ------------------------------


  • 2.  RE: From RIM SC: Inclusive CAP Documentation Hierarchy

    Posted 08-22-2024 17:53

    Hi Everyone, 

    I was reading our last SC Meeting Notes (Thanks Jeff) and it prompted me to draft the CAP Documentation Hierarchy I suggested,.

    I posted it to the CAP SC prior to our meeting tomorrow and I'm forwarding it back to this SC.

    This is just a spitball to get us all thinking about how to make all this work better so that we and our audience don't fall into an endless tail-chase.

    ��

    Rex


    -------- Forwarded Message --------
    Subject: EM CAP SC : From RIM SC: Inclusive CAP Documentation Hierarchy
    Date: Thu, 22 Aug 2024 20:35:52 +0000
    From: Rex Brooks via OASIS <Mail@mail.groups.oasis-open.org>
    Reply-To: OASIS-emergency-cap@ConnectedCommunity.org
    To: rexb@starbourne.com





  • 3.  RE: From RIM SC: Inclusive CAP Documentation Hierarchy

    Posted 08-22-2024 19:33

    A few more thankfully short thoughts,

    If you have the time read this week's RIM SC Meeting Notes. They're long but there's a lot that needed to be discussed.

    Elysa sugeested that we need to take these discussions and use them as the basis for updated Practices. With Guides, Practices and Notes, we have a lot more on our plates than we can get done by the Workshop for the twientieth anniversary of CAP, so we need to make some judicious decisions now. ��

    Last time, I promise!
    Rex

    On 8/22/2024 1:35 PM, Rex Brooks via OASIS wrote:





  • 4.  RE: From RIM SC: Inclusive CAP Documentation Hierarchy

    Posted 08-22-2024 21:33

    Hello from way down in the rabbit hole,

    If you go to the official published urls at https://docs.oasis-open.org you can find:

    https://docs.oasis-open.org/emergency/cap

    and follow the links you can find https://docs.oasis-open.org/emergency/cap-etl/v1.2/cn01/

    but you can't find https://docs.oasis-open.org/emergency/cap-etl/v1.2/cn02/

    However, if you go through the public-facing OASIS OPEN website you can find:

    Event Terms List Version 1.0
    Committee Note 02
    12 October 2021

    Editable source (Authoritative):
    https://docs.oasis-open.org/emergency/etl/v1.0/cn02/etl-v1.0-cn02.docx

    If you are not confused... you're a better nerd than me, Gunga Din

    We better get this straightened out.

    Cheers,
    Rex


    On 8/22/2024 1:35 PM, Rex Brooks via OASIS wrote:





  • 5.  RE: From RIM SC: Inclusive CAP Documentation Hierarchy

    Posted 08-23-2024 08:35

    That's seem a concern.

     

    It seems like that most users will be using cn1 instead or cn2. it might mean it's best to consider cn1 as the authoritative document when producing the new ETL.

     

    We'll have to discuss this at the meeting later.