Question from the title - is it possible to store bank account number in vCard? Does the specification says something? Any guidelines?
m.
Yes. vCARD supports extensions, which means you could use something like
X-BANK-ACCOUNT-NUMBER:12345678
Or, you could just put the details in the comments field.
You can read more about the vCARD extensions on Wikipedia.
I am not an expert on this topic. That said, I strongly recommend against storing any sensitive information in a vCard. As far as I know, vCard does not support encryption (someone please correct me if I am mistaken).
Related
I'm a bit surprised there is not a defined type for a Document. Can I put a type in there that is not outlined in the Full Schema.org Hierarchy?
I'll probably use Article but it seems crazy that there isn't a type defined for documents. Such as legal documents, contracts, agreements, statement of work, NDAs, etc... Maybe a Product?
There is probably no right or wrong answer here, just looking for some tips.
CreativeWork seems to be the closest.
In the meantime there is DigitalDocument which is intended for electronic files and documents.
So my question is simple and probably your answers will tell this is not possible...
Maybe on the first use of the dll file, I should see what is the MAC Address and put a restriction on that base? :)
Interesting question! You could manage a kind of white/black list (of course encrypted) in your DLL and handle the restriction code in DLL_PROCESS_ATTACH and then return TRUE or FALSE according to your needs.
You will need to search for specific technology or language and see what standard approaches do people use for this.
There is a trade off between how difficult it is to set up your product and the defence level. The tougher you make it for the bad guys, the tougher it will become to use your product.
You can use some sort of obfuscation and library encryption, which will work providing your user has a key (or password).
I'm curious to know some more details about the various SQL standard's, i.e. SQL-92, SQL:99, SQL:2003, SQL:2008 etc. There is a short and useful overview on Wikipedia, with links to very expensive documents. Why are those documents not open to public? Can I find some open and free information?
Please, don't post links you found from Google. I'm interested in somewhat authoritative documentation only.
Quoting from one of my web sites:
We all love open source software. Wouldn’t it be great if
international standard documents such as the SQL standard would be
open too?
As a matter of fact: they are!
However, they are not free—just public. Very much like open source
software is not necessarily free. Too often, we neglect these
differences. Just because we have to pay for the standard doesn't mean
it is secret.
A download of the most relevant part of the SQL standard—part 2—is
available for USD 60 at ANSI. A CD with all parts on it can be bought
from ISO for CHF 352. Not free, but affordable.
You mentioned in some comments that you are mostly interested in part 2, so spending USD 60 might be your best option.
If you just need to know about the syntax up to 2003, there are two great free resources:
BNF grammar of SQL-92, SQL:1999 and SQL:2003: http://www.savage.net.au/SQL/
Online validator for SQL:1999: https://developer.mimer.com/services/sql-validator-99/
Finally, the complete text of “SQL-99 Complete, Really” is available at the MariaDB knowledge base. However, this book was written in 1999 when no database actually supported the described features. Keep that in mind when using this resource.
Other answers also mentioned "free" copies of the standards available on the web. Yes there are—those are mostly draft versions. I can't tell which of them are legal, so I rather not link them.
Finally a little self ad: I've just launched http://modern-sql.com/ to explain the standard in an easily accessible way to developers. Note that the actual standards text is written like laws are written :) Depending on your background, that might anyway not what you want.
The Postgresql Developer FAQ maintains links to each of them:
http://wiki.postgresql.org/wiki/Developer_FAQ#Where_can_I_get_a_copy_of_the_SQL_standards.3F
There are some hyperlinked versions of 92, 99 and 2003 here
However, I've never been able to use them effectively (read: I gave up).
This 92 text is useful (and is quoted here on SO several times)
ISO/IEC 9075-1:2011 -- google that.
Actually, digging around I found
http://www.incits.org/standards-information/
and it has freely availble section that clicks to something that redirects to here:
http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
And finally the standards.
You have to accept a license agreement to download a pdf.
However, from what I have read in my pursuit - the RDMS well the 'RD' part is going the way of the dinosaur.. If you are building something new (therefore want the new standards) you may want to reconsider all options.
You don't have to pay for all of the standards. SQL-92 is freely available, for instance.
This was asked in an interview.
I think the answer can be done by constructing a trie of all valid words and then suggestions can be made based on a possible valid path which was otherwise given as incorrect.
Say if user types apfle, and system would detect that after ap a possible valid path was app, which would then satisfy apple.
Is there any better solution than this? Perhaps the one implemented by spell checkers.
See:
How does the Google "Did you mean?" Algorithm work?
How do I approximate "Did you mean?" without using Google?
How to write a spelling corrector
Youtube Video: Search 101
Within typical search engines you will find a lot of Analyzer stuff, which directs to the same underlying problem. A very popular Analyzer would be the n-gram Analyzer.
Perhaps this helps.
I am having to use the Google AdWords API for a project, I have large chunks working but I am getting frustrated with the documentation. For example I know that a TextAd headline field has a limit of 25 characters and can't have things like ! and ? in it. The documentation makes no mention of it though:
http://code.google.com/apis/adwords/docs/reference/v200909/AdGroupAdService.TextAd.html
Does anyone know where I can find this kind of info? This is not a question about the TextAd service, but about the documentation so that I don't have to find the limits of all these fields by trial and error.
Many thanks,
b.
This post is a bit old, but since it showed up at the top of my Google search results I though it might be worth posting a link to the limits.
A list of the limits can be found here:
https://code.google.com/apis/adwords/docs/appendix/limits.html
And I found a list of disallowed symbols here (though there might be a better source):
https://support.google.com/adwords/bin/answer.py?hl=en&answer=53539
Phil
You won't find these limits in the AdWords API documentation anywhere, because these limitations are imposed by AdWords policies rather than any sort of character limit in the API.
Therefore, you must resort to AdWords documentation in order to find out things like the maximum length for an ad description or headline.
https://adwords.google.com/support/aw/bin/answer.py?hl=en-uk&query=characters&answer=6095&type=f should be a good starting point!
Cheers,
Sérgio