search for: dublincor

...t that was not cluttered by and requiring multiple name spaces out of the box. They also felt DC was to loosly defined. (Note that RDF and DC combined in the case of a web feed format would end up being little more than W3C's RSS 1.0 specification. Cluttered and unendorsed.) [1] See http://dublincore.org/documents/dc-xml-guidelines/ and http://dublincore.org/documents/dcmes-xml/ to get the general idea of what this would look like. -- Daniel Aleksandersen

Just noticed this, <http://dublincore.org/usage/documents/relators/>. MARC (Library of Congress) relators are now part of Dublin Core, this allows refinements to meta-data like actor, composer, instrumentalist (of interest to kitchen sink metadata in Ogg/Vorbis). It still falls short of the more qualified relationships that might...

On 19/09/2007, Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: > On Wednesday 19. September 2007 19:02:06 Ian Malone wrote: > > Daniel Aleksandersen wrote: > > > Attached is a much improved version of yesterday's draft. Introducing > > > the audio:collection:artwork element to deal with album cover graphics > > > and such. > >

What I've gotten out of this discussion so far: 1) we need to introduce a means in which to do captions; this could be done through adding a "caption" element to CMML, or in another time-continuous annotation format; so far I am not sure which would be the better way 2) we need a XML annotation format for audio - in particular for music - that is more structured than vorbiscomment

...tos in a relational system is masochistic to say the least (the number of one-to-many as well as many-many relations would make it a real headache to manage). XML to the rescue. We could really simplify things by creating an XML record for each photo (we will be using modified Dublin Core www.dublincore.org for fields and descriptions). We have tried and failed to get a relational system to work well - too many "what if''s" and exceptions to the rules to deal with using a relation system. Since this is the Rails mailing list you can assume that I would like to do this usin...

...no method of describing > what 'role' people and organisations had in the production. Which is > precisely why I added the poorly defined role attribute to the person and > organisation elements. DC has provision for qualifiers, there is a proposed 'agent-role' <http://dublincore.org/usage/meetings/2002/05/Agent-roles.html> which, last time I looked, used the MARC relator list: <http://www.loc.gov/marc/sourcecode/relator/relatorlist.html> Two things to notice: 1. That is a massively long list. 2. It doesn't appear to do what we want. But it is there. Howe...

...people and organisations had in the > > > production. Which is precisely why I added the poorly defined role > > > attribute to the person and organisation elements. > > > > DC has provision for qualifiers, there is a proposed 'agent-role' > > <http://dublincore.org/usage/meetings/2002/05/Agent-roles.html> > > which, last time I looked, used the MARC relator list: > > <http://www.loc.gov/marc/sourcecode/relator/relatorlist.html> > > > > > > > > But it is there. However, no such scheme can reasonably provide &g...

...> dc:identifier > dc:source > dc:subject > xmpBJ:JobRef Several different technologies are discussed, here. You have previously mentioned XML and XMP. However, all but one of the above elements are Dublin Core (DC). DC can be expressed in many languages, including XML; visit: http://dublincore.org/documents/dc-ds-xml/ I am now puzzled why you want to use XMP. There is no standard for expressing DC in Ogg, but it should be straightforward to define one. However, DC has very limited structure, so such a standard would very likely use separate VorbisComments. Regards, Martin -- Martin...

...> what 'role' people and organisations had in the production. Which is > > precisely why I added the poorly defined role attribute to the person and > > organisation elements. > > DC has provision for qualifiers, there is a proposed 'agent-role' > <http://dublincore.org/usage/meetings/2002/05/Agent-roles.html> > which, last time I looked, used the MARC relator list: > <http://www.loc.gov/marc/sourcecode/relator/relatorlist.html> > > > But it is there. However, no such scheme can reasonably provide > support for one-of-roles such a...

Another problem I would like to speack about : tags. Each format appears to create its own tag. TwinVQ and WMA tags are limited but Mp3 has a good tag system (although the "genre" category could be improved). Now ogg develops a new kind of tagging. I imagine converting all my tags with thousand of tracks... real nightmare... Is there an authority or a project to standardiza tags ?

Daniel Aleksandersen wrote: > By the way, I have bee discussing Dublin Core (?DC?) with the developers of > the Atom 1.0 specification. It seams the reason they created atom:rights > instead of using dc:rights were just about what I thought it was: They > though DC was too loosely defined. Their own atom:rights element were > designed to more clearly define what the element