[
https://issues.apache.org/jira/browse/JENA-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194106#comment-16194106
]
Shirren Premaratne commented on JENA-1398:
------------------------------------------
Hi [~andy.seaborne],
I'm happy to submit a pull request. If I understand you correctly with regards
to the migration of terms, this would mean we need to make the edits to
FOAF.java directly manually marking the deprecated properties as exactly that,
adding the new ones as we go along? From what I understand running schemagen
will not supported marking deprecated properties? But then doing so means we
can no longer run schemagen, correct?
> 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)
