Changes between Version 5 and Version 6 of RDF Workshop


Ignore:
Timestamp:
May 29, 2007, 7:18:00 PM (14 years ago)
Author:
Earle Martin
Comment:

This discussion has moved to WikiRDF.org.

Legend:

Unmodified
Added
Removed
Modified
  • RDF Workshop

    v5 v6  
    1 = RDF Workshop =
    2 
    3 == Rationale ==
    4 Both OpenGuides and WikiTravel produce ResourceDescriptionFramework output for their pages. It is probably desirable, given the similar scope of the two projects, that both use an interchangeable format. Let's use this page to work one out.
    5 
    6 Participants:
    7  * EarleMartin of OpenGuides
    8  * EvanProdromou of WikiTravel
    9  * TomHeath of the [http://miltonkeynes.openguides.org/ Open Guide to Milton Keynes]
    10  * IvorWilliams of OpenGuides
    11  
    12 == What do we want to list? ==
    13  * Page / Revision metadata
    14    * Name
    15    * Revision date
    16    * Revision version number (default is latest for page)
    17    * Comments about this revision
    18    * Major or minor change?
    19 
    20  * Physical metadata
    21    * Name
    22    * Address
    23    * Telephone
    24    * Fax? (how often is the fax field completed? is this unnecessary duplication of information?)
    25    * Postcode/ZIP
    26    * URL
    27    * Categories
    28    * Locales
    29    * Opening hours?
    30    * Summary? (like the stuff that goes in the "summary of this node" field)
    31    * Geo Location
    32 
    33  * Contributor Metadata
    34    * Nickname
    35    * Real Name (optional)
    36    * Mailbox hash, e.g. foaf:mbox_sha1sum (optional)
    37    * Homepage/FOAF URI/some other target for rdfs:seeAlso (optional)
    38    * Public key / digital signature?
    39 
    40  * Legal Metadata (This could apply to something on a page e.g. a citation or a photo)
    41    * Licence terms
    42    * Special permission for OpenGuides / WikiTravel
    43    * Copyright holder
    44    * Copyright date range
    45    * Artist (like contributor)
    46    * Source URL
    47 
    48  * Access control
    49    * Function to control (e.g. read, edit, delete)
    50    * Allow list of groups/individuals
    51    * Deny list of groups/individuals
    52 
    53 == Access to RDF ==
    54  * '''OpenGuides''': Link from navigation toolbar on every node. Should have a <link rel="alternate" type="application/rdf+xml"> as well; Earle is planning this for the next version.
    55  * '''WikiTravel''': Global Special:Rdf script with form, enter page name and select what to output
    56 
    57 == Differences ==
    58 Example of current OpenGuides RDF:
    59  * http://london.openguides.org/index.cgi?id=Covent_Garden_Market;format=rdf
    60 
    61 Example of current WikiTravel RDF:
    62  * http://wikitravel.org/en/Special:Rdf (then enter a node name, e.g. "Milton Keynes")
    63    * or cheat - here's a direct link: http://wikitravel.org/en/Special:Rdf?target=Milton+Keynes&modelnames%5B%5D=inpage&modelnames%5B%5D=cc&modelnames%5B%5D=links&modelnames%5B%5D=image&modelnames%5B%5D=interwiki&modelnames%5B%5D=categories&format=xml
    64 
    65 ''What does OpenGuides do in RDF that WikiTravel doesn't?''
    66  * As far as I can work out, the major feature that OpenGuides has is RDF describing the "thing" the page is about, not just RDF about the actual wiki entry. This is a really valuable feature imho. -- TomHeath
    67  * Has JSON output, I think - ChrisSchmidt, did your code for this ever get in? -- EarleMartin
    68 
    69 ''What does WikiTravel do in RDF that OpenGuides doesn't?''
    70  * Supports a range of output formats (Turtle and NTriples, as well as RDF/XML). The OpenGuides doesn't do this AFAIK, but I could be wrong. -- TomHeath
    71  * Various Dublin Core metadata items:
    72    * Links to the page (<dcterms:isReferencedBy>)
    73    * Links from the page (<dcterms:references>)
    74    * Historical versions of the page (<dcterms:hasVersion>), each with its own rdf:Description block containing version URL, creator, timestamp and language (plus <dcterms:isVersionOf>)
    75    * Images in the page (<dcterms:hasPart>), each with its own rdf:Description block containing <dc:type rdf:resource="http://purl.org/dc/dcmitype/Image"/>
    76 
    77 == Comments ==
    78 
    79 I like the range of Dublin Core in WikiTravel's output and think we should match it all by default (i.e. as if the user had selected all the options in WT's Special:Rdf). The selective option is nice, though, because I can imagine that you might want to retrieve a selected subset of data for a wide range of pages. So, we should support a URL argument for specifying what kind of RDF is wanted. A small script that allows you to do this in a pointy-clicky way - i.e., a clone of Special:Rdf! - as well as hacking the URL would be useful.
    80 
    81 WikiTravel and OpenGuides do location hierarchy in a different way. OpenGuides:
    82 {{{
    83 <foaf:based_near>
    84   <wn:Neighborhood>
    85     <dc:title>Westminster</dc:title>
    86   </wn:Neighborhood>
    87 </foaf:based_near>
    88 }}}
    89 
    90 WikiTravel:
    91 {{{
    92 <rdf:Description rdf:about="urn:x-wikitravel:en:Milton_Keynes">
    93   <dcterms:isPartOf rdf:resource="urn:x-wikitravel:en:Bedfordshire"/>
    94 </rdf:Description>
    95 }}}
    96 
    97 (Note that WikiTravel uses URNs, but that's a separate topic I'd like to discuss later.)
    98 
    99 Both approaches have their benefits, and I wonder if we could merge them. Something like:
    100 
    101 {{{
    102 <!-- sucky URLs may be subject to change! -->
    103 <dcterms:isPartOf rdf:resource="http://london.openguides.org/index.cgi?id=Westminster;format=rdf#obj"/>
    104 <foaf:based_near>
    105   <wn:Neighborhood rdf:about="http://london.openguides.org/index.cgi?id=Westminster;format=rdf#obj">
    106     <dc:title>Westminster</dc:title>
    107   </wn:Neighborhood>
    108 </foaf:based_near>
    109 }}}
    110 
    111 Make sense?
    112 
    113 As Tom comments above, WikiTravel is currently lacking data about the subject of the page itself. It would be great to get this in.
    114 
    115 That's all I can think of for the moment but more will probably be coming.
    116 
    117 -- EarleMartin
    118 
    119  * Yep, good point about merging these approaches Earle. Moving to pretty URIs like http://london.openguides.org/locales/Westminster (and using them in the RDF) would provide a useful source of URIs for otherwise 'unidentified' (as far as the Web is concerned) locations. Somewhere like [http://miltonkeynes.openguides.org/?Locale_Fishermead Fishermead] is unlikely to warrant an entry on Wikipedia (or WikiTravel I guess). -- TomHeath
    120 
    121 Just braindumped in some things I would like to see in our feed. Not looked at WikiTravel yet. -- IvorWilliams
    122 
    123 ----
    124 
    125 Braindump from the 2006 meetup: http://opensearch.a9.com/ - format for search results; http://geonames.org/search.html provides location names with unique IDs, and there are RDF versions! Those would be /perfect/ for replacing the x-wikitravel-urn URNs. I will investigate this more. -- Earle
    126 
    127 I'd also like to possibly start using my [http://downlode.org/Code/RDF/wiki/ Wiki Profile Vocabulary]. This will probably require my getting some solid permanent URIs sorted out. -- Earle
    128 
    129 ----
    130 
    131 More related work to look at comes from the Semantic MediaWiki project: http://ontoworld.org/wiki/Special:ExportRDF/San+Diego . How much overlap do we have?
     1This discussion has moved to http://wikirdf.org/cgi-bin/wiki.pl?GeoWikiWorkshop.