Groups - DRAFT-EDXL-RIM-SC-MtgNotes-12-01-2011.doc uploaded

Submitter's message

        Please review these minutes of the December 1st, 2011 meeting of the RIM Subcommittee for approval at our next meeting, subject to any specified changes. Thanks.
        

-- Jeff Waters
        
    

    
        Document Name: DRAFT-EDXL-RIM-SC-MtgNotes-12-01-2011.doc

        
        Description

        At the December 1, 2011 meeting of the Reference Information Model

Subcommittee, the members discussed the following topics:

1. TOPIC:  Does the RIM approve of the proposed URN structure for naming

profiles, including the CAP 1.2 profiles? (Answer: Yes, the structure is as

follows:

urn:oasis:names:tc:emergency:[specification-name]:[specification-version]:profile:[profile-shortname]:[profile-version]

where the items in brackets are replaced with the appropriate values. An

example is urn:oasis:names:tc:emergency:cap:1.2:profile:CAP-AU:1.0

This format follows a naming recommendation paper developed by Werner and

we will reference this format and the paper on a wiki page. For future

profiles, such as CAP 2.0, the addition of ?edxl?, for example ?edxl-cap?,

will be considered. Capitalized letters for the profile name can be used

for emphasis, although the URN standard is insensitive to capitalization.)

2. TOPIC:  Should the optional  extension capability in CAP have a

structured parameter naming convention in future? (Answer: Probably. This

can be considered for CAP 2.0. Similar to the ValueListURN, the  name could

follow a policy for enabling globally unique names as a safer way to handle

extensions of specifications that are interoperable. The profiles

subcommittee can help address this for profiles.)

3. TOPIC:  Could an ontology for EDXL terms be enabled in an easy-to-use

manner to allow emergency managers and their developers to more efficiently

and effectively use the EDXL terms in their web-based content? (Answer:

Yes. The  ?Good Relations? vocabulary was cited as an example for how to do

this with cookbook-type templates for copy/pasting into web pages and then

simply changing the substantive content. The technique utilizes an

underlying ontology and RDFa. The use of a standardized vocabulary in this

way is both easy-to-use for developers and allows companies, such as in

this case Google, to extract the vocabulary to provide more meaningful

application content, such as tailored search results.)

4. TOPIC:  What is the next step for advancing the Reference Information

Model? (Answer: Rex has a version in Enterprise Architect containing the

CAP 1.2 and basic outline structure for adding the additional

specifications. We can proceed to add the remaining specifications,

following the provided format.)        

        Download Latest Revision

        Public Download Link
        
        Submitter: Jeff Waters

                Group: EM Reference Information Model SC

        Folder: Meeting Notes

        Date submitted: 2011-12-06 06:24:25