|
MetaData<< Add Link Bookmarklet | Cookbook-V1 | PmWiki Watch >> Note: The recipes here are for PmWiki versions 0.6 and 1.0 only. For PmWiki 2.0 recipes, see Cookbook.
GoalThe point is to provide Dublin Core (DC) metadata for wiki pages, according to the Dublin Core recommendation for encoding DC metadata in RDF/XML. http://dublincore.org/documents/dcmes-xml/(approve links) It should follow the suggestions for Dublin Core for wikis, as seen here: http://www.emacswiki.org/cgi-bin/community/DublinCoreForWiki There's also a variation for Creative Commons (http://creativecommons.org/) metadata, as defined here: http://creativecommons.org/technology/metadata/implement SolutionDiscussionThis script was developed using PmWiki 1.0.5, but it should work with any 0.6.x or 1.0.x version. InstallTo install, unpack the tarball or zip file, and recursively copy all the contents of the directory it creates to your pmwiki directory: tar zxvf pmwiki-metadata-0.6.tar.gz
cp -R pmwiki-metadata-0.6/* /path/to/pmwiki
Add the following line to your 'local/config.php' file: include_once('cookbook/metadata.php');
That should probably be enough. Configuration variablesThere are a number of configuration variables to change the output of this script.
Note that you really only want to have one of $CopyrightPage or $CopyrightText defined.
See AlsoGuidelines(approve links) for implementing Dublin Core in XML. Why? I think the guidelines are for including DC elements in another XML schema or DTD. The standards supported in this module are defined by Dublin Core and Creative Commons. So it's not really all that much about mixing in DC elements. --EvanProdromou
Some countries (Australia and New Zealand among them) have government metadata standards that are modified Dublin Core -- adding non-DC elements to DC metadata. They also use qualified DC as well as simple DC. The MetaData module as it currently stands doesn't support either qualified DC or non-DC elements. The above link covers both topics, as well as simple DC. The title of the page (MetaData) led this reader to suppose it takes a broader approach to metadata than the one given in the goal. To quote from the link above:
"Many metadata applications will mix Dublin Core metadata with properties taken from other metadata schemas. There are several reasons for wanting to do this including the need for DC-based metadata applications to incorporate semantics that are not available within the DCMES and the desire to incorporate DCMES elements within other metadata applications."
So to meet the local standard means generating some simple DC, some qualified DC and some AGLS/NZGLS elements. This recipe looked as if it might be a useful starting point, but it doesn't solve this reader's problem. --jr
History
Comments & BugsIs there a reason the DublinCore script doesn't include dc:relation and the isPartOf qualifier, with a reference to the I plan to implement the proposed recommendation for Expressing Qualified Dublin Core in RDF/XML(approve links) at some point soon. That will probably have all the isPartOf, hasVersion, and that kind of stuff. --EvanProdromou
I also want to re-architect the code so it uses RAP(approve links) to build the model and serialize it. That'd separate out the data itself from the presentation. Finally, I'd also like to allow editing of a page's metadata in the page itself, with (say) Notation3. For example, %n3% <> dc:summary "This is the page summary." ;
dc:subject "RDF", "Metadata", "Extensions" ;
rdfs:seeAlso <http://www.w3.org/2000/10/swap/Primer> . %%
ContributorsCopyrightCopyright 2004, Evan Prodromou. Available under the General Public License (GPL). pmwiki-2.2.0-beta68 -- Last modified by {{EvanProdromou}}
|