EM Reference Information Model SC

All,

Given the feedback from the TC Admin, I am considering submitting a revised template request. Before proceeding, I would like your input on the points below.

1) Work Product Title: "Emergency Data Exchange Language (EDXL) Reference Information Model (RIM): Common Types, v1.0"
Reason for change: expanded abbreviations and hyphen elimination from previous "EDXL RIM - Common Types".

2) Work Product Abbreviation (WPA): considering alternatives
a) "EDXL-RIM-CT-v1.0"
b) "EDXL-CT-v1.0"
or using "_" for version separation
c) "EDXL-RIM-CT_v1.0"
d) "EDXL-CT_v1.0"
or lower case counterparts
e) "edxl-rim-ct-v1.0"
f) "edxl-ct-v1.0"
g) "edxl-rim-ct_v1.0"
h) "edxl-ct_v1.0"
i) other?
Note that WPA determines the file name of the work products. So far, we have not been consistent in the EM-TC, using upper case, lower case or even mixed forms (e.g. emergency_edxl_have-1.0, EDXL-RM-SPEC-V1.0, EDXL-DE_Spec_v1.0, cap-v1.1-ipaws-profile-v1.0). OASIS does not impose any particular format, but indicates that there is a tendency towards lower case notations for file names, and I personally believe that it would be nice to have a consistent notation within the TC.

3) Namespaces

- Document URI:
http://docs.oasis-open.org/ns/emergency/edxl/rim/ct or other variants derived from WPA.

- xml namespace:
urn:oasis:names:tc:emergency:edxl:rim:ct or other variants derived from WPA.

Thanks for your feedback,
Werner

On Wed, 16 Feb 2011, Werner.Joerg@iem.com wrote: > All, > > Given the feedback from the TC Admin, I am considering submitting a > revised template request. Before proceeding, I would like your input on the > points below. > > 1) Work Product Title: "Emergency Data Exchange Language (EDXL) Reference Information Model (RIM): Common Types, v1.0" > Reason for change: expanded abbreviations and hyphen elimination from previous "EDXL RIM - Common Types". > > 2) Work Product Abbreviation (WPA): considering alternatives > a) "EDXL-RIM-CT-v1.0" > b) "EDXL-CT-v1.0" > or using "_" for version separation Werner/SC - thanks for taking care with the selection of names and URIs. It's possible to change your mind, but preferable to choose something and stay with the decision. Just one clarification on the "_" (UNDERSCORE) character. One of the (obscure?) rules for filenames and directory names comes into play here: the rule that licenses any of the characters A-Z, a-z, and 0-9 (with "." and "-" and a couple other constraints). Since the Work Product Abbreviation is incorporated into the document identifier and the principal filename for the WP, the UNDERSCORE is not allowed [1] > c) "EDXL-RIM-CT_v1.0" > d) "EDXL-CT_v1.0" > or lower case counterparts > e) "edxl-rim-ct-v1.0" > f) "edxl-ct-v1.0" > g) "edxl-rim-ct_v1.0" > h) "edxl-ct_v1.0" > i) other? > Note that WPA determines the file name of the work products. So far, we > have not been consistent in the EM-TC, using upper case, lower case or even > mixed forms (e.g. emergency_edxl_have-1.0, EDXL-RM-SPEC-V1.0, > EDXL-DE_Spec_v1.0, cap-v1.1-ipaws-profile-v1.0). OASIS does not impose > any particular format, but indicates that there is a tendency towards lower > case notations for file names, and I personally believe that it would be nice > to have a consistent notation within the TC. > > 3) Namespaces > > - Document URI: > http://docs.oasis-open.org/ns/emergency/edxl/rim/ct or other variants derived from WPA. > > - xml namespace: > urn:oasis:names:tc:emergency:edxl:rim:ct or other variants derived from WPA. > > Thanks for your feedback, > Werner [1] http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#nameCharacters

