You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2017/10/05 07:57:00 UTC

[jira] [Commented] (JENA-1398) Upgrade to the spelling of archaic FOAF properties

    [ https://issues.apache.org/jira/browse/JENA-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192578#comment-16192578 ] 

Andy Seaborne commented on JENA-1398:
-------------------------------------

Hi [~shirren],

That sounds like a good idea. Would you like to send in a pull request of patch? See [this page|https://github.com/apache/jena/blob/master/CONTRIBUTING.md].

How might the migration process be done? Add the new properties and mark in Java that the old ones as {{@Deprecated}}?

While {{FOAF.java}} was originally created by running {{schemagen}}, it probably needs more control to manage migration of terms. Running {{schemagen}} on an up-to-date version of the FOAF vocabulary and comparing the difference, and marking archaic terms, maybe?

{{jena-arq/Vocabularies/FOAF.ttl}} contains the original input.

These vocabularies are in ARQ because they were used to produce the W3C Implementation EARL reports for SPARQL.


> Upgrade to the spelling of archaic FOAF properties
> --------------------------------------------------
>
>                 Key: JENA-1398
>                 URL: https://issues.apache.org/jira/browse/JENA-1398
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Jena
>    Affects Versions: Jena 3.4.0
>         Environment: NA
>            Reporter: Shirren Premaratne
>            Priority: Minor
>              Labels: easyfix
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> As per the FOAF spec [http://xmlns.com/foaf/spec] some of the properties have upgraded spellings. In particular http://xmlns.com/foaf/0.1/family_name and http://xmlns.com/foaf/0.1/givenname (considered archaic) have been upgraded to http://xmlns.com/foaf/0.1/familyName and http://xmlns.com/foaf/0.1/givenName. There may be other such issues. May I propose that these properties be upgraded to reflect the recommendations of the FOAF spec.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)