This HTML5 document contains 178 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n24https://demo.openlinksw.com/about/id/entity/http/purl.org/dc/elements/1.1/
n18https://demo.openlinksw.com/about/id/entity/http/purl.obolibrary.org/obo/
dctermshttp://purl.org/dc/terms/
n17http://demo.openlinksw.com/about/id/entity/http/xmlns.com/foaf/spec/
n5http://linkeddata.uriburner.com:28898/about/id/entity/http/xmlns.com/foaf/0.1/
n23http://demo.openlinksw.com/about/id/entity/http/purl.org/NET/c4dm/
foafhttp://xmlns.com/foaf/0.1/
n20http://demo.openlinksw.com/sparql/
wdrshttp://www.w3.org/2007/05/powder-s#
dchttp://purl.org/dc/elements/1.1/
schemahttp://schema.org/
rdfshttp://www.w3.org/2000/01/rdf-schema#
skoshttp://www.w3.org/2004/02/skos/core#
n22http://demo.openlinksw.com/about/id/entity/http/dati.beniculturali.it/cis/
voidhttp://rdfs.org/ns/void#
n21http://demo.openlinksw.com/about/id/entity/http/www.ontologydesignpatterns.org/ont/dul/
n4http://demo.openlinksw.com/about/id/entity/http/xmlns.com/foaf/0.1/
n11http://demo.openlinksw.com/about/id/entity/http/demo.openlinksw.com/about/id/http/xmlns.com/foaf/0.1/
n10https://demo.openlinksw.com/about/id/entity/http/xmlns.com/foaf/0.1/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n7http://purl.org/dc/elements/1.1/date#
owlhttp://www.w3.org/2002/07/owl#
n15http://demo.openlinksw.com/about/id/entity/http/xmlns.com/foaf/
n13http://demo.openlinksw.com/about/id/entity/http/purl.org/dc/elements/1.1/
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
dc:date
rdf:type
rdf:Property owl:AnnotationProperty schema:CreativeWork owl:DatatypeProperty
rdfs:label
Date dc:date
rdfs:isDefinedBy
dc:
rdfs:comment
A point or period of time associated with an event in the lifecycle of the resource.
owl:sameAs
n7:this
foaf:topic
n7:this dc:description dc:subject dc:coverage dc:rights dc:publisher dc:format dc:identifier dc:type dc:relation dc:source dc:language dc: dc:contributor dc:title dc:creator
wdrs:describedby
n4:membershipClass n5:givenname n4:skypeID n4:img-uri n5:family_name n5:mbox_sha1sum n4:icqChatID n4:age n4:pastProject n4:theme n10: n11: n4:Group n4:workplaceHomepage-uri n5:member n4:OnlineGamingAccount n13:issued n4:givenName n4:fundedBy n4:OnlineChatAccount n5:depicts n13:thumbnail n4:pastProject-uri n4:currentProject-uri n4:knows-uri n4:workplaceHomePage n4:primaryTopic n4:depiction-uri n4:page n4:workplaceHomePage-uri n5:skypeID n5:account n4:account n4:topic_interest n5:birthday n4:logo n15:spec n4:homepage n4:name n4:Agent n4:birthday n5:publications n4:tipjar n4:Concept n13:rights n4:knows-name n13:coverage n17:index.rdf n13:contributor n4:mbox_sha1sum n4:workplaceHomepage n13:subject n4:maker n17: n4:interest n13:relation n13:language n18:doid.owl n4:Person n5:thumbnail n4:givenname n21:DUL.owl n4:myersBriggs n4:aimChatID n4:openid n4:account-uri n4:made-uri n22: n4:Image n23:event.owl n4:mbox n24: n4:tipjar-uri n4:jabberID n13:type n13:source n13:format n4:msnChatID n4:religion n13:identifier n4:interest-uri n4:schoolHomepage-uri n4:person n4:knows n4:geekcode n4:surname n4:family_name n4:dnaChecksum n4:PersonalProfileDocument n4:plan n4:gender n4:focus n4:homepage-uri n4:firstName n4:topic n4:made n4:depicts n4:familyName n15:0.1 n4:Organization n4:nick n4:workInfoHomepage n4:LabelProperty n4:accountProfilePage n4:dateOfBirth n4: n4:member n4:img n4:weblog-uri n4:schoolHomepage n4:OnlineEcommerceAccount n4:sha1 n5:tipjar n5:primaryTopic n4:publications n5:pastProject n5:msnChatID n5:surname n4:based_near n5:icqChatID n4:OnlineAccount n4:depiction n4:based_near-uri n4:mbox-uri n4:holdsAccount n4:weblog n4:status n4:pubkeyAddress n4:isPrimaryTopicOf n4:title n5:weblog n5:Organization n5:focus n5:geekcode n4:lastName n4:currentProject n4:yahooChatID n4:Project n4:Document n13:modified n4:thumbnail n4:accountServiceHomepage n4:wife n4:openid-uri n4:phone n4:accountName n5:based_near
dcterms:description
Date may be used to express temporal information at any level of granularity. Recommended practice is to express the date, date/time, or period of time according to ISO 8601-1 [[ISO 8601-1](https://www.iso.org/iso-8601-date-and-time-format.html)] or a published profile of the ISO standard, such as the W3C Note on Date and Time Formats [[W3CDTF](https://www.w3.org/TR/NOTE-datetime)] or the Extended Date/Time Format Specification [[EDTF](http://www.loc.gov/standards/datetime/)]. If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Date ranges may be specified using ISO 8601 period of time specification in which start and end dates are separated by a '/' (slash) character. Either the start or end date may be missing.
dcterms:issued
1999-07-02
skos:note
A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/date) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation.
schema:url
dc:date
schema:mainEntity
n13:date
void:sparqlEndpoint
n20: