Why not? It may be stupid, but I'm buying it if material feels right to my skin.
Is Hamas and Iran yours?
UNRWA is compromised as hell, ofc it must go, so it's a pretty good use case for ethical ads usage. Definitely not a reason to enforce an additional censorship.
Location: Buenos Aires, Argentina Remote: Yes Willing to relocate: Depends Technologies: JavaScript/TypeScript, NodeJS, React, Graphl, Relay, Apollo, Nextjs, Python, Postgres, Mongodb, Couchdb, Dynamodb and etc and etc.…
This is incredible. I really want it to take off.
omg. ok, adopting some F features is an interesting idea. but why are they trying to make that thing with syntax happen?
tbh, tailwind feels like the worst thing that happened to frontend dev since coffee script.
> semantic web forcing everything into a single schema I don't think "forcing" is the right word here, I think the right one would be "expects it to converge under practical incentives". That's a more gentle statement…
Oh, I would like to see a look on your face when just in about 100-200 years from now it will be mature enough for a "web scale".
Understood, thank you. Yes, that's not solvable with just OWL (though it might help a little) or any other popular reasoners I know. There're papers, proposals and experimental implementations for generating…
so if it tries to have a unified ontology that's why it's destined to fail, but if it's designed to working with many small ontologies… that's why it will fail! lol, but you can't have it both ways. In SW, the…
That's a valid point, but I'm not sure, the following problem has a technical solution: > Clear indicators the owl author didn't know the domain
There're a lot of wrong perspectives on the topic in this thread, but this one I like the most. When someone starts to talk about "agreeing on a single schema/ontology" it's a solid indicator that that someone needs to…
Isn’t it similar to linear types in haskell?
We’re not, but your point is still valid.
If you open specification linked to that page ( https://wicg.github.io/sanitizer-api/#sanitizer-api ), you'll see that Sanitizer constructor accepts config param, that does exactly that and will probably extended before…
Location: Saint-Petersburg, Russia Remote: Yes Willing to relocate: Yes Technologies: Javascript/TypeScript, React (Relay/Redux/Apollo), Postgresql/Mysql/NoSQLs, K8S, Python Résumé/CV:…
As a non-US citizen, I have 3 questions: 1. WTF 2. Is it even enforceable? 3. Does anybody know recent examples?
> However, there now exist a number of contexts in which namespace prefixes can impart information value in an XML document. Well, yeah. They've given up to a mass amount of half-ass implementations? So what? I think…
I would say use XML Schema at least. DTD looks alien to XML anyway.
It doesn't affect data model encoded in document even a tiny bit. Namespace prefixes are irrelevant. If changing these prefixes breaks the program, the program is incorrect.
Well, yeah, true. I believe it's mostly implementation and popularisation problems. The w3c specs surrounding xml/xpath/xslt/rdf and etc are very well designed but it's possible to appreciate them only after you spend…
> That doesn't seem accurate at all. It would be the case if there was some deterministic abbreviation from URL namespace qualifiers down to namespace prefixes, but there is not; I'm not sure what you mean by that, tbh.…
What do you suggest to use instead? It's a bit too early to use RDF, people haven't catch up yet.
> This breaks people's mental models of how XML works, and correspondingly, breaks people's code that manipulates XML. Because they usually have incorrect mental model. Blaming namespaces for name ambiguity would be the…
Why not? It may be stupid, but I'm buying it if material feels right to my skin.
Is Hamas and Iran yours?
UNRWA is compromised as hell, ofc it must go, so it's a pretty good use case for ethical ads usage. Definitely not a reason to enforce an additional censorship.
Location: Buenos Aires, Argentina Remote: Yes Willing to relocate: Depends Technologies: JavaScript/TypeScript, NodeJS, React, Graphl, Relay, Apollo, Nextjs, Python, Postgres, Mongodb, Couchdb, Dynamodb and etc and etc.…
This is incredible. I really want it to take off.
omg. ok, adopting some F features is an interesting idea. but why are they trying to make that thing with syntax happen?
tbh, tailwind feels like the worst thing that happened to frontend dev since coffee script.
> semantic web forcing everything into a single schema I don't think "forcing" is the right word here, I think the right one would be "expects it to converge under practical incentives". That's a more gentle statement…
Oh, I would like to see a look on your face when just in about 100-200 years from now it will be mature enough for a "web scale".
Understood, thank you. Yes, that's not solvable with just OWL (though it might help a little) or any other popular reasoners I know. There're papers, proposals and experimental implementations for generating…
so if it tries to have a unified ontology that's why it's destined to fail, but if it's designed to working with many small ontologies… that's why it will fail! lol, but you can't have it both ways. In SW, the…
That's a valid point, but I'm not sure, the following problem has a technical solution: > Clear indicators the owl author didn't know the domain
There're a lot of wrong perspectives on the topic in this thread, but this one I like the most. When someone starts to talk about "agreeing on a single schema/ontology" it's a solid indicator that that someone needs to…
Isn’t it similar to linear types in haskell?
We’re not, but your point is still valid.
If you open specification linked to that page ( https://wicg.github.io/sanitizer-api/#sanitizer-api ), you'll see that Sanitizer constructor accepts config param, that does exactly that and will probably extended before…
Location: Saint-Petersburg, Russia Remote: Yes Willing to relocate: Yes Technologies: Javascript/TypeScript, React (Relay/Redux/Apollo), Postgresql/Mysql/NoSQLs, K8S, Python Résumé/CV:…
As a non-US citizen, I have 3 questions: 1. WTF 2. Is it even enforceable? 3. Does anybody know recent examples?
> However, there now exist a number of contexts in which namespace prefixes can impart information value in an XML document. Well, yeah. They've given up to a mass amount of half-ass implementations? So what? I think…
I would say use XML Schema at least. DTD looks alien to XML anyway.
It doesn't affect data model encoded in document even a tiny bit. Namespace prefixes are irrelevant. If changing these prefixes breaks the program, the program is incorrect.
Well, yeah, true. I believe it's mostly implementation and popularisation problems. The w3c specs surrounding xml/xpath/xslt/rdf and etc are very well designed but it's possible to appreciate them only after you spend…
> That doesn't seem accurate at all. It would be the case if there was some deterministic abbreviation from URL namespace qualifiers down to namespace prefixes, but there is not; I'm not sure what you mean by that, tbh.…
What do you suggest to use instead? It's a bit too early to use RDF, people haven't catch up yet.
> This breaks people's mental models of how XML works, and correspondingly, breaks people's code that manipulates XML. Because they usually have incorrect mental model. Blaming namespaces for name ambiguity would be the…