|
From: <las...@Su...> - 2001-04-23 09:59:55
|
Bob Stayton wrote: > > > From: Dan Mueth <da...@ea...> > > > > So, we would have: > > > > urn:x-omf1:organization:group:name:version:language:format > > > > where organization will normally be a domain and group is whatever the > > coordinators for that domain choose (package, project, etc.) > > I seem to have missed the introduction of :group: in > the URN. Is that necessary to establishing a document > "name" part? Or is it part of the metadata (in which case > shouldn't it be in the OMF metadata elements)? Oh, this was me. I just thought that for a large organization we might want to have another level between organization and document. Obvious values for this are project or package name. [snip] > I would propose instead using the OMF <relation> element, > with its url attribute pointing to a series ID. By that I > mean define a seriesID using uuidgen as Dan suggests. Then > the OMF metadata for each document includes > > <relation url="thisseriesUUID" status="omf-series-id"/> > > This defines a relationship between this document and the > series of which it is a part. Then you could query an OMF > metadata collection to select all documents that share the > same relation element. From that you could select specific > alternate version/language/format documents. > > Would this be a correct usage of the <relation> element? > Would it meet the needs of a seriesID? I looked at the definition of the <relation> element and it didnt seem very obvious if it is ok, but I think we could use it like the above. Laszlo |