Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDF::YodaTriples should discourage using faster, quicker serializations #3

Open
anarchivist opened this issue Feb 25, 2015 · 2 comments

Comments

@anarchivist
Copy link
Contributor

< If you choose the quick and easy path as
Vader did - you will become an agent of evil. >
        \
         \         ____
          \     _.' :  `._
            .-.'`.  ;   .'`.-.
   __      / : ___ ;  /___ ;  \      __
 ,'_ ""--.:__;".-.";: :".-.":__;.--"" _`,
 :' `.t""--.. '<@.`;_  ',@>` ..--""j.' `;
      `:-.._J '-.-'L__ `-- ' L_..-;'
        "-.__ ;  .-"  "-.  : __.-"
            L ' /.------. ' J
             "-.   "--"   .-"
            __.l"-:_JL_;-";.__
         .-j/'.;  ;""""  / .'"-.

Parsing YodaTriples should be an exercise in patience. Expedient serializations - and perhaps ones that are easy to read - should be discouraged.

@no-reply
Copy link
Owner

Maybe the module should put the above when required?

@no-reply no-reply mentioned this issue Feb 25, 2015
Merged
@anarchivist
Copy link
Contributor Author

i think this should be reopened for now. @no-reply asked on #4:

So, require 'rdf/yoda_triples' should reopen RDF::Writer to add warnings?

that is my sense, yes. i also considered whether an exception is better, but my sense is that the choice is the up to the padawan, and not the Jedi master:

"It will be a hard life; one without reward, without remorse, without regret. A path will be placed before you. The choice is yours alone. Do what you think you cannot do. It will be a hard life, but you will find out who you are."
―Qui-Gon Jinn, to Anakin Skywalker

@no-reply no-reply reopened this Feb 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants