This snapshot, taken on 25/11/2010, shows web content selected for preservation by The National Archives. External links, forms and search boxes may not work in archived websites.
|
Q. Why do some e-GMS elements have tags that start eGMS.elementName and others that start with DC.elementName? The prefix of the meta name is eGMS for those elements or refinements that are unique to the e-GMS and specified within the standard. However, e-GMS uses both Dublin Core (DC) and e-GMS elements so the tags have different prefixes depending on whether the term is specified by Dublin Core or by e-GMS.
The syntax examples given in e-GMS v3.1 provide guidance on which prefix to use for |
|
Q. What syntax should I use for date ranges rather than a single date? Many implementations use: < meta name="DCTERMS.temporal" scheme="DCTERMS.W3CDTF" content="2007-01-01/2007-12-31" / > to describe date ranges. However the scope of W3CDTF does not cover date ranges, only the display of date and time. So, whilst the values for the dates are correct for the W3C encoding scheme, the range is not recognised. The W3C profile is based on ISO 8601, which does recognise the solidus (/) for specifying periods of time, therefore the following string would better fit the requirement: < meta name="DCTERMS.temporal" scheme="ISO8601" content="2007-01-01/2007-12-31" / > This scheme has not been declared by Dublin Core or the e-GMS as an encoding scheme (hence no DCTERMS or eGMS prefix for ISO8601) but you could declare it as part of your own local profile. Alternatively, Dublin Core advocates the use of the Dublin Core Period encoding scheme for date ranges – see http://dublincore.org/documents/dcmi-period and http://dublincore.org/documents/dcmi-dcsv Following their example for encoding a Period in XHTML, the string would look like this: < meta name="DCTERMS.temporal" scheme="DCTERMS.Period" content="start=2007-01-01; end=2007-12-31" / > |
|
Q. If an element or refinement requires multiple values should I repeat the tag for each value or put all the values in one tag? For preference, repeat the element for each value if the resource covers more than one i.e. for preference use: < meta name="DCTERMS.audience" scheme="eGMS.AES" content="Businesses" / > < meta name="DCTERMS.audience" scheme="eGMS.AES" content="Voluntary sector" / > Alternatively, use a semi-colon as a list separator i.e. if your application is unable to repeat the element, use: < meta name="DCTERMS.audience" scheme="eGMS.AES" content="Businesses; Voluntary sector" / > |