date:20110117

Re: ANN: geometry2rdf software library

2011-01-17 Thread Boris Villazón Terrazas


Hi Christopher

We are also developing a KML exporter with a viewer (within a map) of 
RDF resources. You can find it at [1].
Right now it takes a while to load the facets; once you have the facets, 
for example click on Aiport. Then, click on the KML button (up/right 
corner on the map) to get the KML.

We expect to deliver the final version soon.

All this work is included within the context of GeoLinkedData [2] which 
is an open initiative whose aim is to enrich the Web of Data with 
Spanish geospatial data.


Thanks

Alex and Boris

[1] http://geo.linkeddata.es:8282/GeoLinkedData-DbPedia/
[2] http://geo.linkeddata.es/

On 17/01/2011 3:01, Christopher Gutteridge wrote:

Cool, I've been doing something (very hacky) the other way around.

http://graphite.ecs.soton.ac.uk/geo2kml/
It only handles points and dc:spatial POLYGONs so far, but is really 
handy for checking RDF geo point data, as you can bung it onto google 
maps (or earth) to see if it looks sane.


(I'll happily give away the PHP source if anyone wants, but it's 
pretty shonky *grin*)


Boris Villazón Terrazas wrote:

Dear all

We are pleased to announce geometry2rdf [1], a library for generating 
RDF from geometrical information (Points, LineStrings and Polygons).
The current version of the library works with Oracle geospatial 
databases.


All the best,
Victor, Miguel Angel and Boris


[1] http://www.oeg-upm.net/index.php/downloads/151-geometry2rdf

Re: ANN: geometry2rdf software library

2011-01-17 Thread Giovanni Tummarello

Boris would you be able to provide a bit of explanation on why would
you want o do that e.g. what evidence are there (nice use cases) were
an rdf export of low level features in the map is of use
thanks!
Gio

On Mon, Jan 17, 2011 at 2:34 AM, Boris Villazón Terrazas
bvilla...@fi.upm.es wrote:

 Victor, Miguel Angel and Boris

ANN: DBpedia 3.6 released

2011-01-17 Thread Chris Bizer

Hi all, 

we are happy to announce the release of DBpedia 3.6. The new release is
based on Wikipedia dumps dating from October/November 2010. 

The new DBpedia dataset describes more than 3.5 million things, of which
1.67 million are classified in a consistent ontology, including 364,000
persons, 462,000 places, 99,000 music albums, 54,000 films, 16,500 video
games, 148,000 organizations, 148,000 species and 5,200 diseases. 

The DBpedia dataset features labels and abstracts for 3.5 million things in
up to 97 different languages; 1,850,000 links to images and 5,900,000 links
to external web pages; 6,500,000 external links into other RDF datasets, and
632,000 Wikipedia categories. 

The dataset consists of 672 million pieces of information (RDF triples) out
of which 286 million were extracted from the English edition of Wikipedia
and 386 million were extracted from other language editions and links to
external datasets. 

