[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency] A Registry (was [emergency] RE:[emergency-comment] Proposal: add <responseType> element in <info>)
Actually, it's a bit more complex and more work than that because it simply wouldn't fly to choose just one registry information format when we have two, with individual repositories which are special cases of each, and possibilities for more combinations since, at least in WSRP we are creating technical notes for both UDDI and ebXML, so I think that the task ahead of us will be one of taking these two formats and specifying EM-specific notes for implementing the work we do, including CAP, which I think we also need to consider as only one of our on-going work areas. So, while CAP is a standalone specification, I think that over time we will be including it within a family of specifications that addresses some if not all of the needs, on a global scale, that are described in the NIMS-90 document. It may be that we suggest that OASIS take on the work of building an maintaining a EM-specific repository, implementing both UDDI and ebXML, or that we pursue a joint-registries committee, including the current specifications registry, and see if we can find or create an appropriate non-governmental entity capable, without any vendor-specific bias, of maintaining the kind of repository that is needed, not only by the EM community, but by other specification/standards communities. That consideration is what has been underlying my own research and liaison activity in this area, and there are a few others in TCs such as ebXML regrep, BCM, CAM, WSRP. WSPEL, UBL, etc. This kind of efort also includes cross-consortia liaison work with W3C (VXML for Web Services in particular), HR-XML Consortium, ISO and the Web3D Consortium, just to name those with which I am familiar. XNS brought its work under OASIS, in the XRI and XDI TCs as has some of the work of XTM (which has its own independent consrtium as well, xtm.org) in the topic maps arena, with the TopicMaps for Published Subjects and Published Subjects in Geography and Languages TCs (somewhat overlapps the XLIFF TC), and the TopicMaps Vocabulary for Standards and Technologies. It can get bewildering at times since we recently experienced a burgeoning of TCs as well as outside consortia, which I personally now expect to experience a shakeout. Ciao, Rex At 7:55 PM -0800 3/28/04, Art Botterell wrote: >To do what Bob suggests it seems like we'll need either to select or >to create an actual, particular, usable instance of a registry and >an equally specific framework for maintaining our entries. In the >absence of which we've been muddling. > >Perhaps Bob can help us make the leap from theory to practice in this area. > >- Art > > >At 7:39 PM -0800 3/28/04, Rex Brooks wrote: >>OASIS has started a registry for standards, and we have looked at >>ebXML Registry and UDDI for use in the web services arena, and we >>have put liaison work for making certain that any work we do in >>this area is well grounded near the top of our priorities list, and >>we welcome more participation. I'm personally a fan of XTM, and >>have recommended it in several contexts. >> >>Ciao, >>Rex >> >>At 4:37 PM -0800 3/28/04, Art Botterell wrote: >>>At 6:17 PM -0500 3/28/04, Bob Wyman wrote: >>>> Please consider establishing registries for the CAP enumerated >>>>types, using Topic Maps (i.e. XTM) as the method for describing the >>>>enumerations, and using URN's as the values of the enumerators. >>> >>>Again, the problem isn't that it hasn't been considered, but that >>>so far nobody's come forward to actually do the work involved. >>> >>>And as has been discussed on a number of occasions, this becomes >>>even more salient when we start developing other recommendations >>>beyond CAP. >>> >>>- Art >>> >>> >>>To unsubscribe from this mailing list (and be removed from the >>>roster of the OASIS TC), go to >>>http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php. >> >> >>-- >>Rex Brooks >>GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth >>W3Address: http://www.starbourne.com >>Email: rexb@starbourne.com >>Tel: 510-849-2309 >>Fax: By Request >> >>To unsubscribe from this mailing list (and be removed from the >>roster of the OASIS TC), go to >>http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php. > > >To unsubscribe from this mailing list (and be removed from the >roster of the OASIS TC), go to >http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php. -- Rex Brooks GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth W3Address: http://www.starbourne.com Email: rexb@starbourne.com Tel: 510-849-2309 Fax: By Request
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]