Search results

=== Dublin Core === * [http://dublincore.org/documents/dcmi-terms/ Dublin Core]

* Dublin core * Dublin core

...ributes in <a> elements. Can we find some compatibility between the Dublin Core 'license' and rel='license'?''

=== Dublin Core === * [http://dublincore.org/documents/dcmi-terms/ Dublin Core]

...ributes in <a> elements. Can we find some compatibility between the Dublin Core 'license' and rel='license'?''

* [http://dublincore.org/documents/2003/03/04/dcmi-terms/ Dublin Core] * We're following the [[citation]] microformat for basic formatting and core terminology

...ributes in <a> elements. Can we find some compatibility between the Dublin Core 'license' and rel='license'?'' ...cense DC.rights.license" (i.e. both the rel-license microformat plus Dubin Core), and when no such URL exists, to use a <META> element with name="DC.rights

<li>Dublin Core</li> <p>using Dublin Core terminology

* [http://dublincore.org/documents/dcmes-xml/ Expressing Simple Dublin Core in RDF/XML]

<em>create an XMDP for Dublin Core (creator, etc)</em> <li>Dublin Core</li>

...ile is generated, it is more important than ever to attempt to construct a core set of elements to facilitate metadata interoperability. ...with the following vocabularies, and, most likely, several others: Dublin Core Metadata Element Set, SMIL (Synchronized Multimedia Integration Language),

* “date”: Dublin Core * “modified”: Dublin Core

Dublin Core are working on a collection description application profile which is nearin

...odated. Essentially, work-of-art should strongly encourage the use of its core components (for consistency), but allow additional elements for those cases ** One of the core principles behind microformats is the reuse of existing standards. [[hCard]

...es standard vocabularies and date type formats, including some from Dublin Core and ISO.

...y available in OpenURL (because OpenURL includes all 15 of the main Dublin Core terms). It would be a plural property. By adding this property to the spec,

The [http://dublincore.org/documents/dcmi-terms/#terms-conformsTo Dublin Core conformsTo] term appears to already solve a more general problem of indicat

= Dublin Core =

...owballed, not sure if the ChatChannel stuff is official or not. The Dublin Core and WordNet stuff is mentioned in the FOAF spec index, but seems to be miss

...rty. At the bottom of the list are the unique terms to each format. Dublin Core has basic terms and terms that extend the basic ones.

...e, pas sûr si le truc du ChatChannel est officiel ou non. Les trucs Dublin Core et WordNet sont mentionnés dans la spec index FOAF, mais semble manquer à

** [http://wiki.xiph.org/Metadata Ogg Vorbis XML/RDF+Dublin Core (Draft Proposal)]

...in'? The reason being interoperability with prior art, specifically Dublin Core with their 'DC.whatever". They (DC) even have an RFC which describes this p

...tent should be a date in DD Month YYYY format; this is taken as the Dublin Core date of the item.

** [http://wiki.xiph.org/Metadata Ogg Vorbis XML/RDF+Dublin Core (Draft Proposal)]

...Guidelines pour "Encoding Bibliographic Citation Information" dans Dublin Core Metadata]

| schema.DC || &hellip; || [http://dublincore.org/ Dublin Core] | schema.DCTERMS || &hellip; || [http://dublincore.org/ Dublin Core]

...tation-fr|citation]] + [http://dublincore.org/documents/dcmi-terms/ Dublin Core] === ...our l'inclusion dans [[citation-fr|citation]], ou faisant partie du Dublin Core. Le [http://www.getty.edu/research/conducting_research/standards/intrometa

...ons. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].

The core set of properties should account for the following basic structures: ...descriptive data to web pages, such as meta tags -- with or without Dublin Core -- or embedded RDF.

...ison étant l'interopérabilité avec l'art initial, spécifiquement le Dublin Core avec son 'DC.whatever". Ils (DC) on même une RFC qui décrit ce mécanisme

Requires Dublin Core namespace declaration: <code>'''&lt;link rel="schema.DCTERMS" href="<nowiki Requires Dublin Core namespace declaration: <code>'''&lt;link rel="schema.DCTERMS" href="<nowiki

...ines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]

...st grise. En bas de la liste les termes uniques pour chaque format. Dublin core a des termes basiques et des termes qui étendent les basiques. Si la propr <th>Dublin Core</th>

...w.ietf.org/rfc/rfc2731.txt rfc2731], Eprints.org uses the following Dublin Core terms in meta tags in the HTML HEAD of each paper's page:

Simply taking an existing format (like Dublin Core) and reusing its vocabulary as class names is insufficient to make a microf

...a&metadataPrefix=mtx&identifier=info:ofi/fmt:kev:mtx:dc KEV Format: Dublin Core]</span></cite>

.../elements/1.1/creator, which is a fully qualified namespace for the Dublin Core property named 'creator'. In C++ std::string is an example of a fully quali

...tent should be a date in DD Month YYYY format; this is taken as the Dublin Core date of the item.

...rey. At the bottom of the list are the unique terms to each format. Dublin Core has basic terms and terms that extend the basic ones. If the property is an <th>Dublin Core</th>

=== MARC / MODS / Dublin Core === ...w.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) tr

== MARC / MODS / Dublin Core == ...ww.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml exemple]) et Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml exemple]) de