Re: The final 6

On Nov 25, 2012, at 8:56 AM, Nicholas Humfrey <nicholas.humfrey@bbc.co.uk> wrote:

> Hello,
> 
> The approach I have been taking to write the RDFa parser in EasyRdf, is to
> work through each of the test cases and implement the parts that cause the
> most tests to pass (according to the specification). Generally I worked
> through the easiest to fix tests first.
> 
> I thought you might be interested to know what the final 6 tests that I need
> to fix are.
> 
> 
> 0084: I think I need to implement 'skip element' in order to get this test
> to pass. I am amazed that no other tests require this functionality.
> 
> 0176: this is passing within my own test harness but not on rdfa.info. Need
> to work out why.
> 
> 0183: not sure how I am going to get this test to pass. PHP makes it tricky
> to get hold of the @xmlns attribute, so I have been getting PHP's XML parser
> top resolve namespaces, when I need to look them up. Mixing this with my own
> @prefix table makes it difficult to pass this test.
> 
> 0224: I think this is the only test for @inlist and incomplete triples.
> Implementing inlist has been one of the largest amounts of work. Mainly
> because to works very differently to the rest of the parser. PHP passes
> arrays by value, by default - which was working great for passing contexts
> down the tree. But I had to rework this when it came to implementing inlist
> because of having to pass values back up to the calling function.
> 
> 0303: Gregg tells me that this and 0312 is an HTML5 specific test and isn't
> in a specification yet. I will probably just copy the code from his ruby
> gem.
> 
> 0312: Interesting this is actually passing for me on rdfa.info/test-suite -
> I think the SPARQL query might need to be checked. The turtle output is
> different to the reference implementation.

Nick,

Congratulations on the level of conformance you've reached! Your processor is more than adequate for all but the most pedantic of use cases.

As for 0312, give me your result, and I'll check it. You can also access the same SPARQL implementation at http://rdf.greggkellogg.net/sparql/.

Also, we should add your implementation to the list of implementations in the "Developers" tab, and in the processor drop-down of the test suite (processors.json in the top-level of the GitHub project for rdfa.info [1]). We can also update the EARL report with your results. DOAP and FOAF information for the report should either be dereferencable, or can be added to a file in public/earl-reports based on your processor name; check some of the others that are there.

Gregg

[1] https://github.com/rdfa/rdfa-website

> Note that I don't have a local SPARQL engine in EasyRdf - so internally I
> have been testing against the Turtle output of the Reference Implementation
> (RDFa.rb).
> 
> 
> nick.
> 
> 
> ps. persona.org keeps on going down - making it hard to run the test suite.
> 
> 
> http://www.bbc.co.uk/
> This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
> 					
>

Received on Sunday, 25 November 2012 17:30:42 UTC