rvesse merged PR #168:
URL: https://github.com/apache/jena-site/pull/168
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org
W3C is creating a new working group to work on the validation of RDF
data. "Shapes" is code language for this.
Since an initial draft of a charter, there has a been a lot of
discussion of charter on the public W3C list:
public-rdf-sha...@w3.org
http://lists.w3.org/Archives/Pub
Andy Seaborne created JENA-773:
--
Summary: Move RDF/XML writers to com.hp.hpl.jena.rdfxml.xmloutput
Key: JENA-773
URL: https://issues.apache.org/jira/browse/JENA-773
Project: Apache Jena
Issue
1353 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1621353 ]
JENA-773 : Move RDF/XML writer into com.hp.hpl.jena.rdfxml.xmloutput
> Move RDF/XML writers to com.hp.hpl.jena.rdfxml.xmloutput
>
>
>
[
https://issues.apache.org/jira/browse/JENA-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-773.
--
Resolution: Fixed
Fix Version/s: Jena 2.12.1
> Move RDF/XML writers
Hey, folks--
There hasn't been too much feedback on my proposal for a journaling
DatasetGraph:
https://github.com/ajs6f/jena/tree/JournalingDatasetgraph
which was and is to be a step towards JENA-624: Develop a new in-memory RDF
Dataset implementation. So I'm moving on to look a
Stian--
I will look at this today, but even beforehand, I want to volunteer to help in
whatever way is useful to move this effort forward. I filed JENA-1015 because
downstream projects on which I work would very much like to shift to Commons as
their RDF underpinning.
---
A. Soroka
The
Thanks!
Here are some of the other Commons RDF topics that would be good to
get feedback on:
https://lists.apache.org/list.html?d...@commons.apache.org:lte=1M:%5BRDF%5D
Some of these are design questions that would be good to clarify
before we release API changes.
On 29 September 2016 at 14
Andy
I am familiar with Talis Changesets having used them heavily in my PhD
research.
My concerns are much the same as yours in that Changesets really don't
scale well. The other big problem is that since they are RDF graphs they
are unordered since once cannot rely on a serializer/p
Rob,
It's a balance as to whether to put in a discussion section. I'd prefer
to keep the doc as spec-like and just talk about what RDF patch is.
Someone wanting to use/implement RDF patch may not be interested in the
history (this is a few years from now!). A separate doc would ena
Andy,
I am agreed about scalability and stream processing being an important
goal, which as you note the Changesets do not address. To me, the cleanest
way to implement that would be to go beyond an RDF representation and
create a new language as you've done.
The metadata block you menti
It'll be worth while expanding on the streaming and scalability points.
This metadata is a bit complicated: I've falled into some traps here.
The RDF patch format is not an RDF serialization. Blank node labels
work differently so embedding N-Triples or Turtle isn't so automatic
Revised notes on Talis Changesets:
RDF Patch compared to Talis Changesets.
Talis Changesets (TCS) are defined by:
http://docs.api.talis.com/getting-started/changesets
http://docs.api.talis.com/getting-started/changeset-protocol
http://vocab.org/changeset/schema.html
== Brief Description
Stian Soiland-Reyes created JENA-521:
Summary: IO_Jena.resetJena() does not reset RDF/XML
Key: JENA-521
URL: https://issues.apache.org/jira/browse/JENA-521
Project: Apache Jena
Issue
RDF/XML and RDF/XML-Abbrev.
Similarly, IO_JenaWriters.resetJena() did not reset NT, RDF/JSON or RDFJSON.
My suggested patch is at https://github.com/apache/jena/pull/2/files
This patch includes full tests of both registering and resetting, and also
fixes JENA-520 nullpointerexception.
was
uest as a patch file
https://github.com/apache/jena/pull/2.patch because github-style pull requests
are local to github. Eclipse would not apply this patch but command line
"patch -p 2" did. Visual inspection seesm to show it's OK.
> IO_Jena.resetJena()
6942 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1516942 ]
JENA-520 and JENA-521
> IO_Jena.resetJena() does not reset RDF/XML
> ---
>
> Key: JENA-521
> U
> IO_Jena.resetJena() does not reset RDF/XML
> ---
>
> Key: JENA-521
> URL: https://issues.apache.org/jira/browse/JENA-521
> Project: Apache Jena
> Issue Type: Bug
> Components: RI
test/java/org/apache/jena/riot/system/TS_RiotSystem.java
*
/jena/trunk/jena-arq/src/test/java/org/apache/jena/riot/system/TestIO_JenaReaders.java
*
/jena/trunk/jena-arq/src/test/java/org/apache/jena/riot/system/TestIO_JenaWriters.java
> IO_Jena.resetJena() does not reset
6961 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1516961 ]
JENA_520 and JENA-521 -- stablize testing by setting IO state after the tests
run
> IO_Jena.resetJena() does not reset RDF/XML
> ---
>
jena/riot/system/TestIO_JenaWriters.java
> IO_Jena.resetJena() does not reset RDF/XML
> ---
>
> Key: JENA-521
> URL: https://issues.apache.org/jira/browse/JENA-521
> Project: Apache
[
https://issues.apache.org/jira/browse/JENA-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-521.
--
> IO_Jena.resetJena() does not reset RDF/
Hi,
On 09/09/13 23:25, c...@info-cast.com wrote:
Hi,
I'm considering the Jena Rules as a rule-based programming model
where rules are being discovered and accumulated to grow tens of
thousand, while the fact for inferring new info is only a few
RDF statements. In this case, the rule engin
weets.
Best
Chan
Hi,
On 09/09/13 23:25, c...@info-cast.com wrote:
Hi,
I'm considering the Jena Rules as a rule-based programming model
where rules are being discovered and accumulated to grow tens of
thousand, while the fact for inferring new info is only a few
RDF statements. In this
Rob Vesse created JENA-666:
--
Summary: IP Clearance for Hadoop RDF Tools
Key: JENA-666
URL: https://issues.apache.org/jira/browse/JENA-666
Project: Apache Jena
Issue Type: Task
Reporter
[
https://issues.apache.org/jira/browse/JENA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-666:
---
Attachment: Hadoop-RDF-Tools.patch
Attaching patch file containing the donated code
> IP Clearance for Had
adds
the IP Clearance form to track the progress of the clearance with the Incubator
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/jira/browse/JENA-666
> Pr
work an ASF Member
has to carry out the actual formal parts of the process (like calling the votes)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/jira/browse/JENA-666
>
[
https://issues.apache.org/jira/browse/JENA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-666:
---
Attachment: Hadoop RDF Tools - External Version.pptx
Added a Powerpoint presentation which discusses features
[
https://issues.apache.org/jira/browse/JENA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-666:
---
Attachment: Hadoop RDF Tools - External Version.pdf
Adding PDF version of the presentation
> IP Clearance
aking use of your available compute resources
efficiently.
There is also the factor that many formats physically can’t be processed
on a line by line basis because you need access to all the metadata that
might have occurred prior to the current line e.g. namespace prefixes,
base URI etc.
>From
3942 from [~rvesse]
[ https://svn.apache.org/r1583942 ]
Initial import of Hadoop RDF Tools code which is undergoing IP Clearance
process (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
>
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/jira/browse/JENA-666
> Project: Apache Jena
> Issue Type: Task
>Reporter: Rob Vesse
>
2013 YarcData LLC All Rights Reserved.
{noformat}
What dependencies has the code have (and what licenses do they have)?
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/jira/b
4617 from rve...@apache.org
[ https://svn.apache.org/r1584617 ]
Add standard Apache Copyright headers (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
4619 from rve...@apache.org
[ https://svn.apache.org/r1584619 ]
Add stub LICENSE and NOTICE to hadoop-rdf module (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
r created convenience binaries this and their transitive dependencies
should not be an issue. Regardless anything that is a transitive dependency
via Apache Hadoop must be allowed in Apache distributions anyway or the Hadoop
PMC couldn't release it.
The demo app (hadoop-rdf-stats) uses a
nd NOTICE must not contain anything (the minimal principle).
Same for airline.
I've run RAT (it's clean except POM files don't have a license) and looked at
the dependency tree (clean). Looks good from the contribution point of view.
> I
htly different format (same words) to the rest of
the code base. Minot/trivial but it would be nice to be identical in case we
automate some conversion sometime.
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
&g
or a separate release? Or separate
for now (maybe it would change more frequently?), and later in the main release
cycle?
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
then just include it in future Jena releases as it matures.
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/jira/browse/JENA-666
> Project: Apache Jena
5720 from rve...@apache.org
[ https://svn.apache.org/r1585720 ]
Start migrating to org.apache.jena package (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
5723 from rve...@apache.org
[ https://svn.apache.org/r1585723 ]
Continue migrating to org.apache.jena package (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
5724 from rve...@apache.org
[ https://svn.apache.org/r1585724 ]
Continue migrating to org.apache.jena package (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
5725 from rve...@apache.org
[ https://svn.apache.org/r1585725 ]
Continue migrating to org.apache.jena package (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
5727 from rve...@apache.org
[ https://svn.apache.org/r1585727 ]
Complete migrating to org.apache.jena package (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
5734 from rve...@apache.org
[ https://svn.apache.org/r1585734 ]
Change groupId to org.apache.jena (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
5747 from rve...@apache.org
[ https://svn.apache.org/r1585747 ]
Trim down NOTICE per discussion with Andy on JENA-666
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
5750 from rve...@apache.org
[ https://svn.apache.org/r1585750 ]
Add license headers to relevant XML files (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
h we could take a IP
Clearance vote.
I just need to replicate the L&N into the sub-modules and clean up the
copyright header formatting
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https:/
5801 from rve...@apache.org
[ https://svn.apache.org/r1585801 ]
Align license header formatting with rest of Jena (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/j
Jena dependency to 2.11.2-SNAPSHOT (now
2.11.1-SNAPSHOT), or maybe move away from SNAPSHOT?
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/jira/browse/JENA-666
>
rent state of the code to
build are in the 2.11.1 release
However there are known issues that will need us to work off of
2.11.2-SNAPSHOTs once we get the code IP cleared and are able to start actively
developing it again.
> IP Clearance for Hadoop RD
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://issues.apache.org/jira/browse/JENA-666
> Project: Apache Jena
> Issue Type: Task
>Reporter: Rob Vesse
4851 from [~rvesse]
[ https://svn.apache.org/r1594851 ]
Minor corrections to LICENSE and add missing license to POM per comments from
Andy (JENA-666)
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
>
ator IP Clearance vote is now in progress which is the final hurdle to
accepting the code and being able to start actively developing it
> IP Clearance for Hadoop RDF Tools
> -
>
> Key: JENA-666
> URL: https://iss
result email should show up in the archives shortly
The Hadoop RDF Tools code can now be actively developed against, I'll send an
email to the list laying out some ideas around this
> IP Clearance for Hadoop RDF Tools
> -
>
>
[
https://issues.apache.org/jira/browse/JENA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse closed JENA-666.
--
> IP Clearance for Hadoop RDF Tools
> -
>
> K
Andy Seaborne created JENA-1816:
---
Summary: Update constants for the RDF namespace.
Key: JENA-1816
URL: https://issues.apache.org/jira/browse/JENA-1816
Project: Apache Jena
Issue Type: Task
[
https://issues.apache.org/jira/browse/JENA-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1816:
Fix Version/s: Jena 3.15.0
> Update constants for the RDF namesp
mmit 0840c96062a3c20c3734ec47413cafaef859e780 in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=0840c96 ]
Merge pull request #671 from afs/jena1816-rdf-ns
JENA-1816: Updates of the RDF namespace
> Update constants for the R
mmit c5e8d6939274df3505a8beae81901b61c9a945ab in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=c5e8d69 ]
JENA-1816: Updates of the RDF namespace
> Update constants for the R
Osma Suominen created JENA-1826:
---
Summary: Fuseki RDF/XML response never finishes
Key: JENA-1826
URL: https://issues.apache.org/jira/browse/JENA-1826
Project: Apache Jena
Issue Type: Bug
the {{CONSTRUCT}} with {{SELECT (count(\*) AS ?C)}} and see what the
count is.
# Try each of the top-level UNION arms separately and get the counts.
> Fuseki RDF/XML response never finishes
> --
>
> Key: JENA-1826
>
[
https://issues.apache.org/jira/browse/JENA-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021363#comment-17021363
]
Andy Seaborne commented on JENA-1826:
-
Just noticed that this is only for RDF
[
https://issues.apache.org/jira/browse/JENA-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Osma Suominen updated JENA-1826:
Attachment: data.nt
> Fuseki RDF/XML response never finis
[
https://issues.apache.org/jira/browse/JENA-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021439#comment-17021439
]
Osma Suominen commented on JENA-1826:
-
It's clearly the RDF/XML serializa
[
https://issues.apache.org/jira/browse/JENA-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1816.
-
Resolution: Done
> Update constants for the RDF namesp
the effect:
This uses the non-pretty form of RDF/XML:
{{riot --out RDFXML data.nt}}
takes 2 seconds inc program startup.
This uses the pretty form of RDF/XML and takes 5m 20s.
{{riot --pretty RDFXML data.nt}}
Some of the rules mentioned in
https://jena.apache.org/documentation/io/rdfxml_howto.
seki INFO [7] POST http://localhost:3030/ds/sparql
[2020-01-23 16:40:06] Fuseki INFO [7] Query = CONSTRUCT WHERE { ?s ?p ?o }
[2020-01-23 16:45:46] Fuseki INFO [7] 200 OK (339,646 s)
{noformat}
The first request was for Turtle, the second for RDF/XML. The latter took 5m
40s, so pretty
o analysis for possible pretty patterns.
The only way to get 3 to work is write to a temp buffer but that limits scale.
Doing that for some formats not others is messy.
If (2) is done (3) isn't relevant.
> Fuseki RDF/XML r
aybe open a separate issue for (1)? And
consider (3) solved via (2).
> Fuseki RDF/XML response never finishes
> --
>
> Key: JENA-1826
> URL: https://issues.apache.org/jira/browse/JENA-1826
> Project: A
1), maybe someone can -- the relevant
class is {{org.apache.jena.rdfxml.xmloutput.implUnparser}}.
My personal preference is "use Turtle" , "use JSON-LD". I see "pretty RDF/XML"
as an older technology that is now a bit niche. When XML is needed, the flat
and very
[
https://issues.apache.org/jira/browse/JENA-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022410#comment-17022410
]
Osma Suominen commented on JENA-1826:
-
I also don't like RDF/XML that much a
mmit c100fd44fa4fb264c3baab3b281f9d5f9fdf19a2 in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=c100fd4 ]
Merge pull request #678 from osma/jena-1826-fuseki-rdfxml-plain
JENA-1826: use plain RDF/XML in Fuseki RDF responses
> Fuseki RDF/
mmit 265c880ec9152e1af8385886ee79c9a4e94fef25 in jena's branch
refs/heads/master from Osma Suominen
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=265c880 ]
JENA-1826: use "plain" RDF/XML in Fuseki RDF responses as it's faster than
"pretty"
> F
[
https://issues.apache.org/jira/browse/JENA-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1826.
-
Fix Version/s: Jena 3.15.0
Assignee: Osma Suominen
Resolution: Fixed
> Fuseki
Hi jena devs,
a few months ago we have started a discussion around ideas with a few jena
contributors and community members for an in person 20 Year Jena
celebration event. As you are all too familiar with the current situation
around COVID-19 an in person event is now impossible this year and we h
kinow merged pull request #38:
URL: https://github.com/apache/jena-site/pull/38
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
Jon created JENA-2084:
-
Summary: Error in documentation of RDF Thrift format
Key: JENA-2084
URL: https://issues.apache.org/jira/browse/JENA-2084
Project: Apache Jena
Issue Type: Bug
Components
Jon created JENA-2085:
-
Summary: Error in documentation of RDF Thrift Format
Key: JENA-2085
URL: https://issues.apache.org/jira/browse/JENA-2085
Project: Apache Jena
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/JENA-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon closed JENA-2085.
-
Resolution: Duplicate
> Error in documentation of RDF Thrift For
[
https://issues.apache.org/jira/browse/JENA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon updated JENA-2084:
--
Description:
Both [https://jena.apache.org/documentation/io/rdf-binary.html]
and the page that it links to
[https
ames don't get used normally, and at one time,
were taken out. Looks like the docuement and code got out of step.
> Error in documentation of RDF Thrift format
> ---
>
> Key: JENA-2084
> URL: https://issue
[
https://issues.apache.org/jira/browse/JENA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reassigned JENA-2084:
---
Assignee: Andy Seaborne
> Error in documentation of RDF Thrift for
[
https://issues.apache.org/jira/browse/JENA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-2084:
Fix Version/s: Jena 4.1.0
> Error in documentation of RDF Thrift for
[
https://issues.apache.org/jira/browse/JENA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-2084.
-
Resolution: Fixed
> Error in documentation of RDF Thrift for
Andy Seaborne created JENA-2167:
---
Summary: Provide an RDF Binary format using Protobuf
Key: JENA-2167
URL: https://issues.apache.org/jira/browse/JENA-2167
Project: Apache Jena
Issue Type: New
(not relevant for this ticket) and binaries (we will be in convenience
binaries)
zip files: apache-jena, apache-jena-fuseki
Combined jars: jena-fuseki-server, jena-fuseki-fulljar, jena-fuseki-war..
> Provide an RDF Binary format using P
s is slightly inefficient (it create two java
objects per triple, rather than reuse existing objects).
> Provide an RDF Binary format using Protobuf
> ---
>
> Key: JENA-2167
> URL: https://issues.apache.org/ji
mmit e1580129eb0aa823f2ea0eefc363e7d23ad5806d in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=e158012 ]
JENA-2167: Add required text for Protobuf redistribution
> Provide an RDF Binary format us
mmit 1b5617dade712b6f16a4ea7b76469f67c9aff31f in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=1b5617d ]
JENA-2167: Protobuf-based RDF binary format
> Provide an RDF Binary format us
[
https://issues.apache.org/jira/browse/JENA-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-2167.
-
Fix Version/s: Jena 4.3.0
Resolution: Done
> Provide an RDF Binary format using Proto
mmit 0ffb1a795d46a642ec6263838d565158f98564cd in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=0ffb1a7 ]
Merge pull request #1076 from afs/rdf-protobuf
JENA-2167: Protobuf based RDF binary format
> Provide an RDF Binary format us
mmit 2071508862313ab58296ef405f6ecc55ab0ba0a1 in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=2071508 ]
JENA-2167: Flush output
> Provide an RDF Binary format using Protobuf
> ---
>
>
mmit 0c0a509e3b0f5f636306275ef2b7ab273e99e1fc in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=0c0a509 ]
Merge pull request #1079 from afs/fixes
JENA-2172, JENA-2167 and small improvements.
> Provide an RDF Binary format us
kinow merged PR #111:
URL: https://github.com/apache/jena-site/pull/111
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org
afs closed pull request #131: RDF Patch documentation
URL: https://github.com/apache/jena-site/pull/131
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail
Thanks for sharing, Andy.
Expanding your email to include dev@oodt.a.o and dev@tika.a.o since
both projects deal with RDF data too.
All, FYI below.
++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data
JENA-772 (move ARP to com.hp.hpl.jena.rdfxml.xmlinput) and JENA-773
(move RDF/XML writers to com.hp.hpl.jena.rdfxml.xmloutput) are "quick
wins" in organising the code for any re-modularisation we might wish to do.
Andy
401 - 500 of 1081 matches
Mail list logo
