Instant metadata generator
This is an experimental form to generate a metadata, mainly with Dublin Core properties.
Metadata input form
Put the resource URL in the top field, then describe other properties (you can ). extract data from head element in HTMLLeave blank if not applicable. Or you can add more fields with the pull down menu at the bottom of the form.
- Input URI for fields with default 'http://'. Other fields can have either URI or literal.
- You can add multiple fields with the same property. For dc:subject, just use "+" button to expand.
- URI for rdf:type filed will generate typed node element if it belongs to the predefined namespaces.
- Also, you can use QName format for predefined namespaces.
- If you need some hints, .
RDF metadata
This is an resulting RDF with XML syntax.
Meta elements in XHTML
This is a set of meta elements which embed DC metadata as specified in RFC2731. You can generate an RDF/XML automatically from this XHTML via GRDDL.
Save the above result, and try GRDDL demo.
Extract metadata form (X)HTML
If your (X)HTML <head> element contains link and/or meta elements, paste the head element into the bellow text area, and try bellow 'Extract' button. Additionally, you can put <address> element so that common patterns of modification date and/or author's mail address might be ectracted. The resulting data will appear on the above input form.
- This system tries to extract well-known metadata, e.g. author, keywords, description, content-type, from title, link, meta elements in the HTML head. Also, it attempts to get 'Lats-modified date' and/or author's mail from the address element. Some metadata may not be extracted, and the results may depend on the script engine of your browser.
- If modified date and mail address present both in head element and address element, the value(s) from head element takes precedence.
- You may put entire HTML code into the field, though too large data might cause unexpected error.
- If a meta element contains multiple keywords separated by comma or semicolon, the value will be divided into multiple dc:subjects. Since this system generates a new element with DOM for each additional dc:subject, too much keywords might make the browser unstable (40 keywords at W3C hopepage were successfully extracted).
Predefined namespace URIs
The following prefixes are used for well known vocabularies.
| Vocab | Prefix | Namespace URI |
|---|---|---|
| RDF | rdf | http://www.w3.org/1999/02/22-rdf-syntax-ns# |
| RDF Schema | rdfs | http://www.w3.org/2000/01/rdf-schema# |
| DCMES | dc | http://purl.org/dc/elements/1.1/ |
| DC Refinements | dcq | http://purl.org/dc/terms/ |
| DC Type Elements | dct | http://purl.org/dc/dcmitype/ |
| FOAF | foaf | http://xmlns.com/foaf/0.1/ |
| WordNet | wn | http://xmlns.com/wordnet/1.6/ |
| Geo vocab | geo | http://www.w3.org/2003/01/geo/wgs84_pos# |
| RSS 1.0 | rss | http://purl.org/rss/1.0/ |
| Creative Commons | cc | http://web.resource.org/cc/ |
| CC License | ccl | http://creativecommons.org/licenses/ |
Acknowledgement and Related Resource
This form and system was inspired by the question from Izumi Suzuki.
DC-dot at UKOLN can generate DCMES metadata of a web page by just inputting its URL.