Along with the release of the new datasets, we are happy to announce the
initial release of the DBpedia MappingTool
(http://mappings.dbpedia.org/index.php/MappingTool): a graphical user
interface to support the community in creating and editing mappings as well
as the ontology. 

The new release provides the following improvements and changes compared to
the DBpedia 3.5.1 release: 

1. Improved DBpedia Ontology as well as improved Infobox mappings using
http://mappings.dbpedia.org/. 

Furthermore, there are now also mappings in languages other than English.
These improvements are largely due to collective work by the community.
There are 13.8 million RDF statements based on mappings (11.1 million in
version 3.5.1). All this data is in the /ontology/ namespace. Note that this
data is of much higher quality than the Raw Infobox data in the /property/
namespace. 

Statistics of the mappings wiki on the date of release 3.6: 

+ Mappings: 
 + English: 315 Infobox mappings (covers 1124 templates including
redirects) 
 + Greek: 137 Infobox mappings (covers 192 templates including
redirects) 
 + Hungarian: 111 Infobox mappings (covers 151 templates including
redirects) 
 + Croatian: 36 Infobox mappings (covers 67 templates including
redirects) 
 + German: 9 Infobox mappings 
 + Slovenian: 4 Infobox mappings 
+ Ontology: 
 +  272 classes 
+  Properties: 
 + 629 object properties 
 + 706 datatype properties (they are all in the /datatype/ namespace) 

2.  Some commonly used property names changed. 

+ Please see http://dbpedia.org/ChangeLog and
http://dbpedia.org/Datasets/Properties to know which relations changed and
update your applications accordingly! 

3. New Datatypes for increased quality in mapping-based properties 

+ xsd:positiveInteger, xsd:nonNegativeInteger, xsd:nonPositiveInteger,
xsd:negativeInteger 

4. Improved parsing coverage.

+ Parsing of lists of elements in Infobox property values that improves the
completeness of extracted facts. 
+ Method to deal with missing repeated links in Infoboxes that do appear
somewhere else on the page. 
+ Flag templates are parsed. 
+ Various improvements on internationalization. 

5. Improved recognition of 

+ Wikipedia namespace identifiers. 
+ Wikipedia language codes. 
+ Category hierarchies. 

6. Disambiguation links for acronyms (all upper-case title) are now
extracted (for example, Kilobyte and Knowledge_base for KB): 

+ Wikilinks consisting of multiple words: If the starting letters of the
words appear in correct order (with possible gaps) and cover all acronym
letters. 
+ Wikilinks consisting of a single word: If the case-insensitive longest
common subsequence with the acronym is equal to the acronym. 

7. Encoding (bugfixes): 

+ The new datasets support the complete range of Unicode code points (up to
0x10). 16-bit code points start with '\u', code points larger than
16-bits start with '\U'. 
+ Commas and ampersands do not get encoded anymore in URIs. Please see
http://dbpedia.org/URIencoding for an explanation regarding the DBpedia URI
encoding scheme. 

8. Extended Datasets: 

+ Thanks to Johannes Hoffart (Max-Planck-Institut für Informatik) for
contributing links to YAGO2. 
+ Freebase links have been updated. They now refer to mids
(http://wiki.freebase.com/wiki/Machine_ID) because guids have been
deprecated. 

You can download the new DBpedia dataset from http://dbpedia.org/Downloads36

As usual, the dataset is also available as Linked Data and via the DBpedia
SPARQL endpoint at http://dbpedia.org/sparql

Lots of thanks to: 

+ All editors that contributed to the DBpedia ontology mappings via the
Mappings Wiki. 
+ Max Jakob (Freie Universität Berlin, Germany) for improving the DBpedia
extraction framework and for extracting the new datasets. 
+ Robert Isele and Anja Jentzsch (both Freie Universität Berlin, Germany)
for helping Max with their expertise on the extraction framework. 
+ Paul Kreis (Freie Universität Berlin, Germany) for analyzing the DBpedia
data of the previous release and

Re: Introducing Vocabularies of a Friend (VOAF)

2011-01-17 Thread Stephane Fellah

Bernard,

Thanks for your answer. Another question I was wondering: Can we extend the
VOAF ontology to describe SKOS taxonomies ? Does this question make sense to
you ?  In the case of SKOS, we have only the notion of concepts not classes
and properties.

Regards
Stephane Fellah

On Sat, Jan 15, 2011 at 6:52 PM, Bernard Vatant
bernard.vat...@mondeca.comwrote:

 Hi Stephane

 2011/1/15 Stephane Fellah fella...@gmail.com

 Sounds very interesting initiative. Based on my understanding, I think it
 should be possible to write a tool that read any OWL document and generate a
 VOAF document.


 Indeed I've been thinking along those lines. The current dataset is
 handcrafted as a prototype should be, but I'm indeed thinking now about ways
 to generate the VOAF description automagically from the OWL or RDFS files.
 Devil is in the details, though. Some information you can't really get by
 conventional parsing of the graph, such as which namespaces are used, to
 populate the voaf:reliesOn property. Those you can get by ad hoc syntactic
 scripts, but vocabularies are published using a variety of syntaxes.


 May be Swoogle could be a good starting point, but not sure how the API
 can provide the list of ontology namespaces through the REST API.


 I don't know either, but I'm sure someone will find a way :)


 The imports section would corresponds to the imports statement. The tools
 would count the number of classes and properties in the ontology namespace.
 It would be interesting to aggregate all this information and see which
 vocabularies have the most influence using SNA algorithms.


 You are welcome to play along those lines. I think there are a lot of
 opportunities and things to discover. This is just the beginning of the
 story.

 Best

 Bernard



 --
 Bernard Vatant
 Senior Consultant
 Vocabulary  Data Engineering
 Tel:   +33 (0) 971 488 459
 Mail: bernard.vat...@mondeca.com
 
 Mondeca
 3, cité Nollez 75018 Paris France
 Web:http://www.mondeca.com
 Blog:http://mondeca.wordpress.com

ICWE 2011: Second Call for Papers

2011-01-17 Thread Sören Auer


  11th International Conference on Web Engineering (ICWE 2011)

   http://icwe2011.webengineering.org
June 20-24, 2011, Paphos, Cyprus

 *** Second Call for Papers ***


The International Conference on Web Engineering (ICWE) aims at promoting
scientific and practical excellence on Web Engineering, and at bringing
together researchers and practitioners working in technologies,
methodologies, tools, and techniques used to develop and maintain
Web-based applications leading to better systems, and thus to enabling
and improving the dissemination and use of content and services through
the Web. A special focus of ICWE 2011 will be Web Data Engineering.


*Topics of Interest*

The conference fosters original submissions covering, but not restricted
to the following topics of interest:

Web application engineering
   * Processes and methods for Web application development
   * Conceptual modeling of Web applications
   * Model-driven Web application development
   * Domain-specific languages for Web application development
   * Component-based Web application development
   * Web application architectures and frameworks
   * Rich Internet Applications
   * Mashup development and end user Web programming
   * Patterns for Web application development and pattern mining
   * Web content management and data-intensive Web applications
   * Web usability and accessibility
   * I18N of Web applications and multi-lingual development
   * Testing and evaluation of Web applications
   * Deployment and usage analysis of Web applications
   * Performance modeling, monitoring, and evaluation
   * Empirical Web engineering
   * Web quality and Web metrics
   * Adaptive, contextualized and personalized Web applications
   * Mobile Web applications and device-independent delivery

Web service engineering
   * Web service engineering methodologies
   * Web Service-oriented Architectures
   * Semantic Web services
   * Web service-based architectures and applications
   * Quality of service and its metrics for Web applications
   * Inter-organizational Web applications
   * Ubiquity and pervasiveness
   * Linked Data Services

Web data engineering
   * Semantic Web engineering
   * Web 2.0 technologies
   * Social Web applications
   * Web mining and information extraction
   * Linked Data
   * Web data linking, fusion
   * Information quality assessment
   * Data repair strategies
   * Dataset dynamics
   * Dataset introspection
   * Linked Data consumption, visualisation and exploration
   * Deep Web
   * Web science and Future Internet applications


*Submission instructions*

Authors of the research and industrial papers track must explain the
relationship of their work to the Web Engineering discipline in their
submissions. Research papers must comprise substantial innovative
discussion with respect to the related work and must be well motivated
and presented.

   * Extension: Papers must not be longer than 15 (fifteen) pages.
   * Format: according to the LNCS guidelines.
   * Submission: http://www.easychair.org/conferences/?conf=icwe2011


*Publishing of accepted works*

The conference proceedings will be published by Springer-Verlag as an
LNCS volume. Official proceedings will include: full papers (15 pages),
demonstration papers (4 pages) and posters (4 pages). Workshop
papers and contributions to the doctoral consortium will be published
separately. Final versions of accepted papers must strictly adhere to
the LNCS guidelines and must include a printable file of the
camera-ready version, as well as all source files thereof. No changes
to such formatting rules are permitted. Authors of accepted papers
must also download and sign a copyright form that will be made
available on the Web site of the conference. Each paper requires at
least one full registration to the main conference. Selected papers
will be invited to submit an extended version to a special issue of the
JCR-indexed Journal Of Web Engineering (pending agreement).


*Important Dates*

   * Submission deadline: February 14, 2011 (23:59 Hawaii Time)
   * Notification of acceptance: April 14, 2011
   * Camera-ready version: April 28, 2011


*Program Chairs*

   * Oscar Diaz, University of the Basque Country, Spain
   * Sören Auer, Universität Leipzig, Germany

In case of inquiries, please contact the program chairs at:
pcchairs [at] icwe2011.webengineering.org


*Conference Committee*

General Chair
   * George A. Papadopoulos, University of Cyprus, Cyprus
Industrial Track Chair
   * Andreas Doms, SAP Research, Germany
Workshop Chairs:
   * Nora Koch, LMU and Cirquent GmbH, Germany
   * Andreas Harth, KIT, Germany
Tutorial Chairs
   * Cesare Pautasso, University of Lugano, Switzerland
Demo  Poster Chairs
   * Axel Ngonga, Universitat Leipzig
   * Pelechano Vicente, Universidad Politecnica de Valencia
Doctoral Consortium Chairs
   * Peter Dolog, Aalborg University, Denmark,
   * Bernhard Haslhofer,

2nd CfP: Linked Data on the Web (LDOW2011) Workshop at WWW2011

2011-01-17 Thread Chris Bizer

Hi all,

 

this is just a quick reminder that the submission deadline of the 4th
International Workshop on Linked Data on

the Web (LDOW2011) at WWW2011, Hyderabad, India is approaching slowly. The
deadline is in about 3 weeks: 

 

Submission deadline: 8th February, 2011

 

The LDOW2011 website is now available at:

 http://events.linkeddata.org/ldow2011/
http://events.linkeddata.org/ldow2011/

 

Please find below the CfP and we are looking forward to see you at LDOW2011!

 

Cheers,

 

Chris Bizer

Tom Heath

Tim Berners-Lee

Michael Hausenblas

 

 

=

 

Linked Data on the Web (LDOW2011) Workshop at WWW2011

 

http://events.linkeddata.org/ldow2011/

 

=

 

Workshop date: March 29th, 2011, Hyderabad, India

 

Submission deadline: 8th February, 2011

 

=

 

Objectives

 

The Web has developed into a global information space consisting not just of
linked documents, but also of linked data. In 2010, we have seen significant
growth in the size of the Web of Data as well as in the number of
communities contributing to its creation. In addition, there is intensive
work on applications that consume Linked Data from the Web.

 

The LDOW2011 workshop in Hyderabad follows the LDOW2008 workshop in Beijing,
the LDOW2009 workshop in Madrid, and the LDOW2010 workshop in Raleigh. As
the previous workshops, LDOW2011 is open to cover all topics related to
Linked Data publication as well as consumption, including principled
research in the areas of user interfaces for the Web of Data as well as on
issues of quality, trust and provenance in Linked Data. We also expect to
see a number of submissions related to current areas of high Linked Data
activity, such as government transparency, life sciences and the media
industry. The goal of this workshop is to provide a forum for exposing high
quality, novel research and applications in these (and related) areas. In
addition, by bringing together researchers in this field, we expect the
event to further shape the ongoing Linked Data research agenda.

 

=

 

Topics of Interest

 

Topics of interest for the LDOW2011 workshop include, but are not limited
to:

 

1. Foundations of Linked Data 

* Web architecture and dataspace theory

* dataset dynamics and synchronisation

* analizing and profiling the Web of Data

 

2. Data Linking and Fusion

* entity consolidation and linking algorithms

* Web-based data integration and data fusion

* performance and scalability of integration architectures

 

3. Write-enabled Linked Data Web

* access authentication mechanisms for Linked Datasets (WebID, etc.)

* authorisation mechanisms for Linked Datasets (WebACL, etc.)

* enabling write-access to legacy data sources (Google APIs, Flickr API,
etc.)

 

4. Data Publishing

* publishing legacy data sources as Linked Data on the Web 

* cost-benefits of the 5 star LOD plan

 

5. Data Usage 

* tracking provenance of Linked Data

* evaluating quality and trustworthiness of Linked Data

* licensing issues in Linked Data publishing

* distributed query of Linked Data

* RDF-to-X, turning RDF to legacy data 

 

6. Interaction with the Web of Data

* approaches to visualise Linked Data 

* interacting with distributed Web data

* Linked Data browsers, indexer and search engines

 

 

 

=

 

Submissions

 

We seek three kinds of submissions:

 

1. Full technical papers: up to 10 pages in ACM format

2. Short technical and position papers: up to 5 pages in ACM format

3. Demo description: up to 2 pages in ACM format

 

Submissions must be formatted using the WWW2011 templates available via the
LDOW2011 homepage. We note that the author list does not need to be
anonymised, as we we do not have a double-blind review process in place.

 

Submissions will be peer reviewed by at least three independent reviewers.
Accepted papers will be presented at the workshop and included in the
workshop proceedings.

 

Please submit your paper via EasyChair at

http://www.easychair.org/conferences/?conf=ldow2011

 

=

 

Important Dates

 

Submission deadline: 8th February, 2011

Notification of acceptance: 25th February, 2011 

Camera ready versions of accepted papers: 10nd March, 2011

Workshop date: Tuesday, 28th or 29th March, 2011  

 

=

 

Organising Committee

 

Christian Bizer, Freie Universität Berlin, Germany

Tom Heath, Talis Systems Ltd, UK

Tim Berners-Lee, MIT CSAIL, USA

Michael Hausenblas, DERI, NUI Galway, Ireland

 

=

 

Contact

 

For further information about the workshop, please contact the

workshops chairs at ldow2011 [at] events [dot linkeddata [dot] org

 

=

 

 

 

--

Prof. Dr. Christian Bizer

Property for linking from a graph to HTTP connection meta-data?

2011-01-17 Thread Martin Hepp


Hi all,

In some cases, it's useful to attach HTTP connection meta-data, in  
particular HTTP response header parameters, to an RDF graph, in  
particular whenever we rdfize existing Web content. For example, if  
we fetch a CSV file and derive an RDF representation thereof, we may  
want to preserve the original HTTP header information.


Luckily, there is a W3C RDF vocabulary for HTTP [1, 2].

Directly using the header properties [3] seems possible. However, it  
would turn the RDF graph into a http:Response (because the domain of  
all header properties is http:Response).


Does anybody know of a standard property for linking a RDF graph to a  
http:GetRequest, http:Connection, or http:Response instance? Maybe  
rdfs:seeAlso (@TBL: ;- ))?


Best

Martin

[1] http://www.w3.org/2006/http#
[2] http://www.w3.org/TR/HTTP-in-RDF/
[3] http://www.w3.org/WAI/ER/HTTP/WD-HTTP-in-RDF-20070301#header




martin hepp
e-business  web science research group
universitaet der bundeswehr muenchen

e-mail:  h...@ebusiness-unibw.org
phone:   +49-(0)89-6004-4217
fax: +49-(0)89-6004-4620
www: http://www.unibw.de/ebusiness/ (group)
 http://www.heppnetz.de/ (personal)
skype:   mfhepp
twitter: mfhepp

Re: Introducing Vocabularies of a Friend (VOAF)

2011-01-17 Thread Christopher Gutteridge

I can't help but feel that calling it VOAF is just going to muddy the
waters. Friendly vocabularies for the linked data Web
doesn't help clarify either. It's cute, but I strongly suggest you at
the very least make this 'tag line' far more clear. Frankly calling
something 'voaf' when people will hear it mixed in with 'foaf' is just
making the world more confusing. I had a lot of confusion until I found
out the SHOCK vocab people were talking about was spelled SIOC.

One other minor suggestion;
Vocabulary
http://graphite.ecs.soton.ac.uk/browser/?uri=http%3A%2F%2Fwww.mondeca.com%2Ffoaf%2Fvoaf%23Vocabulary#http://www.mondeca.com/foaf/voaf#Vocabulary
? rdfs:subClassOf
http://graphite.ecs.soton.ac.uk/browser/?uri=http%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23subClassOf#http://www.w3.org/2000/01/rdf-schema#subClassOf
? void:Dataset
http://graphite.ecs.soton.ac.uk/browser/?uri=http%3A%2F%2Frdfs.org%2Fns%2Fvoid%23Dataset#http://rdfs.org/ns/void#Dataset

might be a mistake because void:Dataset is defined as A set of RDF
triples that are published, maintained or aggregated by a single
provider. ad it may be that you would want to define non RDF vocabs
using this. I see no value in making this restriction.

On 17/01/11 15:26, Stephane Fellah wrote:

Bernard,

Thanks for your answer. Another question I was wondering: Can we
extend the VOAF ontology to describe SKOS taxonomies ? Does this
question make sense to you ? In the case of SKOS, we have only the
notion of concepts not classes and properties.

Regards
Stephane Fellah

On Sat, Jan 15, 2011 at 6:52 PM, Bernard Vatant
bernard.vat...@mondeca.com mailto:bernard.vat...@mondeca.com wrote:

Hi Stephane

2011/1/15 Stephane Fellah fella...@gmail.com
mailto:fella...@gmail.com

Sounds very interesting initiative. Based on my understanding,
I think it should be possible to write a tool that read any
OWL document and generate a VOAF document.

Indeed I've been thinking along those lines. The current dataset
is handcrafted as a prototype should be, but I'm indeed thinking
now about ways to generate the VOAF description automagically from
the OWL or RDFS files. Devil is in the details, though. Some
information you can't really get by conventional parsing of the
graph, such as which namespaces are used, to populate the
voaf:reliesOn property. Those you can get by ad hoc syntactic
scripts, but vocabularies are published using a variety of syntaxes.

May be Swoogle could be a good starting point, but not sure
how the API can provide the list of ontology namespaces
through the REST API.

I don't know either, but I'm sure someone will find a way :)

