<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet title="XSL formatting" type="text/xsl" href="http://blog.siaige.com/feed/rss2/xslt" ?><rss version="2.0"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>S.I.A.I.G.E : ZE BLOG.... - Tag - stakes internet of things  - Commentaires</title>
  <link>http://blog.siaige.com/</link>
  <atom:link href="http://blog.siaige.com/feed/tag/stakes%20internet%20of%20things/rss2/comments" rel="self" type="application/rss+xml"/>
  <description>Systemes d'Information Appliques a l'Intelligence et a la Guerre Economique
--------------------------------------------------------------------
étude et développement des politiques en matière de systèmes d'information au sens large, dans le cadre de leur implication, ainsi que leur application aux concepts et principes d'intelligence et de guerre économique.
--------------------------------------
http://www.copyrightfrance.com/php/certificat.php?reference=3T53168</description>
  <language>fr</language>
  <pubDate>Fri, 03 Oct 2008 08:10:42 +0200</pubDate>
  <copyright>(c) SIAIGE - http://www.copyrightfrance.com/php/certificat.php?reference=3T53168</copyright>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Dotclear</generator>
  
    
    
    <item>
    <title>Governance issues regarding the “Internet of things”: comments about a chronicle from Jacques Attali announcing the upcoming French ONS root (English version of the previous post). - Neuze Mayo (PG)</title>
    <link>http://blog.siaige.com/post/2007/11/30/Governance-issues-regarding-the-Internet-of-things#c5807881</link>
    <guid isPermaLink="false">urn:md5:ef14f93d5bf6e75cf8826b8e5cd2863d</guid>
    <pubDate>Fri, 30 Nov 2007 16:14:50 +0100</pubDate>
    <dc:creator>Neuze Mayo (PG)</dc:creator>
    
    <description>&lt;p&gt;Mark,&lt;br /&gt;
I do agree with everything in your comment.&lt;br /&gt;
We're on the same line !&lt;br /&gt;
Regards,&lt;br /&gt;
PG&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Governance issues regarding the “Internet of things”: comments about a chronicle from Jacques Attali announcing the upcoming French ONS root (English version of the previous post). - Mark Harrison</title>
    <link>http://blog.siaige.com/post/2007/11/30/Governance-issues-regarding-the-Internet-of-things#c5806553</link>
    <guid isPermaLink="false">urn:md5:6548f0fd68b49789f5397d00c93acf2a</guid>
    <pubDate>Fri, 30 Nov 2007 13:24:28 +0100</pubDate>
    <dc:creator>Mark Harrison</dc:creator>
    
    <description>&lt;p&gt;During the last four years since EPCglobal was formed in late 2003,
