Document: draft-kameyama-tv-anytime-urn-02.txt
From: Scott W Brim 
Date: 17 januari 2005 

I have some questions that have not been satisfied in the few minutes
I've spent digging.  I'd like to use this as an excuse to get educated
about the pros and cons of doing things in different ways way up there
in application space where I'm not used to venturing.

This is for a new URN, "urn:tva:{category}:{string}", for "naming
persistent resources published by the TV-Anytime Forum including the
TV-Anytime Forum Standards, XML (Extensible Markup Language) Document
Type Definitions, XML Schemas, Namespaces, and other documents."

However, in their schema spec (sp003 part A) they say they have
adapted "the XML-based MPEG-7 Description Definition Language (DDL)
[ISO/IEC 15938-2] as ... representation format for metadata."

So if they're using a known standard for metadata representation, and
we know all about how to manage objects of all kinds using XML and
that standard, why do they need a new URN?  While we're at it, why did
they need the CRID draft (draft-earnshaw-tv-anytime-crid-04.txt)?
"crid://" is for referencing tv-anytime media, but these objects all
come wrapped in XML.  Why build the (higher layer) object type, being
carried in XML, into lower layer syntax?

Other than the fact that I don't understand the usefulness of either,
I have no objection.