- From: Gregg Kellogg <gregg@kellogg-assoc.com>
- Date: Sat, 4 Sep 2010 15:36:55 -0400
- To: RDFa WG <public-rdfa-wg@w3.org>, "public-rdf-ruby@w3.org" <public-rdf-ruby@w3.org>
- Message-ID: <145F3528-A317-4A1A-8037-08D63F72C04E@kellogg-assoc.com>
Both Ruby Gems have been updated to support features from the latest RDFa Core 1.1 Editor's Draft (2010-08-03). This includes support for the following: * Use of a Processor Graph to gather information and errors during the course of parsing. Use the :processor_graph option to specify a Graph in which to collect information. There is no published specification for the properties to use, but until there is, each event is saved with a Blank Node subject of typerdfa.UndefinedPrefixError, rdfa:UndefinedTermError,rdfa:HostLanguageMarkupError, rdfa:ProfileReferenceError,rdfa:InformationalMessage, rdfa;MiscellaneousWarning orrdfa:MiscellaneousError. Additionally statements with literals fordc:description, dc:date, rdfa:sequence and rdfa:source (path to HTML Node) are generated. * RDFa Profiles allow URI mappings for terms and prefixes along with the specification of a default vocabulary. * RDFa 1.1 prefers the use of @prefix to create prefix mappings, but @xmlns continues to be supported. * XMLLiterals must be declared explicitly by setting @datatype="rdf:XMLLiteral". In 1.0, any statement with a property that contained anything other than text nodes as children caused an XMLLiteral to be emitted. Note that until RDFa Core 1.1 is published, all features are subject to change. I will not be attempting to maintain compatibility with draft features that are obsoleted during the standardization process. See related blog post: http://www.kellogg-assoc.com/2010/09/01/rdfcontext-and-rdf-rdfa-support-for-rdfa-1-1-2008-08-03-draft-semantics Gregg
Received on Saturday, 4 September 2010 19:38:07 UTC