significant progress has been made by the EPCglobal community in the
development and ratification of user-driven open standards for many elements of
the EPC Network architecture. These include software standards, as well as
standards relating to hardware, such as the UHF Class 1 Gen 2 air interface,
which has even been adopted by ISO as ISO 18000-6 C. They have also been active
in promoting the technology and helping to drive adoption. This in turn has
helped lead to increased demand and falling prices for low-cost RFID tags
etc.&lt;br /&gt;
Upon ratification, EPCglobal standards are freely available to everybody to
download from &lt;a href=&quot;http://www.epcglobalinc.org/standards&quot; title=&quot;http://www.epcglobalinc.org/standards&quot;&gt;http://www.epcglobalinc.org/standar...&lt;/a&gt;
. Recently, the associated files (XML schema, WSDL files etc.) have also been
made available. In addition, there are open source projects for the EPC
Network, in Java ( &lt;a href=&quot;http://www.accada.org&quot; title=&quot;http://www.accada.org&quot;&gt;http://www.accada.org&lt;/a&gt; ) and C#/.NET ( &lt;a href=&quot;http://source.mit.edu&quot; title=&quot;http://source.mit.edu&quot;&gt;http://source.mit.edu&lt;/a&gt;
).&lt;br /&gt;
The EPC Network is currently positioned primarily as a business-to-business
infrastructure that enables businesses and supply chains to operate more
efficiently through the automated capture and exchange of serial-level data
about the location and movement of individual objects. Although an Object Name
Service (ONS) provides a lookup mechanism to find authoritative information
about an individual object or EPC (usually information provided by the object's
manufacturer), its implementation in DNS is not well suited to providing
dynamic track and trace information in a scalable and secure manner. For this
purpose, complementary lookup services, known as 'Discovery Services' are under
development. EPCglobal is currently gathering user requirements for these,
which will then feed into the development of a technical standard. In parallel,
three IETF internet drafts on Extensible SupplyChain Discovery Services (ESDS)
have been posted - and a mailing list esds@ietf.org has been established to
promote discussion on the design of the technical interfaces and data model.
Over the last 18 months, the BRIDGE project (a 3 year integrated project within
the European Commission's 6th framework programme (FP6)) has also undertaken
significant work on the requirements, design and prototyping of Discovery
Services. The BRIDGE team has also contributed two of their reports to both
EPCglobal's Data Discovery Joint Requirements Group and has also posted the
reports to the ESDS@IETF.ORG mailing list, in order to contribute to current
standardization efforts.&lt;br /&gt;
Discovery Services will probably provide much greater business value than an
Object Name Service. It is already apparent that a number of solution providers
are already providing services targeting this role - and it is hoped that we
can work towards convergent interfaces between them, in order to achieve
interoperability and a genuinely competitive multi-vendor marketplace for
Discovery Services.&lt;br /&gt;
Before this point is reached, EPCglobal may need to rethink their current
business model, in which subscribers are provided with entries in their root
ONS, as one of the subscriber benefits (in addition to the opportunities to
network with other early adopters and actively participate and influence the
development of user-driven standards). Of course, a future 'Internet of Things'
has a much broader scope than the current 'EPC Network'; we can imagine several
location-based services for citizens - effectively interfacing the World Wide
Web much more closely to objects and real-world locations.&lt;br /&gt;
Much of the innovation in the World Wide Web has been driven by the creative
and altruistic ideas of enthusiastic individuals - and it is essential that
citizens are not deterred from full participation in the future 'Internet of
Things'. In the world wide web, there are very low economic barriers to
citizens who wish to create new websites and services - the costs of
registering a domain name and hosting websites are very affordable - and there
are also several providers of free hosting and free website addresses. The
availability of freely available web browsers and many free or affordable
software tools for creating information content and services means that there
are few economic barriers to participation. The free availability of relevant
web standards from W3C and related network standards from other bodies, such as
IETF enables global interoperability.&lt;br /&gt;
Turning to the future 'internet of things', the open standards from EPCglobal
may provide a strong foundation for the technical standards - and the
availability of freely available open source software for the EPC network
should enable the prototyping and development of new and innovative
applications and services by enthusiastic citizens. Falling costs of RFID tags
(economies of scale driven by the large volumes to be used by business) is also
a welcome development.&lt;br /&gt;
However, at present, the EPC identifier namespace does not yet cater for
tagging of individual objects by citizens, nor the tagging of arbitrary
locations anywhere on the planet (such as signposts and viewpoint information
boards within the landscape and national parks, which are not commercial
'business locations'). The good news is that the Electronic Product Code (EPC)
is really a framework that can support multiple identifier schemes - and there
are already standards such as Tag Data Translation and the Tag Data Standard,
which facilitate the mapping of any identifier system into an EPC format. It is
therefore not a difficult technical challenge to develop an EPC identifier
scheme that can encode the latitude, longitude and altitude of any place on
earth (so that it could be read via a mobile phone and linked to location-based
services (e.g. photos, video, reviews) on the web). Likewise, it would
technically be a very trivial matter for an 8-bit EPC header code to be
allocated for private / internal-use identifiers generated by citizens or
companies. It is even conceivable that citizens might use the short codes
generated by URL-shortening services (such as snipurl.com, tinyurl.com,
purl.org) to encode an RFID tag and link it to a particular resource on the
web). Most of the EPCglobal technical standards would continue to function even
if the EPC namespace were opened up to serve an expanded 'internet of things'
that is open for innovation and active participation by all citizens.&lt;/p&gt;</description>
  </item>
      
</channel>
</rss>