- From: mca <mca@amundsen.com>
- Date: Sat, 21 Mar 2015 16:14:30 -0400
- To: Erik Wilde <dret@berkeley.edu>
- Cc: Hydra <public-hydra@w3.org>
- Message-ID: <CAPW_8m7nTQ_0dE6jKMK+oBmHipfzqNfMof4iMTPOp9VoQ7Vh-g@mail.gmail.com>
Right you are. I assumed (after only a cursory scan of both docs) that actions would be properties but I see no examples of that as I look again. Looks like this is about defining constraints for sharing objects/graphs in triple form. Thanks for keeping me straight ;) On Mar 21, 2015 2:13 PM, "Erik Wilde" <dret@berkeley.edu> wrote: > hello mike. > > On 2015-03-21 13:37, mca wrote: > >> Hmm... A bit of a cross between a schema and a WSDL. >> > > i am wondering where you see something WSDLish in SHACL. to me, it looks > like a pretty straightforward to look at a metamodel's concepts, and then > design a variety of features that can constrain data in ways that hopefully > make it most useful for real-life tasks. > > what i am crucially missing so far is any kind of wildcard mechanism, > which to me would be absolutely essential for a language for real-life > scenarios. maybe i am just not seeing them, if so, could somebody point > them out, please? thanks! > > Good for getting >> details of a single implementation, but the reliance on cardinality and >> enumerated types, etc. limits wide use beyond a single service >> implementation. >> > > maybe this is the same comment i was making above in terms of a missing > wildcard mechanism? if not, what else are you missing? > > cheers, > > dret. > > -- > erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | > | UC Berkeley - School of Information (ISchool) | > | http://dret.net/netdret http://twitter.com/dret | >
Received on Saturday, 21 March 2015 20:14:58 UTC