It helps a lot and thanks for sending. That explains a lot about some of the
issues with open versus native definitions also. Thank you, knowing most of the
battle is going to ALWAYS BE uphill at least puts things in perspective. (01)
DEBORAH MACPHERSON
Specifications and Research (02)
Cannon Design
3030 Clarendon Blvd.
Suite 500
Arlington, VA 22201
Phone: 703.907.2353
Direct Dial: 2353 (03)
dmacpherson@xxxxxxxxxxxxxxxx
Cannondesign.com
Skype debmacp (04)
-----Original Message-----
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
[mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Peter R. Benson
Sent: Monday, March 11, 2013 11:53 AM
To: 'Ontology Summit 2013 discussion'
Subject: Re: [ontology-summit] Hackathon: BACnet Ontology (05)
Deborah, IP is a real issue. We designed the eOTD to try to resolve some of
these issues. In a dictionary the IP resides in the representation but also in
the identifiers or codes as these are always copyright. The eOTD is a
collection of terminology sourced from international, national and industry
standards as well as terminologies and glossaries that are either published or
directly provided to ECCMA from corporations. ECCMA assigns public domain
concept and terminology identifiers specifically to allow the concepts and
associated terminology to be referenced without using proprietary identifiers.
eOTD encoded data is portable data it contains only public domain identifiers. (06)
We work in a space where companies pay to have their master data cleaned and
many have been disappointed when they become aware that "Data coded using a
licensed dictionary (metadata) or validated using licensed data requirements or
created using licensed description rules is subject to the terms of the
license" so making sure that their contractor uses eOTD concept identifiers
solves this problem. (07)
The eOTD also supports those companies that spend considerable amounts of time
and money developing very valuable content services. The eOTD allows them to
keep control over their IP will providing their customers with eOTD encoded
"non-proprietary" data. (08)
I hope this helps. (09)
Peter (010)
-----Original Message-----
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
[mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of MacPherson,
Deborah
Sent: Monday, March 11, 2013 10:16 AM
To: Ontology Summit 2013 discussion
Subject: Re: [ontology-summit] Hackathon: BACnet Ontology (011)
Can anyone point to a map or registry somewhere that distinguishes between what
is open versus well-funded licensed? Specifically I'm interested in facility
related of course but, any example of Linked Open Data versus ISO versus
patented IP. (012)
Particularly for this community I would also ask for feedback on how an open
ontology might help bridge the gaps even if you had to pay-to-play for some
parts of a workflow. (013)
DEBORAH MACPHERSON
Specifications and Research (014)
Cannon Design
3030 Clarendon Blvd.
Suite 500
Arlington, VA 22201
Phone: 703.907.2353
Direct Dial: 2353 (015)
dmacpherson@xxxxxxxxxxxxxxxx
Cannondesign.com
Skype debmacp (016)
-----Original Message-----
From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
[mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Joel Bender
Sent: Monday, March 11, 2013 10:03 AM
To: Ontology Summit 2013 discussion
Subject: Re: [ontology-summit] Hackathon: BACnet Ontology (017)
Deb, (018)
> I've forwarded onto someone at Project Haystack that was working on pumps.
A few months ago I sent him some information from Matthew West RE: the 15926
Reference Library - they were interested in that too but had questions about IP
licensing of ISO 15926 and if it is compatible with the open source license
they are using for Haystack. (019)
Licensing is going to be a stumbling block... more like a brick wall. (020)
> I share your excitement about Building Automation Federated Lexicon
(BAFL). Some convergence forces are practically undeniable... (021)
Yes, there are forces pulling them together, but I fear the intellectual
property rights daemons with their pay walls, they are very well funded.
Thank you for the encouragement, we soldier on! (022)
Joel (023)
_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/ (024)
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013
Community Portal: http://ontolog.cim3.net/wiki/ (025)
_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/ (026)
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013
Community Portal: http://ontolog.cim3.net/wiki/ (027)
_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013
Community Portal: http://ontolog.cim3.net/wiki/ (028)
_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013
Community Portal: http://ontolog.cim3.net/wiki/ (029)
|