The imports section would corresponds to the imports
statement. The tools would count the number of classes and
properties in the ontology namespace. It would be interesting
to aggregate all this information and see which vocabularies
have the most influence using SNA algorithms.

You are welcome to play along those lines. I think there are a lot
of opportunities and things to discover. This is just the
beginning of the story.

Best

Bernard

--
Bernard Vatant

Senior Consultant
Vocabulary Data Engineering
Tel: +33 (0) 971 488 459
Mail: bernard.vat...@mondeca.com mailto:bernard.vat...@mondeca.com

Mondeca
3, cité Nollez 75018 Paris France
Web: http://www.mondeca.com
Blog: http://mondeca.wordpress.com

--
Christopher Gutteridge -- http://id.ecs.soton.ac.uk/person/1248

/ Lead Developer, EPrints Project, http://eprints.org/
/ Web Projects Manager, ECS, University of Southampton,
http://www.ecs.soton.ac.uk/
/ Webmaster, Web Science Trust, http://www.webscience.org/

URI Comparisons: RFC 2616 vs. RDF

2011-01-17 Thread Martin Hepp


Dear all:

RFC 2616 [1, section 3.2.3] says that

When comparing two URIs to decide if they match or not, a client   
SHOULD use a case-sensitive octet-by-octet comparison of the entire

   URIs, with these exceptions:

  - A port that is empty or not given is equivalent to the default
