According to Misha Wolf:
> Jacqueline wrote:
>
> > What would be an appropriate way to group repeated elements (using the
> > HTML
> > Meta element) when they contain 'multiline metadata'? For example, if more
> > than one type of Relation is to be specified:
>
> [...]
>
> This question applies also to other elements, eg Creator.
>
> Possible answers include:
>
> 1. Assume the ordering is significant and don't use tools that mess up
> the ordering.
In my humble opinion this is the best solution. For users it is easy
to create/read and it is (more or less) easy to parse by a tool.
This solution is used at a project at the University of Siegen
(Germany) where I'm currently writing a gatherer/parser...
[...]
> None of the above are ideal and that's where RDF will come in. The W3C
An other solution is to use dedicated start-/end-tags, e.g.
<META NAME="groupstart" CONTENT="1">
<META NAME="DC.creator" CONTENT="John Doe">
<META NAME="DC.creator.email" CONTENT="[log in to unmask]">
<META NAME="groupend" CONTENT="1">
<META NAME="groupstart" CONTENT="2">
<META NAME="DC.creator" CONTENT="Joe User">
<META NAME="DC.creator.email" CONTENT="[log in to unmask]">
<META NAME="groupend" CONTENT="2">
Some time ago Nancy Morgan directed me to the GEM-site
(http://gem.syr.edu/Workbench/Metadata/metadata_index.html)
where they are using this solution.
But from an implementors point of view it has no real advantage,
because I still have to take care of the ordering of meta tags.
I find it easier to use the DC element itself as an implicit
start-tag.
ciao...
--
Lars Eilebrecht - Any sufficiently advanced bug...
[log in to unmask] - is indistinguishable from a feature.
|