Thanks Robin, That changes my preference to f). Cheers, Rex On 2/16/11 10:34 AM, Robin Cover wrote: > On Wed, 16 Feb 2011, Werner.Joerg@iem.com wrote: > >> All, >> >> Given the feedback from the TC Admin, I am considering submitting a >> revised template request. Before proceeding, I would like your input >> on the points below. >> >> 1) Work Product Title: "Emergency Data Exchange Language (EDXL) >> Reference Information Model (RIM): Common Types, v1.0" >> Reason for change: expanded abbreviations and hyphen elimination from >> previous "EDXL RIM - Common Types". >> >> 2) Work Product Abbreviation (WPA): considering alternatives >> a) "EDXL-RIM-CT-v1.0" >> b) "EDXL-CT-v1.0" >> or using "_" for version separation > > Werner/SC - thanks for taking care with the selection of names > and URIs. It's possible to change your mind, but preferable to > choose something and stay with the decision. > > Just one clarification on the "_" (UNDERSCORE) character. > > One of the (obscure?) rules for filenames and directory names comes > into play here: the rule that licenses any of the > characters A-Z, a-z, and 0-9 (with "." and "-" and > a couple other constraints). Since the Work > Product Abbreviation is incorporated into the > document identifier and the principal filename for > the WP, the UNDERSCORE is not allowed [1] > >> c) "EDXL-RIM-CT_v1.0" >> d) "EDXL-CT_v1.0" >> or lower case counterparts >> e) "edxl-rim-ct-v1.0" >> f) "edxl-ct-v1.0" >> g) "edxl-rim-ct_v1.0" >> h) "edxl-ct_v1.0" >> i) other? >> Note that WPA determines the file name of the work products. So far, we >> have not been consistent in the EM-TC, using upper case, lower case >> or even mixed forms (e.g. emergency_edxl_have-1.0, EDXL-RM-SPEC-V1.0, >> EDXL-DE_Spec_v1.0, cap-v1.1-ipaws-profile-v1.0). OASIS does not impose >> any particular format, but indicates that there is a tendency towards >> lower case notations for file names, and I personally believe that it >> would be nice to have a consistent notation within the TC. >> >> 3) Namespaces >> >> - Document URI: >> http://docs.oasis-open.org/ns/emergency/edxl/rim/ct or other >> variants derived from WPA. >> >> - xml namespace: >> urn:oasis:names:tc:emergency:edxl:rim:ct or other variants derived >> from WPA. >> >> Thanks for your feedback, >> Werner > > [1] > http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#nameCharacters > > --------------------------------------------------------------------- > 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 > >

FWIW, Werner My preference is h) lower case. I would like to suggest that we do this consistently in edxl-sitrep, edxl-de and edxl-have. Of course we need to put it before the TC after our meeting next week. Cheers, Rex On 2/16/11 10:00 AM, Werner.Joerg@iem.com wrote: > All, > > Given the feedback from the TC Admin, I am considering submitting a revised template request. Before proceeding, I would like your input on the points below. > > 1) Work Product Title: "Emergency Data Exchange Language (EDXL) Reference Information Model (RIM): Common Types, v1.0" > Reason for change: expanded abbreviations and hyphen elimination from previous "EDXL RIM - Common Types". > > 2) Work Product Abbreviation (WPA): considering alternatives > a) "EDXL-RIM-CT-v1.0" > b) "EDXL-CT-v1.0" > or using "_" for version separation > c) "EDXL-RIM-CT_v1.0" > d) "EDXL-CT_v1.0" > or lower case counterparts > e) "edxl-rim-ct-v1.0" > f) "edxl-ct-v1.0" > g) "edxl-rim-ct_v1.0" > h) "edxl-ct_v1.0" > i) other? > Note that WPA determines the file name of the work products. So far, we have not been consistent in the EM-TC, using upper case, lower case or even mixed forms (e.g. emergency_edxl_have-1.0, EDXL-RM-SPEC-V1.0, EDXL-DE_Spec_v1.0, cap-v1.1-ipaws-profile-v1.0). OASIS does not impose any particular format, but indicates that there is a tendency towards lower case notations for file names, and I personally believe that it would be nice to have a consistent notation within the TC. > > 3) Namespaces > > - Document URI: > http://docs.oasis-open.org/ns/emergency/edxl/rim/ct or other variants derived from WPA. > > - xml namespace: > urn:oasis:names:tc:emergency:edxl:rim:ct or other variants derived from WPA. > > Thanks for your feedback, > Werner