W3C home > Mailing lists > Public > public-egov-ig@w3.org > February 2010

Re: [WebTech] Types of Online Government Services - Vocabulary

From: Chris Beer <chris-beer@grapevine.net.au>
Date: Tue, 23 Feb 2010 23:21:47 +1100
Message-ID: <4B83C85B.9020404@grapevine.net.au>
To: Gannon Dick <gannon_dick@yahoo.com>
CC: public-egov-ig@w3.org, Mike Thacker <mike.thacker@esd.org.uk>, VassiliosPeristeras <vassilios.peristeras@deri.org>
Hi Gannon

Quick answer - good points. However we're more talking a plain english 
definition of "online government service" for the purposes of IG Project 
Note outputs :) I just thought that a types as defined in schemas was a 
good place to start in terms of getting the thinking juices going.



On 23/02/2010 7:37 AM, Gannon Dick wrote:
> Chris et. al.
> 'Mike raises another good point which is also a concern with me btw - "do
> we have a definition of service".'
> This is part of a larger education problem with meta data.  Most people think you can choose names and content according to whim.  Actually you can choose either, but not both.  Tabular data (web form submissions, Address Books, etc.) are a much harder problem since the nominal format ("Data View") contains no formal meta data repository.
> see: http://www.rustprivacy.org/meta/roundtripping.pdf
> Fortunately, HTML documents have a meta property list, one D, but you can work with it.  I am not sure you need a definition of a "service" as it is just another resource (under some constrained circumstances).  I approached the problem from a little different perspective:  What do you need for an end-to-end (Word Processor to Catalog) archive process ?
> The OpenOffice XHTML export uses Dublin Core linking syntax, as does AGLS.  The XSLT is (nymg.xsl) "Not Yo Mama's GRDDL".
> example: http://www.rustprivacy.org/meta/mayflower.zip
> Output is a short RDF "resource manifest" giving:
> 1) A Collection (list) of the HTML Profile URL, and other linked namespaces.
> 2) A Collection (list) of the Namespaces, Prefixes and (Said To Be) Languages
> 3) A Collection (list) of (qualified) terms used in this particular document.
> What you will not see is any "gleaned" data - normally the point of GRDDL.  The transform verifies that the meta data links in the<head>  are properly in place according to the DCMI link syntax.
> --Gannon
Received on Tuesday, 23 February 2010 12:22:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:00:43 UTC