Document:
DRAFT-EDXL-RIM-SC-MtgNotes-11-17-2011.doc

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Jeff Waters on 2011-12-01 4:55 pm UTC

Publication Type

None at this time.

Group / Folder

EM Reference Information Model SC / Meeting Notes

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

86

Download Agreement

None at this time.

Description

At the November 17th, 2011 meeting of the Reference Information Model Subcommittee, the members discussed the following topics:

1.TOPIC : What is the status of the GML Simple Features profile? (Answer: It has been submitted for OASIS staff processing but JIRA currently does not show that it has been assigned to anyone. There appears to be a backlog due to various reasons. Rex will bring this up at the next TC meeting and then Lew will discuss with Chet the status.)


2.TOPIC: Should OASIS staff allow html links in public review documents to specifications under development where the links are correct but at the moment broken? (Answer: The links need to be provided at some point, so either they are included and broken or not included. Neither choice is ideal. The discussion broadened into the question of what should be included (specification, schema, examples, needed supporting schema) in the submitted specification zip file to address multiple needs, those of OASIS staff, reviewers, developers, etc. A suggestion was made to define and recommend a zip structure that would address all the needs. The ability to represent that same directory/subdirectory structure in Kavi would be helpful, but in the past this hasn’t been allowed. We should follow up with OASIS staff to see if we can get permission to manage our directory structure, if this is possible in Kavi, and obtain guidance on the structure itself.)

3.TOPIC: What are our most useful next steps to advance the development of our EDXL Reference Model? (Answer: The development of a UML representation was suggested, based on an underlying XML representation. Although the ontology representation might be better in some ways, the XML/UML approach may enable a quicker product that is more familiar to a majority of users. Both Lew and Rex are engaged in efforts to produce XML and UML models of components of EDXL. Their work could be the basis for these versions of the larger EDXL model. The use of simpler diagrams or pictures may be more intuitive and helpful to practitioners, as well. )