W3C home > Mailing lists > Public > public-egovernance@w3.org > August 2013

Project Open Data

From: Gannon Dick <gannon_dick@yahoo.com>
Date: Mon, 26 Aug 2013 10:55:58 -0700 (PDT)
Message-ID: <1377539758.18857.YahooMailNeo@web122901.mail.ne1.yahoo.com>
To: "public-egovernance@w3.org" <public-egovernance@w3.org>
http://project-open-data.github.io/schema/ (ref:accessLevel)

Question:  Why, practically, would it ever be necessary to co-mingle datasets with different accessLevels ? 

1) Support for DB Admin security clearances ? Privacy is not dead, but Curiosity is on Mars.  Open Government Data has pictures.
2) Promoting the extensive use of encryption software solutions ? Which dooms their long term efficacy ?
3) Possibly HTML <BLINK> tags were misunderstood and *not* really annoying ?
4) ??? Any other ideas

The practice is specifically disallowed (not "depreciated") in Legislative Mark-up.
http://uscodebeta.house.gov/download/resources/USLM-User-Guide.pdf
2.2.3 Element Text vs. Attributes
XML attributes are reserved for metadata and/or normalized representations of the element text. No attribute text should ever appear, as is, in the online or printed presentation of the United States Code.
========================



Field
accessLevel
Cardinality (1,1) 
Required Yes, always 
Accepted Values Must be one of the following: Public, Restricted, Private 
Usage Notes This field refers to degree to which this dataset could be made available to the public, regardless of whether it is currently available to the 
public. For example, if a member of the public can walk into your agency and obtain a dataset, that entry is public even if there are no files online. A restricted dataset is one only available under certain conditions or to certain 
audiences (such as researchers who sign a waiver). A private dataset is 
one that could never be made available to the public for privacy, 
security, or other reasons as determined by your agency. 
Example {"accessLevel":"public"} 




________________________________
 From: Brand Niemann <bniemann@cox.net>
To: 'Gannon Dick' <gannon_dick@yahoo.com> 
Sent: Monday, August 26, 2013 7:57 AM
Subject: RE: eGov group transition/Project Open Data
 


Gannon, Please summarize the data sets you have produced that you think I should work with. Thank you, Brand
 
From:Gannon Dick [mailto:gannon_dick@yahoo.com] 
Sent: Thursday, August 22, 2013 6:55 PM
To: Brand Niemann; public-egov-ig@w3.org
Cc: Holm, Jeanne M \(1760\)
Subject: Re: eGov group transition/Project Open Data
 

I promised a small demo. http://www.rustprivacy.org/faca/ogd/
 
The examples are unusual, even by my lax standards.
 
1) Open Government Data Access By Language
    (where else are you going to get a link list of Government Websites in Spanish, or Arabic ?)
 
 
Portable Wealth is an interesting subject, because baggage weight restrictions on international flights are  ... never mind ... let's just say every clean sock is priceless nowadays.  Everybody's a refugee.
 
2) + 3) It occurred to me that Language Skills are a form of Portable Wealth.  So, 2) tells you about the 219 Languages (via the LOC id servers ISO 639-1).  In a pinch, you might be able to use the Government data websites as a safe ad hoc Rosetta Stone for translation in places where search engines might get problematic. 3) is Currencies in use, by Country, roughly for the last 20 years.  The gimmick is that once you've looked up the Currency by name, you can expand the search globally.  This is another way at "Portable Wealth".
 
Talk to you all tomorrow.
 
--Gannon
Received on Monday, 26 August 2013 17:56:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:39:01 UTC