I am experimenting with a new style of URI which not only identifies a SW resource but also summarizes its semantics under a built-in upper ontology.
My design goal was a new form of OWL-compatible "word sense" for Lexikos' NLP software, but I suspect "SAIDs" can advance BioPAX goals and perhaps those of ontology authors generally.
My Premises
BioPAX would benefit by using such URIs to denote its vocabulary. If future releases included them, all ontology models, changes, and debates on changes would be easier to understand.
They would also help BioPAX interoperate with other ontologies, and simplify the task of "converting" triples from a supplier's schema into new versions compliant with BioPAX.
My Offer
I'd like to work with BioPAX.org to release a working variation of web API [1], which can simplify the tasks of suppliers doing data imports:
[1] ![[WWW]](/wiki/modern/img/moin-www.png){kind=small}
http://www.lexikos.com/exhibit/10questions/interactions.jsp
My offer is to make it save supplier postings as CSV files, then validate them by adapting my WORDS validator [2] to work from PSAID facets:
[2] http://www.lexikos.com/words/constraints.htm
BioPAX.org must concurrently use pre-release utility [3] to create, debate, and publish in arrays for [1] your related 2.x vocabulary models as PSAIDs:
[3] http://www.lexikos.com/exhibit/10questions/editor.jsp
You must also help me plan how to configure RDF-export templates by using the BioPAX ontology; pass in the captured data; get suppliers to buy into this new program; and make it into an on-going community resource.
Comments are welcome on below or by email. Suppliers especially - please say what you think of the first tool, and if you think some variation of it might help get your data converted more quickly.
Thanks - Dan Corwin
---
Hi Dan- this sounds interesting, but unfortunately I can't understand it (too many acronyms + jargon and no examples/explanations of introduced concepts). It would help if you could provide a brief description of use case (motivation) and some examples. Thanks.
Gary - There are demos at [1] and [3] with all those things. You won't "get" this until you try both out, and build a few SAIDs using [3]. Don't worry about messing anything up; easy to clean it up later. Dan.