any23-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <>
Subject [jira] [Resolved] (ANY23-249) Update all W3C and other Standards Compliance within Any23
Date Thu, 25 Jan 2018 18:01:00 GMT


Lewis John McGibbney resolved ANY23-249.
    Resolution: Fixed

This issue is too large to fix in it's entirety right now. We have done an excellent job recently
in addressing many issues. We should release 2.2 then we can come back and open any further
issues with standards compliance. 

> Update all W3C and other Standards Compliance within Any23
> ----------------------------------------------------------
>                 Key: ANY23-249
>                 URL:
>             Project: Apache Any23
>          Issue Type: Improvement
>          Components: api, core, extractors, microdata, nquads
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Major
>              Labels: gsoc2015, gsoc2016
>             Fix For: 2.2
> [~michele.mostarda] and [~lewismc] have been [discussing|]
what would work well for an Any23 Google Summer of Code Project for 2015.
> It turns out that in order to rebuild confidence with the Any23 standards compliance
(in light of new W3c standards which may be emerged or advanced) an in light of new non-W3C
emerging standards such as [microformats2|] it
would be a very worthwhile effort to have one or more student(s) engage on 
>  * initially evaluating all of the existing standards compliance within Any23
>  * uncovering which aspects of the compiled list require attention e.g. updating, overhauling,
re-implementation, extension or otherwise
>  * progress on executing the above under supervision of one or more of the assigned mentors

This message was sent by Atlassian JIRA

View raw message