<HTML>
<HEAD>
<TITLE>Re: [Geodata] Rebooting this committee [SEC=UNCLASSIFIED]</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>While current semantic work (e.g. RDF, SKOS, LinkedData etc) is very important and will be of immense benefit to us, there are many issues that are also relevant, including:<BR>
<BR>
</SPAN></FONT><UL><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>spatial discovery metadata and catalogues / registries;
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>open spatial standards underpinning our view of the world from the ‘universe of discourse’ through to detailed ‘application profiles’ that implement logical data models for a given domain. There is a lot of work happening within this space, e.g. with GeoSciML, WaterML 2.0, CSML 3.0, etc;
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>the semantic relationships between similar concepts from different domains (‘application profiles’);
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>authoritative vocabulary services, persistent ids etc;
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>managing IP, access constraints, licensing, CC, etc;
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>managing data provenance, e.g. If I publish a scientific paper, what data was used to underpin the analysis communicated in the paper. This could relate to specific gridded datasets and what observation data was current within the database at the time that the grids were created;<BR>
</SPAN></FONT></UL><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'><BR>
<BR>
Bruce<BR>
<BR>
<BR>
<BR>
On 31/07/12 9:23 AM, "Scot Wilcoxon" <<a href="scot@wilcoxon.org">scot@wilcoxon.org</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'>On Mon, 2012-07-30 at 11:40 +0100, Seven (aka Arnulf) wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT COLOR="#3C3C3C"><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>1. My suggestion is to also use this committee as a hub to build<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'> </SPAN></FONT><FONT COLOR="#3C3C3C"><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>knowledge around licenses, maintain a repository of initiatives and link<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'> </SPAN></FONT><FONT COLOR="#3C3C3C"><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>everything together. Not so much like hard metadata in a catalog but a<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'> </SPAN></FONT><FONT COLOR="#3C3C3C"><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>lot looser, more like a big bucket with goodies to find.<BR>
</SPAN></FONT></FONT></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'><BR>
I think the concept that you're looking for is a "semantic web".<BR>
<a href="http://en.wikipedia.org/wiki/Semantic_Web">http://en.wikipedia.org/wiki/Semantic_Web</a><BR>
<BR>
A bunch of buckets of data, and you define the characteristics of the buckets so software can use (and display) the info.<BR>
<BR>
* You have a license object which defines the characteristics of a license. Probably defined in something like XML.<BR>
* You define a license (identifier="CC-BY-SA", name="Creative Commons ... etc", restrictions="share-derivatives,attribute", etc...) -- except you probably use XML.<BR>
* You have a data object which defines the characteristics of some data, and this includes the license (identifier).<BR>
* You define data using the data object characteristics.<BR>
<BR>
If a data definition is available through a URL, inside that definition will be the relevant other objects, including the URL of the data object definition, the license identifier ("CC-BY-SA"), and the URL of the definition of the license. Similarly, the license includes the URL of the license object which defines all the license fields.<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>