Justin, I'm sorry you felt that the wikipedia links were directed at you, the definitions were meant for this conversation and its readers as some may or may not be aware of them. I honestly can't read anyone's mind or know what they already know, but you did seem to imply that they were both one and the same just now and I just wanted to point out that they may in fact be different.
On Wednesday, May 7, 2014, Justin Israel <[email protected]> wrote: > Thank you for sharing the definition of a database schema with me. I would > not have know this otherwise. > I'm not going to further the debate since I think it's not going anywhere > productive. > > > On Thu, May 8, 2014 at 7:59 AM, Marcus Ottosson > <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');> > > wrote: > >> To be clear, schemas and parsing are not one and the same. >> >> http://en.wikipedia.org/wiki/Database_schema >> http://en.wikipedia.org/wiki/Parsing >> >> It really isn't a matter of splitting hairs. >> >> This is an example of schemas in action. >> https://code.google.com/p/protobuf/ >> >> And the re module, and possibly pyparsing, is an example of parsing. >> >> >> >> On 7 May 2014 20:38, Justin Israel <[email protected]> wrote: >> >> Marcus that is exactly what you do with pyparsing. >> >> If it helps to call it a schema then let's call it that. The list you >> made with the 4 string elements is that same as if you defined 4 word rules >> in pyparsing and the list itself is the same as the mechanism they give you >> to combine them into a grammar. This grammar can then be used to parse the >> path string. The only difference I see between what you are showing and >> what pyparsing seems to offer is that pyparsing would be more robust in >> defining the rules. For instance, you have just assigned indexes to a >> paths split components. But what if index 4 is different depending on what >> 3 evaluates to. What if 4 can be broken up into two individual components >> like res_colorspace? That is the stuff you could define as part of the >> grammar. >> >> Also there isn't anything saying you couldn't wrap the parsing into >> something that gives you object oriented access like a Project object. But >> at some point, you will have a path and you will need to parse it to be >> able to generate the instances of your objects. Starting with the name of a >> project would be straightforward if you then wanted to access a shot off it >> by name. >> On May 8, 2014 12:05 AM, "Marcus Ottosson" <[email protected]> >> wrote: >> >> That’s a good point; paths could potentially be filled with rules that >> need to be broken down, re-defined often and remain well understood. >> >> I would however argue whether or not it is a good idea to rely this >> heavily on paths in the first place, as it seems better suited for a schema. >> >> About object composition and schemas, this is what I’m picturing as an >> alternative to (my understanding of) pyparsing: >> Objects >> >> >>> project.shot(1000).used_assets() >> ['myasset1', 'myasset2'] >> >> As opposed to >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAWLQD4WVrrTP%2BGQ7%2BOC4JoaHxbbVdES6zarNb3L7Ys_w%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAWLQD4WVrrTP%2BGQ7%2BOC4JoaHxbbVdES6zarNb3L7Ys_w%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > [email protected]<javascript:_e(%7B%7D,'cvml','python_inside_maya%[email protected]');> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA0tuGQPb1gexKupGDgf74dp_6sB%2Br7oGqn4X7P%3DNqNjEw%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA0tuGQPb1gexKupGDgf74dp_6sB%2Br7oGqn4X7P%3DNqNjEw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- *Marcus Ottosson* [email protected] -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAG_m622-mSo7BaTVe_Z8CT%2BhtZPomHswKN5cDQ-9KE8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
