Another similar candidate for renaming is com.hp.hpl.jena.query.ResultSet
and com.hp.hpl.jena.vocabulary.ResultSet

Just to avoid ambiguity and autocomplete issues I'd prefer the latter to
be called ResultSetVocab or ResultSetVocabulary

Rob



On 5/21/12 7:42 AM, "Andy Seaborne" <[email protected]> wrote:

>On 21/05/12 12:10, Damian Steer wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 21/05/12 12:06, Andy Seaborne wrote:
>>> We have two classes called Query and they are not related.
>>>
>>> com.hp.hpl.jena.query.Query (in ARQ, part of the API)
>>> com.hp.hpl.jena.graph.query.Query (in Jena, not API but is SPI,
>>> suited to RDQL but not SPARQL)
>>>
>>> Proposal: rename ....graph.query.Query as "GQuery".
>>>
>>> Andy
>>
>> Suggest a more explicit name: GraphQuery.
>
>Yes - that's a better name.
>
>>
>> But +1 to a rename. Autocomplete catches me out occasionally.
>
>       Andy
>
>>
>> Damian
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk+6IpgACgkQAyLCB+mTtymxawCeL5TOE0dFSym4EqhAYoBHufuB
>> Gv4AoKsAsi6bpGIuhKFDkqR1i3vFhdgN
>> =QN1k
>> -----END PGP SIGNATURE-----
>

Reply via email to