port for that URI-reference;
  - Comparisons of host names MUST be case-insensitive;
  - Comparisons of scheme names MUST be case-insensitive;
  - An empty abs_path is equivalent to an abs_path of /.

   Characters other than those in the reserved and unsafe sets (see
   RFC 2396 [42]) are equivalent to their % HEX HEX encoding.

   For example, the following three URIs are equivalent:

  http://abc.com:80/~smith/home.html
  http://ABC.com/%7Esmith/home.html
  http://ABC.com:/%7esmith/home.html


Does this also hold for identifying RDF resources

a) in theory and
b) in practice (e.g. in popular triplestores)?

I did not test it yet, but I assume that not all implementations would  
treat


   http://purl.org/NET/c4dm/event.owl#Event
   HTTP://purl.org/NET/c4dm/event.owl#Event
   http://PURL.org/NET/c4dm/event.owl#Event
   http://purl.org:80/NET/c4dm/event.owl#Event

as the same class.

Any facts or opinions?

Best

Martin


[1] http://www.ietf.org/rfc/rfc2616.txt


martin hepp
e-business  web science research group
universitaet der bundeswehr muenchen

e-mail:  h...@ebusiness-unibw.org
phone:   +49-(0)89-6004-4217
fax: +49-(0)89-6004-4620
www: http://www.unibw.de/ebusiness/ (group)
 http://www.heppnetz.de/ (personal)
skype:   mfhepp
twitter: mfhepp

34 matches

Mail list logo