Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 11 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(1)
我负责管理南安普顿大学开放数据服务。 http://data.southampton.ac.uk/
为了热爱所有神圣的事物,请不要不要发明一个新的词汇——已经有很多可靠的工作了。
该网站旨在成为其他人借鉴想法的典范。我们使用了简单的解决方案,易于用户使用,并且所有工具都是开源的。我们主要使用简单的电子表格,然后使用 XSLT 来生成 RDF 数据。所有这些也是开源的。用于生成每个数据集的所有工具都与数据集一起发布,以便直接复制我们的方法或将其用作起点非常容易。
选择好的、简单的、可持续的 URI 是关键。我们使用域来执行此操作并且仅此操作:例如。 http://id.southampton.ac.uk/building/59
人员 -- 开始与 FOAF 一起。
人员角色——我建议您查看英国公务员制度制作的“组织图”。这将角色视为包含零个或更多人的群体类型。 (多个人可以拥有相同的角色,角色可以在人员为空的地方存在)
出版物 - 我们为此使用 bibo 和 dcterms。最棘手的部分是将其巧妙地与人和人联系起来。会议
——我们目前不对此进行建模,但您可以使用标准的“事件”词汇,除非有理由不这样做:http://motools.sourceforge.net/event/event.html
项目——这是我们刚刚开始考虑的事情,我目前的计划是使用 http://ontoware.org/swrc/
研究领域;我这里还没有任何有用的想法。
我们正在尝试在 openorg.ecs.soton.ac.uk 上记录此类任务的合理启动模式——这将是一项持续不断的工作。目标是生成具有足够通用结构的数据,以便您可以创建与多个组织合作的应用程序,并更轻松地合并来自其他站点的信息。
我写了一篇博客文章,演示了一种工具,可处理(放置)南安普顿、牛津和林肯生成的 RDF 数据(尽管林肯数据服务器现在处于离线状态)http://blogs.ecs.soton.ac.uk/data/2011/11/25/roi/
我们有一个名为“openorg”的 RDF 命名空间,用于存储我们已经添加的附加词汇发现我们需要完成我们的任务。我们尽力将这种情况保持在最低限度,并且大多数内容都是使用现有词汇来描述的。
至于在数据之上构建网站,我们使用一个名为“Graphite”的 PHP 库(我是该库的首席开发人员,并且是免费开源的)。这相对容易上手。 http://graphite.ecs.soton.ac.uk/
这都是非常新的,所以当我们学习好的和坏的技术时,我们将更新内容。
I run the University of Southampton Open Data Service. http://data.southampton.ac.uk/
For the love of all that is holy, don't invent a new vocab -- there's plenty of solid work already out there.
This site is designed to be a model for other people to lift ideas from. We've used simple solutions which are easy for users to consume and all the tools are open source. We mostly use simple spreadsheets, then XSLT to produce RDF data. All of this is also open source. All of the tools used to generate each dataset are published with the dataset to make it really easy to either directly copy our approach, or use it as a starting point.
Picking good, simple, sustainable URIs is key. We use a domain to do this and only this: eg. http://id.southampton.ac.uk/building/59
People -- start with FOAF.
Person Roles -- I suggest you look at the "organogram" produced by the UK civil service.. this treats a role as a type of group which contains zero or more people. (multiple people can have the same role, and roles can exist where people are empty)
Publications -- we use bibo and dcterms for this. The trickiest part is neatly linking it back to people & parts of the organisation etc.
Meetings -- we don't currently model this, but you can just use the standard "event" vocab unless there's a reason not to: http://motools.sourceforge.net/event/event.html
Projects -- this is something we're just starting to consider, and my current plan is to use http://ontoware.org/swrc/
Research area; I don't have any useful ideas here, yet.
We are trying to document sensible starting patterns for this kind of task on openorg.ecs.soton.ac.uk -- which will be a constant work in progress. The goal is to produce data with enough commonality of structure that you can create apps which work with more than one organisation, and more easily merge information from other sites.
I've written a blog post demonstrating one tool working with (places) RDF data produced by Southampton, Oxford and Lincoln (although the Lincoln data server is offline right now) http://blogs.ecs.soton.ac.uk/data/2011/11/25/roi/
We have an RDF namespace called "openorg" for the additional vocab we've found we need to achieve our tasks. We try to keep this to a minimum and most things are described using existing vocabs.
As for building the site on top of the data, we are using a PHP Library called "Graphite" (which I'm the lead developer on, and is Free Open Source). This is relatively easy to get started with. http://graphite.ecs.soton.ac.uk/
This is all very new so we'll be updating things as we learn good and bad techniques.