Re: [metadata] Launching DPIG Metadata Task Force

Hi Rob,

chiming in, because some of these ideas came also from me...

On 24 Jan 2014, at 17:44 , Robert Sanderson <azaroth42@gmail.com> wrote:

> 
> Hi Bill, all,
> 
> Rather than clutter the wiki with personal opinions and questions, I'll post them here. If you think they're valuable, I'll copy them over.
> 
> * Bibliographic metadata -- There are many, many bibliographic schemas and "standards" out there. All have their issues.  RDA is 1600 properties. Bibframe is looking to be similar, if it ever materializes.  Simple Dublin Core is woefully insufficient. DC Terms isn't as bad as an 80%, but so is Bibo. And then there's non RDF schemas... MARC is ubiquitous in libraries, but arcane and not at all web friendly. MODS, MARC/XML, PRISM, ONIX, etc... 

Correct. The idea would be to simply make some sort of a proper overview, cataloging, so to say, of what is out there, who manages them, etc. There is no way we could do anything more...

I am not well informed of the current landscape to know whether (a) there exist such an overview already or not and (b) whether it would be useful to have one. The Metadata Handbook of Renée and Thad, that they gracefully gave us, does include some of these, but a more systematic approach might be useful. But maybe not... I am just listening!

> 
> Also, what's the line between Descriptive and Bibliographic?  
> 
> * Technical metadata -- technical metadata for what? For any resource on the web ... which therefore encompasses absolutely everything?
> 
> * Administrative metadata -- Does this mean rights metadata?
> 
> * Versioning -- A huge issue by itself.  To self-cite, http://tools.ietf.org/html/rfc7089 was 4 years of work to cover a very, very small portion of this.
> 
> * The IG's charter (IIRC) says that it won't create new recommendations -- to work with ONIX (for example) to create an RDF version would mean the creation of a separate Working Group?
>  
> 

Correct. And it is of course by no means certain that there would be enough strong voices for that work. Ie, the IG's only role would be to collect all the possible use cases, requirements, etc, that would justify the creation of such a group, leaving then the responsibility of moving ahead to... well, W3C, EDItEUR, and whoever wants to do this.

Cheers

Ivan


> So overall, my concern is that nothing useful will get done due to the existing baggage in the domain. Picking something focused is, in my opinion, going to be more productive than trying to even survey what exists across the entire "metadata" landscape.
> 
> Rob 
> 
> 
> 
> On Fri, Jan 24, 2014 at 7:58 AM, Bill Kasdorf <bkasdorf@apexcovantage.com> wrote:
> Hi, folks—
> 
>  
> 
> First, my apologies for having taken so long to get this activity in motion.
> 
>  
> 
> In order to structure and streamline the discussion for this Task Force, we’ve provided a basic framework on the wiki (http://www.w3.org/dpub/IG/wiki/Task_Forces/Metadata).
> 
> 
> Those who volunteered to be members of this Task Force are invited to contribute as they see fit. While discussion on the list is also appropriate and encouraged, we would like to consider the wiki the formal “record” of our discussion going forward. Please put your name in [brackets] at the beginning of anything you add to the wiki.
> 
>  
> 
> Others in the DPIG who might want to join this task force are of course still welcome to do so. Please add your name, affiliation, and e-mail as indicated on the wiki and also e-mail us privately to alert us that you’ve joined.
> 
>  
> 
> --Bill Kasdorf (bkasdorf@apexcovantage.com)
> 
> and Madi Solomon (madi.solomon@pearson.com).
> 
>  
> 
> Bill Kasdorf
> 
> Vice President, Apex Content Solutions
> 
> Apex CoVantage
> 
> W: +1 734-904-6252
> 
> M: +1 734-904-6252
> 
> @BillKasdorf
> 
> bkasdorf@apexcovantage.com
> 
> www.apexcovantage.com
> 
>  
> 
> <image003.jpg>
> 
>  
> 
> 


----
Ivan Herman, W3C 
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
GPG: 0x343F1A3D
FOAF: http://www.ivan-herman.net/foaf