+1, I prefer the current style and no clear reason why the other
possibility would be more beneficial for us at this point.
Cheers,
Peter
On 17 March 2015 at 22:27, Andy Seaborne wrote:
> I prefer the current style. It's more common and closer to the specs.
>
> Java itself uses SOAP*, SQL*, XP
+1 for Acronyms as word. I never want to see another XMLSAXDTDParser type
of name...
Gary
On Tue, Mar 17, 2015 at 2:51 AM, Reto Gmür wrote:
> I know it's just a detail and there is no clear right or wrong. Still I'd
> like to have a conscious decision on how to do the casing so we can apply
> i
I'm never quite decided on those.. I struggle with JsonThing vs
JSONThing. One advantage of the first style is that it autocompletes
much nicer, I don't have to type out the full acronym before I can
type the T for Thing (e.g. J T Ctrl-Shift-T). Also it downplays the
importance of the acronym.
get
I prefer the current style. It's more common and closer to the specs.
Java itself uses SOAP*, SQL*, XPath*, JMX*, JAXB*, HTML*, .. and a mix
of Xml and XML, Http and HTTP.
(With deviation from any rules where obvious readability improvements
result.)
Digressing - I found that an identifier
Hi Rob,
In Clerezza we have started a subproject where develop the code we
originally suggested for the commons sandbox. We try to keep the rest of
clerezza in sync with the changes there so we will also have releases on
this subproject. The project shall gradually become closer to the incubator
c
Hi Sergio,
I'm not sure which deliberate decision you are referring to, is it Issue
#35 in Github?
Anyway, the impl.sparql code is not about extending the API to allow
running queries on a graph, in fact the API isn't extended at all. It's an
implementation of the API which is backed by a SPARQL
I know it's just a detail and there is no clear right or wrong. Still I'd
like to have a conscious decision on how to do the casing so we can apply
it consistently everywhere.
Approaches:
A) Acronyms are treated like normal words, i.e. only the first character is
uppercased, this is what the googl
Folks
Can we please avoid cross posting across multiple RDF/Linked Data project
mailing lists now that we have the Commons RDF podling up and running.
For those of us already on the lists of multiple projects getting multiple
copies of discussions is not particularly helpful for keeping track of
Hi Reto,
thanks for updating us with the status from Clerezza.
In the current Commons RDF API we delivery skipped querying for the
early versions.
Although I'd prefer to keep this approach in the initial steps at ASF (I
hope we can import the code soon...), that's for sure one of the next
p
