OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [xri] RE: Request membership in (XRI TC)

	Caught! ;-)

	We've gotten several emails about the overlap with Topic Maps and
the Oasis Published Subjects TC. I'm enthusiastically trying to absorb as
much about Topic Maps as is humanly possibly within the constraints of
getting focused on spinning up our TC.
	I look forward to reading your paper and seeing you online..


> -----Original Message-----
> From: Mary Nishikawa [mailto:nisikawa@fuchinobe.oilfield.slb.com]
> Sent: Thursday, December 26, 2002 5:39 PM
> To: gwachob@visa.com
> Cc: xri@lists.oasis-open.org; bernard Vatant
> Subject: Request membership in (XRI TC)
> Hi Gabe,
> I have been seeing you on the #topicmaps@ 
> irc.openprojects.net  for some 
> days now and wondered who you were :)
> For this committee your objective to "...define a URI scheme and a 
> corresponding URN namespace for distributed directory 
> services that enable 
> the identification of resources (including people and 
> organizations) and 
> the sharing of data across domains, enterprises, and 
> applications"  has 
> some overlap with what we have been looking into the past 
> year in the TM 
> Published Subjects TC which you seem to be aware of.
> Of course there are differences in the approach, but it is 
> good to take a 
> look at these differences. You also mentioned working with 
> LDAP metadata 
> which is of interest to me too.
> If you take a look at the recent paper that I presented at 
> Extreme Markup 
> Languages 2002, you will have some idea of what I and the 
> committee has 
> been working on and where there is some overlap between these 
> committees, I 
> think.
> <http://www.idealliance.org/papers/extreme02/html/2002/Nishika
> wa01/EML2002Nishikawa01-toc.html 
>   >
> The standards work that I have planned for 2003 is to work on 
>  Published 
> Subjects for Geography and Languages (OASIS GeoLang 
> Committee) and Review 
> and comment on the SC34 WG3 standards for Topic Maps for Japan, and 
> finalize the drafts of the Topic Maps Published subjects 
> Requirements and 
> Recommendations.
> As you can see, I am very busy, but I will subscribe to the 
> lists to follow 
> what your group is doing and anyone here is welcome to stop 
> by the channel.
> Cheers,
> Mary
> ***********************************************************
> Mary Y. Nishikawa,  EDMS Technical Advisor
> Schlumberger K. K.
> 2-2-1 Fuchinobe
> Sagamihara, Kanagawa 229-0006
> Tel:  +81-42-759-5376
> Fax: +81-42-759-3563
> Eureka IT Community Web Technologies SIG Co-leader &
> XML BB Manager, xmlbb@slb.com
> ISO/IEC JTC1/SC34 WG3 Japan
> OASIS TM Pubsubj TC, GeoLang TC, XMLVoc TC
> ************************************************************
> A new OASIS technical committee is being formed. The OASIS Extensible
> Resource Identifier Technical Committee (XRI TC) has been proposed by
> the following members of OASIS: Geoffrey Strongin, AMD; 
> Krishna Sankar,
> Cisco; Joseph Moeller, EDS; Jim Schreckengast, Xavier Serret, and
> Phillipe LeBlanc, Gemplus; Winston Bumpus, Novell; Nat Sakimura, Hiro
> Ogawa, Tomonori Seki, and Tetsu Watanabe, NRI Pacific; Drummond Reed,
> Loren West, Dave McAlpin, and Marc LeMaitre, OneName; Dave Wentker,
> Rajeev Maria, Mike Lindelsee, and Gabe Wachob, Visa International;
> Michael Willett and Lark Allen, Wave Systems; and Bill 
> Washburn, XNSORG.
> The proposal for a new TC meets the requirements of the OASIS TC
> Process (see http://oasis-open.org/committees/process.shtml), and is
> appended to this message. The proposal, which includes a statement of
> purpose, list of deliverables, and proposed schedule, will constitute
> the TC's charter. The TC Process allows these items to be clarified
> (revised) by the TC members; such clarifications (revisions), as well
> as submissions of technology for consideration by the TC and the
> beginning of technical discussions, may occur no sooner than the TC's
> first meeting.
> To become a member of this new TC you must 1) be an employee of an
> OASIS member organization or an Individual member of OASIS; 2) notify
> the TC co-chairs, Drummond Reed (drummond.reed@onename.com) and Gabe
> Wachob (gwachob@visa.com) of your intent to participate at 
> least 15 days
> prior to the first meeting; and 3) attend the first meeting on 9
> January. You should also subscribe to the TC's mail list. Note that
> membership in OASIS TCs is by individual, and not by organization. You
> must be eligible for participation at the time you time you notify the
> chair.
> The private mail list xri@lists.oasis-open.org is for committee
> discussions. TC members as well as any other interested OASIS members
> should subscribe to the list by going to the mail list web page at
> http://lists.oasis-open.org/ob/adm.pl, or by sending a message to
> xri-request@lists.oasis-open.org with the word "subscribe" as the body
> of the message. (Note that subscribing to the mail list does not make
> you a member of the TC; to become a member you must contact 
> the TC chair
> and attend the first meeting as described in the preceeding 
> paragraph.)
> A public comment list will be available for the public to 
> make comments
> on the work of this TC; a message may be sent to the TC via 
> the address
> xri-comment@lists.oasis-open.org.
> The archives of both of these mail lists are visible to the public at
> http://lists.oasis-open.org/archives/
> Additional information on this topic may be found on the 
> Cover Pages at
> http://xml.coverpages.org/xns.html "Extensible Name Service (XNS)"
> -Karl
> =================================================================
> Karl F. Best
> Vice President, OASIS
> +1 978.667.5115 x206
> karl.best@oasis-open.org  http://www.oasis-open.org
> (i) Name of TC:
> Extensible Resource Identifier (XRI) Technical Committee
> (ii) Statement of Purpose:
> Increasingly, there is a demand for distributed directory 
> services that
> enable the identification of resources (including people and
> organizations) and the sharing of data across domains, 
> enterprises, and
> applications.  There are currently no transport- and 
> application-neutral
> identification schemes to support this infrastructure.
> The purpose of this committee is to define a URI scheme and a
> corresponding URN namespace that meet these requirements. This TC will
> also define basic mechanisms for resolving the identifiers in these
> schemes and for exchanging data associated with these 
> identifiers. This
> work will enable the creation of Web-like collections of resources
> (including, but not limited to, data, systems, services, 
> organizations,
> and people) that extend the WWW's current generalized addressing and
> linking capabilities.
> The URI scheme will conform to RFC 2396. It will also accommodate
> human-readable names as a subset of the compliant identifiers.  The TC
> will also produce an interoperable URN namespace 
> specification compliant
> with RFC 2141 and guided by the requirements in RFC 1737 for resources
> that need the ability to be persistently identified and linked.
> The TC will also define an XML schema to associate metadata with
> resources and a service to manipulate this metadata and data 
> associated
> with the resources. Specifically, this service will reflect the simple
> transactional nature of the WWW, i.e., it will use a small set of REST
> (Representational State Transfer) or CRUD-like operators on an
> infinitely extensible set of XRI-addressable resources.  This data
> exchange service will provide a platform for integration with
> directory-related specifications such as LDAP, DSML, and SPML.
> This TC's work will be influenced by the general architecture 
> described
> in XNS and specifically by the XNS Addressing Specification.  The XNS
> specifications published by the XNS Public Trust Organization (XNSORG)
> will be contributed to the TC for consideration in the 
> committeefs work.
> XNS is licensed under RF terms as described in
> http://www.xns.org/pages/XNS_License.pdf.
> (iii) List of Deliverables:
> Delivery schedule to be discussed at the first meeting.
> The TC deliverables will include:
> 1) Use cases & requirements
> 2) A syntax specification for the URI scheme & URN namespace
> 3) A resolution specification for the URI scheme & URN namespace
> 4) An XML schema for associating metadata with identified resources
> 5) A REST/CRUD-like data exchange service and bindings for 
> Relationship to Existing Activities:
> This TC:
> - is defining a URI scheme under RFC 2396 and a URN namespace 
> under RFC
> 2141 and guided by the requirements in RFC 1737.
> - will examine use of the IETF DDDS framework for resolution (RFC
> 3401-3405).
> - will integrate the W3C XML and XML Schemas architectures for data
> representation and description.
> - will integrate the W3C Web services framework for messaging, service
> description, and location.
> - will integrate the OASIS Web services security framework for secure
> messaging.
> - will examine possibilities for expression and integration of the
> directory services features with DSML, SPML, UDDI, and ebXML 
> as well as
> more established directory services specifications such as LDAP.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC