I've reviewing the FHIR Extension: TEL-address (https://www.hl7.org/fhir/extension-iso21090-tel-address.html) and at the sample section (https://www.hl7.org/fhir/datatypes-examples.html#ContactPoint) I guess there is a mistake, as valueUrl must be used instead of valueUri.
Hope useful
Martí
Thanks. Please use the 'propose a change' link at the bottom of any page in the FHIR specification to submit a change request. There's a 1-time free registration (where we verify you're a human), after which you're free to submit any issues you find.
Related
since google did not create extensive documentation for their API Linter and I cannot find anything from other sources, i wanted to ask here.
From what exactly am i supposed to create protofiles and what do they represent?
As I understood, these protofiles get checked for compliance to their AIPs.
I'm interested in creating a automatic prototype (Java) to check for customized API Rules and am thinking about using Protobufer for this goal. Would this be a pragmatic solution?
Thank you!
As I now understand, Googles API Linter isn't supposed to check a API or a different API specification for compliance.
It checks proto files because they are themself the API specification and can be converted to Code. But before converting them they can be checked against rules they have to comply with.
These rules are not in the protofiles (as I initially thought) but in the many GO-files under rules/ .
Please correct me if you read this and find mistakes! Thanks!
Please, we are developing with new BotComposer and we know there are several memory scopes var that we can use:
[user], for example: "user.surname" is valid if we created previously this var in scope "user"
We know too "turn.recognized.intent" for the last recognized intent...
We know too "dialog.result" if we save a result of a dialog into result...
But what about the others? The predefined or existing values?
· What type of information and how we can obtain all the settings with settings?
· What type of information and how we can obtain all the dialog vars with dialog?
The same for class and this...
We are searching how to obtain current conversationId for example...
The docs for memory can be found in the Composer docs and BotBuilder docs.
The BotBuilder docs will probably be most helpful to you. Let me know if those docs answer your questions and feel free to open issues if something is missing or confusing.
I would like to understand why I can not continue my work with Carrot2. A message appears saying "Our apologies, the following processing error has occurred:
org.carrot2.source.etools.IpBannedException: org.apache.http.client.HttpResponseException: Forbidden"
There is a problem with eTools, Wiki, PUT document sources (31/07/19) into Online version. I try to work with the downloaded version of the programme, but no document source does not work. Could you solve this problem and how long it will take?
Thank you!
Please see here:
http://project.carrot2.org/faq.html#ipbanned
We provide the search interface as a demo of the technology and we use a partnership with a company called Comcepta (eTools) for providing a limited number of free search requests. Unfortunately, some people have been abusing this free service and we had to introduce per-IP limitations.
If you wish to extend your query limits please install Carrot2 locally and contact Comcepta for custom query limit arrangements.
Apologies for the inconvenience.
I'm using DotNetKit 1.2.6.5 and SagePayIntegration.Validation() is rejecting a customer email that uses the new .online domain (eg: foo#bar.online) with
CustomerEMail is invalid.
Is this fixed in 1.2.6.7 or is the source code for SagePay.IntegrationKit.DotNet.dll available somewhere so I can fix it?
Despite access to the source code (many thanks to #DavidG) SagePay Support have confirmed that the actual Gateway does not support all these new domains - so even if I modified the DotNetKit it would still be rejected by the Gateway.
SagePay support were very helpful but ultimately the
"... email domain foo#bar.online is not yet supported on our gateway.
We run development sprints continuously and although there are some
domains we may not yet support, we look to in future, dependent on
impact and demand..."
The SagePay Integration Kit uses this regex to validate email addresses:
[a-zA-Z0-9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-zA-Z0-9!#$%&'*+/=?^_`{|}~-]+)*#(?:[a-zA-Z0-9](?:[a-zA-Z0-9-]*[a-zA-Z0-9])?\.)+(?:[a-zA-Z]{2,4})\b
Which does unfortunately not allow extra long TLDs. Fortunately I have the source code for the kit and I've added it to my GitHub account (along with a bug fix which is why I had to get it in the first place as SagePay are not updating it). You can find it here:
https://github.com/WiredUK/SagePay.IntegrationKit
And the Regex you need to edit is this file:
https://github.com/WiredUK/SagePay.IntegrationKit/blob/801f61cf965c391a98a025aa632949719084cef0/ApiRegex.cs
For info, you need to edit the very last part of the expression from 2,4 (which matches 2 to 4 characters in the TLD) to allow more, for example 2,30.
Edit: And just because I can, I opened an issue and fixed it.
I'm working with some legacy exchange code and I am having trouble finding information about some methods/constants. A google search reveals others using similar code, but with no explanations. Does anyone have any ideas where I can find proper docs? One constant I am looking for is: SYNC_ASSOCIATED.
Exchange is a Microsoft protocol, so the best place to look is usually MSDN.
The MSDN library, however, seems curiously lacking on Exchange documentation, but an MSDN search looks in a few other places too.
In this case, it's led me to this blog post which gives you a number of constants as they would be defined in a C header file. SYNC_ASSOCIATED is defined as 0x10.
This is part of ICS, Exchange's mechanism for monitoring and tracking changes in a mailbox. See the ICS section of the bulk data transfer protocol spec.