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] | [List Home]

Subject: RE: [xri] Metadata Discovery Coordination Group, an Introduction


I completely agree that a uniform, web-wide solution for metadata discovery
can have tremendous benefits for many different technologies. Our experience
at the OASIS XRI TC has been that there are already uses of the XRDS and XRD
discovery formats that we never anticipated, and I think we still have only
touched the tip of the iceburg.

Thanks for establishing the metadata-discovery list as a neutral open forum
where participants in all the metadata discovery efforts can carry on

One question: do you intend for this to replace the current XRDS-simple
Google Group (http://groups.google.com/group/xrds-simple), i.e., will it go
away once interested participants have migrated here?


> -----Original Message-----
> From: Eran Hammer-Lahav [mailto:eran@hueniverse.com]
> Sent: Friday, November 21, 2008 3:14 PM
> To: oauth@googlegroups.com; xrds-simple@googlegroups.com; OASIS XRI TC
> Cc: metadata-discovery@googlegroups.com
> Subject: [xri] Metadata Discovery Coordination Group, an Introduction
> Discussions about URI metadata discovery have been going on in many places
> for the past couple of years. This has been reaching its boiling point
> with
> the recent discussions between the W3C TAG, XRI TC, POWDER WG, the OpenID
> /
> Yadis, OAuth, Portable Contacts, XRDS-Simple, and OpenSocial communities,
> and various IETF I-Ds published on related topics.
> Web Discovery is likely to consist of two parts, the *retrieval* and
> *format* of a metadata document linked to a resource identified by a URI.
> There are multiple proposals for the metadata document format, with XRDS
> and
> POWDER as two notable examples. Discussions regarding metadata format
> should
> and will remain where they are currently being held.
> However, there is great recognizable value in a single (simple) mechanism
> for *retrieval* of metadata for resources identified with a URI. From the
> most basic use case of identifying which API is supported by a given
> endpoint, to a more complex trusted identity resolution, the requirements
> seems to be significantly overlapping.
> For many of these communities, time is running out and most are getting
> ready to put the final touches and ship specifications that already have
> running code. We have a rare (but narrow) opportunity to quickly go
> through
> the current proposals and at least set the tone for current and future
> discovery solutions.
> I am not ignoring the political complications of trying to reach consensus
> among so many entities and communities but I truly believe from the many
> hours of conversations I had the past 2 months that we are mostly all on
> the
> same page. All I think we now need is a room, and hence this new list:
> metadata-discovery@googlegroups.com.
> This is not a working group, nor does this group have any deliverables or
> will produce specifications. It is designed as a coordination venue for
> the
> various efforts going on to discuss their proposals and progress. It is
> also
> for soliciting feedback and confirming assumptions about discovery
> proposals.
> Given the complexities behind IPR policies and the significant
> differences,
> this list does not have an IPR policy. This means that discussions held
> here
> are not covered, and if produce anything other than normative references
> to
> existing standards (which is clearly the intention), will need to be
> resolved if adopted elsewhere.
> Web discovery has been my top priority for the past year and I am excited
> to
> finally reach the point where a critical mass is formed to finally address
> it. Please join the discussion at
> http://groups.google.com/group/metadata-discovery.
> ---------------------------------------------------------------------
> 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

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