Andy Kirkwood|Motive said:
An interesting application of the technology, although I'm not sure that
is addresses how to make it *easier* for administrators to
maintain metadata records.
and
(Assuming the ideal solution would be a wysiwyg editing environment for
non-technical content authors.)
Title: Re: [WSG] Naked metadata - RDF in
HTML
Hi Terrence,
It feels like we're talking at cross-purposes?
I'm approaching the subject with the idea
that metadata is
important in order for people to find
(related) information at some later
time.
Interesting and valid point, unfortunately
Thanks Jonathon. This is great, I have forwarded a link to your page to
our metadata people.
--
kind regards
Terrence Wood.
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for
Some more thoughts (that send button is just too easy to press =)
Would using a rel or rev attribute be more appropriate than using a class
to delineate the metadata? These attributes imply a relationship whereas
class does not.
If you needed to get at elements containing metadata at the
Hi Jonathan,
An interesting application of the technology, although I'm not sure
that is addresses how to make it *easier* for administrators to
maintain metadata records.
ISSUES
(Assuming the ideal solution would be a wysiwyg editing environment
for non-technical content authors.)
Hi Ian, Liddy, Charles, Peter, Misha, Alan, Patrick, Andy, Geoff,
DC-General and WSG
Thank you for all your help and comments. In particular, thank you,
Ian, for RDF in HTML.
Last week, I wrote to the DC-General and the Web Standards Group
mailing lists. I was lamenting the fact that
Hi WSG'ers
After seeing Sarah's post about CSS for titles, I thought that people
might be interested in this idea. It's a half baked idea. If you have
any comments or suggestions, I would love to hear them.
Apologies for those who have already seen this on the DC-General list.
** The
Jonathan O'Donnell wrote:
meta name=DC.title content=#title /
meta name=DC.creator content=#creator /
meta name=DC.creator content=#rights /
I'm not a DC expert, but I believe that that's not a valid way to go
about it. When you embed DC information via meta elements, content
Hi Jonathan,
I second Patrick's comment that 'pointing' the DC records to content on the
page is not the solution.
Although, from a maintenance perspective, this may appear to be a work-around
for not completing the metadata records (questionable), metadata harvesting
tools are unlikely to
Jonathan O'Donnell wrote:
Hi WSG'ers
In general, data (including metadata) should be stored in one place
only. This prevents drift: if it is only stored in one place, it can
only be updated in that place.
Often, the information that we want to store as metadata already
appears in the Web
10 matches
Mail list logo
